As of release 3.5.0 it will be possible to configure checks so that the non-existence of instances does not trigger an alarm. The default configuration won’t change, meaning that an UNKNOWN will still be sent when the performance getter (performance collectors) don’t find volumes, disks, luns, etc… …
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 …
The --no_instances=OK switch has been available for some time now. It prevents for example a LUN check that can’t find any LUNs with a not always matching UNKNOWN not to seek any unneeded attention. Recently, we received an increasing number of requests that express the desire for such a switch for collectors …
Current versions of check_netapp_pro.pl ignore the --timeout|-t parameter (which limits the runtime of the check). This only affects checks listed with check_netapp_pro.pl. Getter and setter and stand-alone checks are not affected. Since** check_netapp_pro.pl reads data from the local stores, timeouts very rarely …
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 …
_Unknown _volumes are currently not supported by the Usage plugin included in version 3.4.0. As a workaround we recommend excluding the respective volumes via the X switch after having verified their unknown state using -explore. As of the next release (3.4.1) the plugin will skip unknown volumes (and outputs the …
Not every Server with a stopped operational state should always be marked as critical. With the next release we are adding the possibility to set the option ‑‑skip_reason. This option kann be set multiple times to specify more than one reason to skip the check. An excerpt from our help page to illustrate its usage: $ …
We are currently developing a check that detects the blocked but unused blocks of LUNs and that sends an alarm if a specified threshold has been reached. This check will most likely be used to notify admins that it is time to tell the VMWare ESX server via _unmap _to free unused blocks. Please find more information …
Our legacy check for Spapvaults on 7m filers (check_netapp7_snapvault) monitors lag time and other metrics, previously displayed in seconds:
$ ./check_netapp7_snapvault.pl -H sim ... ‑‑what=lag-time CRITICAL: Lag-time of SnapVault relation ... 12629906 seconds. Not that readable, is it? This is why the next release …
Not long ago we received an email from one of our very dedicated clients asking if it were possible to design a check that could verify if a server can be pinged from a vserver via jumbo frames. He was kind enough to attach a CLI command, which he used for testing purposes: network ping ‑vserver nfs ‑destination esx1 …