Check for volumes snapshot-policy?

check_netapp_pro already provides a way to flag volumes which do not have snapshots at all. The check SnapshotLessVolume just looks for the size used by snapshots and if that size is equal to 0 it will raise an alarm. Lately, while working on a check for snapmirrors, I found some attributes from which we could derive and check the snapshots policy name and the number of snapshot copies in the volume.
Read full post

Check for Offline or Failed Disks

The new **Disk **check monitors the disks of a NetApp Filer. Depending on the settings, the check sends an error message when offline or failed disks are found. An example using a 7-Mode Filer: $ **./check_netapp_pro.pl Disk -H sim812 ‑‑what=failed** NETAPP_PRO DISK CRITICAL - 14 disks checked, 1 critical and 0 warning. sim812 v5.16: not failed sim812 v5.17: not failed sim812 v5.18: not failed sim812 v5.19: not failed sim812 v5.21: not failed sim812 v5.
Read full post

Collector Architecture

Turning Off Performance Data Output | Monitoring NetApp - Jan 3, 2015 […] a check for each volume that outputs performance data and the corresponding graph. Thanks to the collector architecture no additional requests have to be sent to the […] #### [Collectors and Distributed Monitoring | Monitoring NetApp](https://blog.monitoring-plugins.pro/posts/collectors-and-distributed-monitoring/ "") - Jan 4, 2015 […] Collectors have some great advantages: the monitored device is put under less computational load and a greater flexibility for the configuration of service checks.
Read full post

Collector Architecture

Our present monitoring-plugin for NetApp FAS devices, named check_netapp_pro is based on the so-called collector architecture. This allows us to monitor even the most complex storage-systems like Fabric Metro Clusters. The collector architecture works as follows: Collectors are distinct scripts that collect all the data that the checks require and saves it in a Store on the Nagios Server. The checks have access to the Store and no longer contact the NetApp devices themselves.
Read full post