mirror of
https://github.com/librenms/librenms.git
synced 2024-10-07 16:52:45 +00:00
4c14efb375
* Fix routing engine discovery on standalone JunOS devices In #9426, the sensor discover code was replaced with YAML. Unfortunately it treats the FRU table as standalone OIDs, and did not implement the filtering that was present in the original code. This change causes LibreNMS to fully walk the FRU table, which allows us to silence alerting on devices with an 'unknown' status. Without this change, standalone devices have a spurious routing engine with state 1, which triggers false harware failure alerts. As we're changing the name of the sensors, this causes a loss of sensor history. This has been brought up on community a couple of times: https://community.librenms.org/t/juniper-qfx-routing-engine-state-alert/6152 https://community.librenms.org/t/spurious-failed-routing-engine-from-some-junos-devices/6208 * Update test data * Update test data * Update test data * Update test data * This syntax works, but fails linting