Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
Check_netapp3
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
An updated version of the original check_netapp and check_netapp3 scripts written in perl.
Similar to its predecessor, it can check netapp SNMP status on a number of variables. The logic has been revamped and the script set to allow for simple expansion of new checks (like qtree status)
Inside the script is a hash of hash that stores all the config data for the variable to check.
Similar to its predecessor, it can check netapp SNMP status on a number of variables. The logic has been revamped and the script set to allow for simple expansion of new checks (like qtree status)
Inside the script is a hash of hash that stores all the config data for the variable to check.
Reviews (4)
byelasticworms, April 1, 2019
How can have the result of check DISKUSED64 in GB or TB ?
byffranco, April 9, 2012
All the checks are great. I've been using it for a week now and replaced all my other checks to NetApp appliances. However, the only problem I see is NVRAM. According to the MIB file, a value of 0 and 9 are good. Anything between is not good. I haven't found a way to get an ok back if the values 0 and 9 are reported.
I tried to use the NAGIOS standard of -c 2:8 but I don't see it working. Has anybody run into this and been able to overcome it?
Here is what the MIB for NetApp reports.
ok(1),
partiallyDischarged(2),
fullyDischarged(3),
notPresent(4),
nearEndOfLife(5),
atEndOfLife(6),
unknown(7),
overCharged(8),
fullyCharged(9)
I tried to use the NAGIOS standard of -c 2:8 but I don't see it working. Has anybody run into this and been able to overcome it?
Here is what the MIB for NetApp reports.
ok(1),
partiallyDischarged(2),
fullyDischarged(3),
notPresent(4),
nearEndOfLife(5),
atEndOfLife(6),
unknown(7),
overCharged(8),
fullyCharged(9)
byrrobert, August 25, 2011
Comment out the "use warnings;". Ran fine from the command line, but with both that and "use strict;" as a Nagios plug-in it returned the error, "(Service check did not exit properly)."
