search

district09 / check_netapp_ontap

:four_leaf_clover: Check NetApp Ontap :four_leaf_clover:
https://outsideit.net/monitoring-netapp-ontap/
GNU General Public License v3.0
39 stars 28 forks source link

netapp_alarms and root aggregate usage #14

Open johnzimm opened 8 years ago

johnzimm commented 8 years ago

I've configured the netapp_alarms check and the root aggregates are always making this check critical. They are always 95% on the filer and do not grow.

Can the root volume space be excluded from the check?

Napsty commented 8 years ago

I have the same problem. 

./check_netapp_ontap.pl -H netapp -u monitoring -p secret -o netapp_alarms
inf-stormgm02-p/aggr_inf_stormgm01_p_root/aggregate_used 95%, inf-stormgm03-p/aggr_inf_stormgm02_p_root/aggregate_used 95%

A workaround would be to exclude them with the -m parameter:

./check_netapp_ontap.pl -H netapp -u monitoring -p secret -o netapp_alarms -m exclude,inf-stormgm03-p/aggr_inf_stormgm02_p_root/aggregate_used,inf-stormgm02-p/aggr_inf_stormgm01_p_root/aggregate_used
OK - No problems found (0 checked)

But I'm not sure if this prevents the check of working correctly? Because right now I have a failed disk:

./check_netapp_ontap.pl -H netapp -u monitoring -p secret -o disk_health
1.11.11 state is failed

Isn't "netapp_alarms" supposed to show that too? Or what exactly is netapp_alarms supposed to be reporting?

MarcusCaepio commented 5 years ago

-m exclude,root should also work