We have released the version 2.0.0 of our Check NetApp-REST product – a collection of modern go-coded Nagios-compatible monitoring checks based on NetApp’s RESTful API.
New The aggregate-check has got the long awaited usage and free subcommands. (Until now check_netapp_aggregate was a special check for …
The RESTful Spare-Disk Check has got subcommands for checking both spare-disks and spare-partions.
Example for checking spare-disks ./check_netapp_spare disk -H filer NETAPP_PRO SPARE OK - 28 disks checked ... Checks all nodes for sufficient spare-disks.
Example for checking spare-partitions ./check_netapp_spare …
The family of Check NetApp REST monitoring plugins has grown. With the check_netapp_disk container-type plugin the storage admin has a constant eye on disks that have been moved into unwanted containers.
Let’s look at an example:
.$ check_netapp_disk container-type -H sim96 NETAPP DISK CONTAINER TYPE OK - 28 …
3.4.1_01 FIXES USAGE/SHELF-ENVIRONMENT, DISKCOUNT, WORKLOAD, LUNSIZE Released 2016-03-18
Fixed Usage-Check: Handling of volumes with no state-attribute shelf-environment-object in cm-getter needs a node-name (sometimes) New and improved new DiskCount check (counts spare-disks per type or storage-pool) new …
Our new DiskCount check counts available disks on a system. This can be quite handy when setting a filter, e.g. only counting SSD drives in the spare container. This way, one can use thresholds to send warning messages as soon as the number of spare SSD disks falls below a certain threshold. In contrast to the …
Our Disk check is going to have a new feature. Using the switch ‑‑what=non-zeroed-spare an alarm is sent as soon as non-zeroed spare disks have been found. Depending on wether the zeroing process is currently running or not, a WARNING (including progress) will be sent or else CRITICAL.
There are two different ways of monitoring the 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 …