When monitoring volumes with very different sizes using usage it might be desirable to have the option to configure different thresholds independently of the size of the volumes. The easiest way of doing this would be to set different percentages for small, medium and large volumes. Example Lets say… …
After having received feedback from a client saying the cluster mode collector get_netapp-cm.pl needs up to 45 seconds or more to collect 4500 snapshots, we looked into possibilities to accelerate the getter. In previous versions we relied on the default setting of the NetApp API which is set to 20 instances to be …
_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 …
With Usage it was always mandatory to set the ‑‑vserver|‑‑node|‑s argument. This means it necessary to specify for which node or vserver the volumes should be monitored. The argument expects either the node or vserver name, depending on the device being monitored. This has caused quite some confusion in the past. In …
DataONTAP 7.x will no longer be supported by check_netapp_pro. Nevertheless, some checks might still work relatively well. For example, the aggregate usage can be monitored with the check Usage, if the Server/Node name is set to the host name (--vserver|--node|-s). Here an example: $ ./get_netapp_7m.pl -H 10.25.0.22 -o …