Karsten Suehring <[email protected]> writes: >> snmpwalk -v2c -c <community> <host> 1.3.6.1.4.1.674.10892.1.600.30.1 > > On the upgraded system I get the following: > > Cannot find module (LM-SENSORS-MIB): At line 0 in (none) > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.1.1.1 = INTEGER: 1 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.2.1.1 = INTEGER: 1 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.3.1.1 = INTEGER: 0 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.4.1.1 = INTEGER: 1 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.5.1.1 = INTEGER: 2 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.7.1.1 = INTEGER: 26 > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.8.1.1 = STRING: "System Board > System Level" > SNMPv2-SMI::enterprises.674.10892.1.600.30.1.15.1.1 = INTEGER: 0 > > On the not upgraded system I only get the error message > > Cannot find module (LM-SENSORS-MIB): At line 0 in (none)
Aha... so with firmware 1.33, the OIDs for power monitoring are not present at all, but with firmware 1.54 they are partly present. The status of the probe (10892.1.600.30.1.5.1.1) is "2", which corresponds to "Unknown". The plugin translates this to "Critical" in Nagios. We're obviously dealing with a corner case here. I wonder if this behaviour is a bug in OMSA. I have added some code in the plugin to handle this situation. If the status is "Unknown", reading is unavailable and checking is done via SNMP, the plugin will ignore the probe completely. This has been added to the beta version available here: http://folk.uio.no/trondham/software/check_openmanage.html#download Please give it a try and let me know if this resolves the issue for you. Regards, -- Trond H. Amundsen <[email protected]> Center for Information Technology Services, University of Oslo _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
