Uninett / nav

Network Administration Visualized
GNU General Public License v3.0
194 stars 39 forks source link

Monitor Juniper Virtual Chassis members #2249

Open lunkwill42 opened 3 years ago

lunkwill42 commented 3 years ago

Is your feature request related to a problem? Please describe. Juniper devices can be stacked into a virtual chassis. NAV cannot detect the VC members or outages thereof.

Describe the solution you'd like NAV should be able to detect a Juniper device operating as a VC, listing the member devices with their serial numbers, and to send chassisState alerts on member outages.

This type of monitoring is already supported for stacks that report these details through the ENTITY-MIB, but Juniper only has partial support for this MIB. The proprietary MIB needed to support this enhancement is the JUNIPER-VIRTUALCHASSIS-MIB

Describe alternatives you've considered Juniper supports ENTITY-MIB (partially) on some platforms, and should potentially be able to report the necessary details to NAV without changes. In practice, however, VC information does not seem to be present in Juniper's implementation of the MIB, so it is useless for this purpose.

lunkwill42 commented 3 years ago

I'm working on an implementation using JUNIPER-VIRTUALCHASSIS-MIB, but it seems the Juniper switches we're testing on will actually provide the necessary information in ENTITY-MIB.

However, the latter implementation reports the stack members as modules in a chassis, rather than as multiple chassis in a stack. It's not exactly the model we are looking for, but it is already supported by NAV, and will ensure an alert is dispatched if a stack member goes missing.

However, it isn't clear that detecting missing members will cover all failure scenarios. Some failures will have a stack member malfunction, but still be detected as present. It is not yet clear how such a malfunction could be detected in a Juniper Virtual Chassis.

We're blocked, waiting for further analysis in the event of the next VC production failure experienced by the CNaaS NOC team...