I would do this type of discovery using LibreNMS “Components” which are a generic way of storing data and polling it. Standard Interface is tighlty linked to IF-MIB and would not be adapted for anything else.
Using Components, you could do a discovery phase (with a new module), a polling phase (again with a new module) and create new WebUI to display this data.
OSPF neighbors are an example of this “Component” usage.
Just a tip: If you want to add ONU data (sensors, interfaces, etc) I would make that optional creating a module.
Why? Think in a OLT with, lets say, 300 ONUs. That means you will have a device overview with 300+ sensors that will need to load. And now think in a OLT with 3k ONUs.
I dont own a ZTE but Huawei ones. In my case, polling ONU info would multiply no less than x10 my current sensor count in LibreNMS. And thats only with 1 sensor (ONU RX).
Hi Guys!, thanks for your comments!, so, I need only to graph bandwidth for ONU. could you give a example how I need to configure the template to do it please?, Right now I am using Cacti, but I need to improve discovery ONU, because I am configuring one by one ONU OID (Tx, Rx) .
Here my test code file over root of librenms install, don’t want to PR, cause ugly and snmp problems on devices
But ZTE C320 has very slow CPU and VERY SLOW AND BUGGY snmp replies… So i disappointed in these devices…
This can work normaly on small count of ONT/ONU on OLT…
Device needs SNMP data caching on firmware level,or may be spike-nails in PHP code, to to align received or non-received data)
Hi, can I get your code? because this link is not valid anymore. I have this device but after add to Librenms only show basic information such as system up, location, sysname.