For obvious reasons, the first checks that we developed primarily monitored volumes and aggregates. The overall method took the approach of sending an UNKOWN alarm if no volumes or aggregates could be found – since it is very unusual to find a filer without any aggregates or volumes. The same overall library was then …
Today we announce a new check NetInterface which monitors the Is-Home flag of a network interface and sends an alarm if current-port differs from home-port. This enables us to monitor the output of the following CLI command in a continuous and automated way: clu1::> network interface show -is-home false Logical …
Since support for version 2.x will run out at the end of 2015, a number of checks that have not been replaced yet in the new version check_netapp_pro (3.x) will no longer be available: e.g. Hardware check, which has only been replaced partially (for instance, by Disk ). Now, with check_netapp7_head.pl, it is possible …
In order to verify a filer’s _system health status, _we now provide a new check: check_netapp_health.pl. It returns a warning message if the status of Seven and Cluster Mode filers deviates from “OK”. $ ./check_netapp_health.pl -H your-filer OK - system health status is ok. This check is included in …
Up until now, the Disk Check was used to inspect the failed (or offline) attribute of disks. Unfortunately in cluster mode, this caused disks that did not belong to an aggregate to be skipped and thus not to be checked. Therefore, we have extended the check as follows: Failed disks will always be reported as such, …
Unassigned disks currently cause the Disk Getter to crash. We have already developed a fix for this problem. At the same time, the check **Disk **can be used to check for unassigned disks: $ **./check_netapp_pro.pl Disk ‑H fasdc_cluster ‑‑what=unassigned** NETAPP_PRO DISK WARNING - 192 disks checked, 0 critical and 1 …
Checks such as Disk or ShelfBay have very long outputs with (depending on the configuration of the filer) long lists of instances even when everything is perfectly fine. At first, this might seem a bit confusing, but the checks can be configured according to your needs. Let’s take a look at an example with a very …
An existing installation of checks can be replaced by a newer version quite easily as long as it is the same product, e.g.: check_netapp 2.1.0 by check_netapp 2.2.5. Equally, the same holds true for the pro version (e.g. check_netapp_pro 3.0.17 by check_netapp_pro 3.1.0). In these cases the update is nothing else than …
Beginnend mit DataONTAp 8.2.1 verschwindet das bisher für die Prüfung der Netzwerkperformance verwendete Objekt ifnet für cluster-mode. Stattdessen steht nun das Performanceobjekt lif zur Verfügung. Da sich auch bei den Countern einiges verändert hat, stellen wir mit dem nächsten Release gleich einen neuen, …