Open for Voting

Add Juniper alarm monitoring to hardware health status

Juniper devices have red and yellow alarms that indicate various conditions (ie booted from backup partition) and both yellow and red alarms can be monitored via snmp. I currently have custom pollers doing the work for me, and get alerted when a red or yellow alarm happens. But it would be good to have that integrated into NPM's hardware health monitoring for Juniper devices.

For those interested in doing this through a UDP as well:

jnxRedAlarmState (OID: 1.3.6.1.4.1.2636.3.4.2.3.1)

jnxYellowAlarmState (OID: 1.3.6.1.4.1.2636.3.4.2.2.1)

is what you're after.  Use a raw value for MiB value type, format is enumeration (map values: 0=other, 1=off, 2=on), snmp get type=get next.



  • I've love to have the ability to easily monitor a virtual chassis' overall status.

    We've had a number of EX3300's, for example, space out on certain firmware that would cause the CPU of one or more members to peg 100%, but that act never triggers an alarm on the virtual chassis. It would render one or more of the switch members unusable. We'd have no way of knowing unless we SSH into the virtual chassis and see the affected member list as "unknown" or "missing". The VC status isn't presented in an SNMP OID (that I could find anyways). I've not been able to create a custom view to show FRU status, but it's been impossible (for me) to turn that view into an actual alert as the FRU status only show functioning members at the time of polling - it never shows the status of missing or non-reporting members.

    Definite upvote here!