Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Hey all, I'm getting more and more devices set up in Nagios but I've hit yet another snag. Almost all of my ProLiant servers have the following OID as the Array Controller status:
CPQIDA-MIB:cpqDaCntlrCondition
OID 1.3.6.1.4.1.232.3.2.2.1.1.6
Type INTEGER
Units
Access read-only
Status mandatory
The condition of the device. This value represents the overall
condition of this controller , and any associated logical drives ,
physical drives , and array accelerators.
Possible Values :
other(1)
ok(2)
degraded(3)
failed(4)
I say almost because I have four ProLiant DL360 G5 servers that show the following error:
Everything else is working. I'm using a mib browser to pull the Array Controller status out of my G5s and I get the same OID. Has anyone else had this same problem? If so how have you gotten your information out of the servers?
Have you tried to get this particular OID manually by snmpget ?
Most possibly, these older servers keep older Firmware, and don't have this OID at all.
1) I didn't realize that snmp was so tightly intertwined with the OS. I ran the snmpget command on the following four servers and three of them gave me different responses:
[root@link objects]# snmpget -v 2c -c public 192.168.2.30 1.3.6.1.4.1.232.3.2.2.1.1.6.0
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-SMI::enterprises.232.3.2.2.1.1.6.0
[root@link objects]# snmpget -v 2c -c public 192.168.2.38 1.3.6.1.4.1.232.3.2.2.1.1.6.0
SNMPv2-SMI::enterprises.232.3.2.2.1.1.6.0 = No Such Instance currently exists at this OID
[root@link objects]# snmpget -v 2c -c public 192.168.2.39 1.3.6.1.4.1.232.3.2.2.1.1.6.0
SNMPv2-SMI::enterprises.232.3.2.2.1.1.6.0 = No Such Instance currently exists at this OID
[root@link objects]# snmpget -v 2c -c public 192.168.2.207 1.3.6.1.4.1.232.3.2.2.1.1.6.0
SNMPv2-SMI::enterprises.232.3.2.2.1.1.6.0 = No Such Object available on this agent at this OID
[root@link objects]#
2) I have a couple of older (eight years old) ProLiant servers and THEY give me the correct response: