NetApp’s ZAPI interface (now called ONTAPI) will reach end of availability (EOA) in January 2023. Therefore the checks from Check NetApp-ZAPI won’t be of much use in the near future. Fortunately all customers for Check NetAppPRO can use the future-proof Check NetApp-REST with the same license and therefore …
The
check_netapp_volume usage command understands relative thresholds in percent as well now …
The v1.2.0 release of our Check NetApp-REST product contains a new monitoring plugin called check_netapp_volume usage. It provides the monitoring of:
the used space of each volume (in Bytes) the total used space of several volumes the average used space of several volumes the min/max of used space of several volumes A …
The first stable release (v1.1.0) of our brand new Check E-Series product brings an automated health check for e-series nodes.
check_eseries_health will run the health checks regularly and automatically report any errors found.
Example $ ./check_eseries_health --host=10.1.1.125 --system-id 1 [...] NETAPP ESERIES HEALTH …
Since 4.0.0 every over-all check has a feature, which we call “instance-name contains node-name”. We have introduced this as an replacement for the sporadic available --node|--vserver parameter (not available any more). So since then each instance-name has the name of its node prefixed. This allows to use …
The 5.3.0 version, released yesterday includes a new check to monitor the EMS(Event Management System)-Logfile. This allows several new checks among them one to send an alarm, if an unusal high number of autogrow-events take place.
Let’s have some examples:
# check myfiler for autoSize events and alarm according …
Our quite new SnapCenter check can filter for resource-groups and policies. Until now one had to precisely define which resource-groups should get checked.
In some situations the resource-group name changes. To allow checking such resource-groups without having to constantly change the filters in the service-check …
We have one report, that changing the setup from a chain setup (netapp01 → netapp02 → netapp03) to a star setup (netapp01 → netapp02 ➕ netapp01 → netapp03) makes stoping some collectors (e.g. get_netapp_cm.pl) with an error of “Instance ‘NETAPP01-SVM01:NETAPP01_SVM01_xxxx01_vol’ already exists - can …
We are happy to announce that the next major release of check_netapp_pro is now available on the Q-Portal for download.
The breaking changes for this release are:
A new directory layout which will ease the creation of RPM-packages. Also we have introduced a new getter for DataONTAP 9.7s new API plus several new checks. …
The new UnprotectedVolume check searches for volumes not protected by a SnapMirror.
An alarm is generated if one or more unprotected volumes are found. Specific volumes and vservers can be checked by using the standard check_netapp_pro --include= and --exclude= arguments. A simple example follows using the default …