Hello,
I’v been testing LibreNMS for a 6 months now and among other things i’v been monitoring couple of Nokia ISAM. Some of them with thousands of customers and some with only few hundreds.
Lately i discovered that LibreNMS puts a lot of “pressure” on the ISAM and causes sluggish reponse in the CLI. I use default 5 min polling. I have also used config.php to exclude interfaces that are not of interest to me.
Has anybody else experienced this and do you have any suggestion what to do?
Among other things, I’m monitoring 2 geographically separate 7342 ISAM deployments. One has 3 OLT shelves, the other has 7 OLT Shelves. Polling takes forever. I’m still pretty new to Libre. I need to slim it down a lot. We have a similar issue with monitoring/polling our Calix E7-2 shelves, which is similar in functionality.
I don’t have a suggestion for you, but I’m looking for some recommendations myself. Right now, I’m going to just add the shelves as Ping Only device. Eventually I’ll turn on selected port polling and enable the important ports.
I can let you know on that. We had the Nokia ISAM monitored by PRTG for years. It worked, but we’ve recently implemented Libre and I just added the ISAM shelves in (w/full discovery and polling) earlier this week. They kept setting off the +5min polling time alerts. I’ve deleted them and readded as ping only devices for today. I will see if the cli performance and cpu usage goes up after I start adding more sensors in.
I have added a pull request for the SNMP monitoring of the two contexts (ihub and nt). With this pull request you can also walk the SNMP ports that are in the ihub context next to the more generic chassis and pon ports that are in the nt context:
You can just add a Nokia ISAM to the Gui as a Device (Using SNMPv2/v3). This is the SNMPv3 example of how to configure the ISAM to allow to read all contexts (ihub/nt):
! Configure SNMPv3
configure system security snmp view MONITORING_READ subtree * type include
configure system security snmp view MONITORING_WRITE subtree * type exclude
configure system security snmp group MONITORING security-level privacy-and-auth context all read-view MONITORING_READ write-view MONITORING_WRITE
configure system security snmp user LIBRENMS authentication sha1:plain:<SNMPv3_AUTH> privacy aes-128:plain:<SNMPv3_PRIV>
configure system security snmp map-user-group LIBRENMS group-name MONITORING
!