I am trying to monitor my netapp 2240 using the check-netapp-ng.pl plugin. I have been able to successfully get notifications when a volume it beyond the configured thresholds and nagios shows the current CPU usage and failed disk as 0. Everything appears to be setup correctly, yet when I pull a disk out of my netapp, nagios does not send any notification that a disk has failed. the failed disk monitor continues to report FAILEDDISK as 0. The last time I pulled a disk to test nagios alerts Netapp sent us a new disk within 2 hours, so I know that the system is recognizing the disk as failed and sending an alert to netapp, just not sure why nagios is not picking up on the failure. Below is the alert I have configured in commands.cfg:
define command{
command _name check_netapp_fd
command_line /usr/bin/perl5.13.2 $USER1$/check-netapp-ng.pl -H $HOSTADDRESS$ -T FAILEDDISK -C public
}
and the service:
define service{
use local-service
host_name NETAPP01
service_description Failed Disk
check_command check_netapp_fd
}
Appreciate any suggestions
Thank you
PT
monitoring netapp fas2240
Re: monitoring netapp fas2240
Lets check the oid for FAILEDDISK from the script with snmpget from the XI cli:
(replace "<ip of netapp device>" with your netapp device's ip . . .
If you do not have snmpget:
Code: Select all
snmpget -v1 -c public <ip of netapp device> 1.3.6.1.4.1.789.1.6.4.7.0If you do not have snmpget:
Code: Select all
yum install net-snmp-utilsFormer Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
Re: monitoring netapp fas2240
Thank you for your input. I ran the command you suggest and this is the response:
SNMPv2-SMI::enterprises.789.1.6.4.7.0 = INTEGER: 0
SNMPv2-SMI::enterprises.789.1.6.4.7.0 = INTEGER: 0
Re: monitoring netapp fas2240
So it is returning zero. Try pulling the disk again and rerunning the command from the cli. If it still reports "0", then it is a problem with the device not correctly reported the change in the FAILEDDISK value.
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.