Nagios Support Forum

I can do this with my own scripts but was wondering if one of the SNMP monitoring wizards would simplify this.

I have Juniper switch gear and I'm trying to monitor the state of components like fan, Power supplies...
This MIB has the information

https://oidref.com/1.3.6.1.4.1.2636.3.1.13.1

snmpwalk -v3 -auth info removed- 10.36.112.133 .1.3.6.1.4.1.2636.3.1.13.1.5
JUNIPER-MIB::jnxOperatingDescr.1.1.0.0 = STRING:
JUNIPER-MIB::jnxOperatingDescr.2.1.1.0 = STRING: Power Supply: Power Supply 0 @ 0/0/*
JUNIPER-MIB::jnxOperatingDescr.2.1.2.0 = STRING: Power Supply: Power Supply 1 @ 0/1/*
JUNIPER-MIB::jnxOperatingDescr.4.1.1.1 = STRING: FAN 0 @ 0/0/0
JUNIPER-MIB::jnxOperatingDescr.4.1.2.1 = STRING: FAN 1 @ 0/1/0
JUNIPER-MIB::jnxOperatingDescr.7.1.0.0 = STRING: FPC: EX4300-32F @ 0/*/*
JUNIPER-MIB::jnxOperatingDescr.8.1.1.0 = STRING: PIC: 32x 1G SFP, 4x 1G/10G SFP/SFP+ @ 0/0/*
JUNIPER-MIB::jnxOperatingDescr.8.1.2.0 = STRING: PIC: 2x 40GE QSFP+ @ 0/1/*
JUNIPER-MIB::jnxOperatingDescr.9.1.0.0 = STRING: Routing Engine 0

snmpwalk -v3 -auth info removed- 10.36.112.133 .1.3.6.1.4.1.2636.3.1.13.1.6
JUNIPER-MIB::jnxOperatingState.1.1.0.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.2.1.1.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.2.1.2.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.4.1.1.1 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.4.1.2.1 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.7.1.0.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.8.1.1.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.8.1.2.0 = INTEGER: running(2)
JUNIPER-MIB::jnxOperatingState.9.1.0.0 = INTEGER: running(2)

If I run this through the SNMP walk wizard by specifying .1.3.6.1.4.1.2636.3.1.13 as the filter OID, the wizard breaks these all out as individual OIDs. I can select the appropriate jnxOperatingState OID and set the label to the related jnxOperatingDescr string, but then it still wants warn/critical thresholds when this is table of good and bad values.

{unknown(1),
running(2), -- up and running, as a active primary
ready(3), -- ready to run, not running yet
reset(4), -- held in reset, not ready yet
runningAtFullSpeed(5), -- valid for fans only
down(6), -- down or off, for power supply
standby(7)} -- running as a standby backup

Better way to do this?

Thanks,

Dave

Hi Dave,

If you're looking to match values like you're describing you will likely want to change the TYPE dropdown on the OID you're selecting within the SNMP Walk Wizard. If you change the Type to String you can enter a literal value that you want to match against. The check result will return OK if it matches what you enter here.

Let us know if this doesn't quite do what you're trying to accomplish.

As an addition, I would suggest updating to the latest XI release, 2026R1.5. This version introduces a bunch of quality of life improvements to the SNMP Walk Wizard specifically.

I am testing with 2026R1.5.

Yes, if I change the type to string I can specify running(2) as the match and it should come up OK. This doesn't help with multiple "good" status options like running(2) or standby(7). Also I just did this with 2026R1.5 and it looks like it wrote the config check_xi_service_snmp check command to the config with the -r flag rather than -s for string matching.

I was actually hoping it would correlate the various indexes like the network switch/router wizard does for network interfaces but that might be asking too much

Thanks,

Dave

Dave, how many "bad" statuses are there in this case?

I dug up the documentation on the check_snmp plugin and it looks like you're technically right, we are using -r instead of -s for string matching. "-r" is for regex matching though, which should allow you to actually check for multiple different string values with the right regex.