We are having a new check proposed by one of our customers who had an issue with a single process eating up all the CPU time on a filer. It’s easy to identify the culprit once you are on the command-line of the filer (priv-mode) by issuing the ps command. To automate that sort of monitoring and getting an alarm …
Mapped and online LUNs can remain unused in a filer because a connected initiator is missing. With the NetApp-CLI, such LUNS can be detected by following these steps: First, we look for initiator groups for which **all **initiators are not logged in. node01::> lun igroup show -igroup \*group06\* -instance Vserver …
One of the most innovative features of check_netapp_pro is probably the option -rm_ack, which solves the problem of errors not being alarmed for confirmed overall checks. These errors will not be alarmed actively and can therefore be easily overlooked. This switch might soon be replaced by another, more sophisticated …
Our new check PerfAggregate measures various performance counters per aggregate. Currently, the following counters can be monitored: aggr_throughput (B/s) latency (µs) read_data (B/s) total_transfers (/s) total_transfers_hdd (/s) total_transfers_ssd (/s) transmit_failure (-) user_read_blocks (/s) user_read_latency (us) …
The newly published check_netapp_takeover has been enhanced to check the metro-cluster configuration too. All of these checks are done in one service-check. Example:``` $ check_netapp_takeover.pl -H filer01f NETAPP_TAKEOVER OK node filer0101 connected (ha mode): The the storage failover facility is enabled. Takeover of …