Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

netapp_alarms and root aggregate usage #14

Open
johnzimm opened this issue Jan 12, 2016 · 2 comments
Open

netapp_alarms and root aggregate usage #14

johnzimm opened this issue Jan 12, 2016 · 2 comments

Comments

@johnzimm
Copy link

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
Copy link
Contributor

Napsty commented Jun 16, 2016

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
Copy link

-m exclude,root should also work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants