There are two different ways of monitoring health states of a NetApp filer:

  • check_netapp_pro.pl Head -H <filer> -o health monitors the health state of a cdot filer, using the data from the getter of the head object. This means that there is no need for further requests to the filer. There is however a short delay between the time of the health-state changing and the time of warning (the delay depending of the frequency of the getter, i.e. the interval of the getter check and the interval of the actual check).
  • check_netapp_health.pl inspects the health state for 7mode as well as cdot filers.  This check contacts the filer directly. Therefore in some cases, it send warnings more quickly than the head check described above.

In both cases some uncertainties may arise concerning which results on a NetApp filer is influencing its health state. There is no definitive answer to this issue. For instance, a spare-low condition on a 7mode system results in a warning for the health status, but not for a cdot system. An aggregate with status degraded does not affect the health status in any system.

Therefore, our recommendation: treat the health check exclusively as a supplement, and monitor all relevant values and status using specific checks.

Example

In order to get alerted about a lack of spare disks in an aggregate, these two checks have to be configured:

This applies for 7mode and cdot filers.

Additionally, check_netapp_health (7m or cdot) or Head -o health (only cdot) can be configured as well.