Page 1 of 1

DataPower Device Monitoring using Nagios

Posted: Wed Oct 17, 2018 4:08 pm
by vy3734
Hi,
We are trying to monitor the datapower devices using snmpwalk. I've added the below command to the commands.cfg file and passing the host address and the MibName. The command is as follows:
/usr/bin/snmpwalk -On -v 2c -c public $HOSTADDRESS$ -m /usr/share/snmp/mibs/drStatusMIB.txt $MibName.
The output of the above command when 'dpStatusTemperatureSensorsTable' mib name is provided is as follows:
[nagios@NagisosServer static]$ /usr/bin/snmpwalk -On -v 2c -c public DataPowerDevice -m /usr/share/snmp/mibs/drStatusMIB.txt dpStatusTemperatureSensorsTable
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = STRING: Temperature CPU1
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = STRING: Temperature CPU2
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = STRING: Temperature Inlet 1
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = STRING: Temperature Inlet 2
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = STRING: Temperature Outlet 1
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = STRING: Temperature Outlet 2
.1.3.6.1.4.1.14685.3.1.141.1.1.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = STRING: Temperature System Ambient
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = INTEGER: 16 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = INTEGER: 14 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = INTEGER: 20 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = INTEGER: 17 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = INTEGER: 21 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = INTEGER: 21 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.2.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = INTEGER: 25 Degrees C
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = INTEGER: 85
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = INTEGER: 85
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = INTEGER: 52
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = INTEGER: 52
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = INTEGER: 62
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = INTEGER: 62
.1.3.6.1.4.1.14685.3.1.141.1.3.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = INTEGER: 57
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = INTEGER: 90
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = INTEGER: 90
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = INTEGER: 62
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = INTEGER: 62
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = INTEGER: 72
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = INTEGER: 72
.1.3.6.1.4.1.14685.3.1.141.1.4.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = INTEGER: 67
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.5.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = INTEGER: ok(4)
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.49 = INTEGER: 88
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.67.80.85.50 = INTEGER: 88
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.49 = INTEGER: 58
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.73.110.108.101.116.32.50 = INTEGER: 58
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.49 = INTEGER: 68
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.79.117.116.108.101.116.32.50 = INTEGER: 68
.1.3.6.1.4.1.14685.3.1.141.1.6.84.101.109.112.101.114.97.116.117.114.101.32.83.121.115.116.101.109.32.65.109.98.105.101.110.116 = INTEGER: 63

Attached the Nagios output also.
We want to know if nagios is capable of providing a table view as in the attached screenshot and also if the existing check we setup will alert if any of the OK's will turn to FAIL.

Thanks!!

Re: DataPower Device Monitoring using Nagios

Posted: Wed Oct 17, 2018 4:19 pm
by npolovenko
Hello, @vy3734. No, Nagios will not be able to recognize and send a notification if any OK result changes to Fail. You need to find or write a script that will parse the snmp walk output and exit with a critical code(2) if something is in a failing state. I highly recommend looking on the http://www.nagiosexchange.com for already existing plugin written for your device.

Re: DataPower Device Monitoring using Nagios

Posted: Mon Oct 22, 2018 8:48 am
by vy3734
Thanks for the clarification. Much appreciated!

Re: DataPower Device Monitoring using Nagios

Posted: Mon Oct 22, 2018 1:40 pm
by benjaminsmith
Hi @vy3734,
Thanks for the clarification. Much appreciate
Do you have anymore questions, or can we close the forum topic? Please let us know.