check_snmp unable to return GAUGE32 from HPE SAN

[Ulfandu]

Hello everybody,

I'm trying to use Nagios Core to monitor a HPE StoreVirtual 3200 SAN via check_snmp, spesifically, I want to monitor the amount of memory that the device is utilizing. I've acquired the correct MIBs from HPE's website (in relation to the device's firmware version) and I've moved them to /usr/share/snmp/mibs/ with correct permissions.

I know that monitoring the RAM is possible, because HPE informed me with an email, that by updating the firmware it would be possible:



When using a free MIB explorer, I was able to the OID that I was looking for:



However, I cannot fetch this using check_snmp for some reason. I'm a little rusty with OIDs, so I tried adding a zero to the end:

Code: Select all

[root@nagios libexec]# ./check_snmp -H 192.168.1.10 -o .1.3.6.1.4.1.9804.3.1.1.2.15.2.1.51 -C testsnmp -m ALL -vvv
/usr/bin/snmpget -Le -t 10 -r 5 -m ALL -v 1 [context] [authpriv] 192.168.1.10:161 .1.3.6.1.4.1.9804.3.1.1.2.15.2.1.51
External command error: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: LEFTHAND-NETWORKS-NSM-NOTIFICATION-MIB::lhnMemoryUtilization

Code: Select all

[root@nagios libexec]# ./check_snmp -H 192.168.1.10 -o .1.3.6.1.4.1.9804.3.1.1.2.15.2.1.51.0 -C testsnmp -m ALL -vvv
/usr/bin/snmpget -Le -t 10 -r 5 -m ALL -v 1 [context] [authpriv] 192.168.1.10:161 .1.3.6.1.4.1.9804.3.1.1.2.15.2.1.51.0
External command error: Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: LEFTHAND-NETWORKS-NSM-NOTIFICATION-MIB::lhnMemoryUtilization.0

In addition to all that, there is another Memory OID which works fine but it returns a STRING and not an integer value so I can't make Nagios send an alert if a certain threshold is reached:



And it works fine:

Code: Select all

[root@nagios libexec]# ./check_snmp -H 192.168.1.10 -o  .1.3.6.1.4.1.9804.3.1.1.2.1.40.0 -C testsnmp -m ALL
SNMP OK - Memory-Utilization=89.2169% |

Any help would be much appreciated as I have to make this work one way or another.

[cdienger]

Regarding the first issue, a snmpwalk may be helpful here finding the proper OIDS:

Code: Select all

snmpwalk -v1 -c testsnmp 192.168.1.10 .1.3.6.1.4.1.9804

For the second issue, I think you'll need to use a script to wrap the check and parse out the information you need and check the thresholds. /usr/local/nagios/libexec/utils.pm and utils.sh can be imported into scripts to take care of handling thresholds.

[Ulfandu]

Hi, I did the SNMPWALK command and could not find the OID I was looking for. As I turns out, the OS' version was not recent enough for it to contain the OID. The required OS version was 13.6.00.0275 and the one we have is 13.6.00.0241.0.

I will return to this matter after the device has been updated.

[cdienger]

Sounds good!