monitoring
monitoring copied to clipboard
script failing: check_cisco_nexus_hardware.pl not supported oid 1.3.6.1.4.1.9.9.91.1.2.1.1.4
Hi David
check_cisco_nexus_hardware.pl failing to get info on getting info for few, further verified from cisco that oid 1.3.6.1.4.1.9.9.91.1.2.1.1.4 is not supported as of now.
ciscodev.example.com: CRITICAL (12 sensors failed on 394, 0 fan failed on 38, 0 psu failed on 36) OK: dBm (Ethernet1/32(Rx-dBm)) is failed: 0milli dBm is less than 2999 OK: dBm (Ethernet3/15(Rx-dBm)) is failed: 0milli dBm is less than 2999 OK: dBm (Ethernet1/31(Rx-dBm)) is failed: 0milli dBm is less than 2999 MAJOR: amperes (Ethernet1/31(ampere)) is failed: 0milli amperes is less than 11800 MAJOR: amperes (Ethernet3/15(ampere)) is failed: 238milli amperes is less than 11800 OK: dBm (Ethernet1/32(Tx-dBm)) is failed: 0milli dBm is less than 2699 OK: dBm (Ethernet3/15(Tx-dBm)) is failed: 0milli dBm is less than 2699 MAJOR: dBm (Ethernet1/31(Tx-dBm)) is failed: -17695milli dBm is less than 2699 OK: dBm (Ethernet3/16(Rx-dBm)) is failed: 0milli dBm is less than 2999 MAJOR: amperes (Ethernet1/32(ampere)) is failed: 210milli amperes is less than 11800 MAJOR: dBm (Ethernet3/16(Tx-dBm)) is failed: -20969milli dBm is less than -7304 MAJOR: amperes (Ethernet3/16(ampere)) is failed: 0milli amperes is less than 11800 | Ethernet1/17(ampere)=8528amperes;;;;
Hi,
As of #9 , I have no access to any Cisco Nexus right now. However, if you feel comfortable with development, you can send me PR. I will be happy to merge.
David
Well this has been around a while. How do we determine status of a check if they no longer support retrieval of hardware-defined thresholds for each value..?
We have chosen to ignore sensors of type 14, dbm, and type 5, ampere. Being the hackiest way to silence this particular type of annoyance. :)