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 …
As of the next release, DiskPaths will skip unassigned disks (e.g. disks left over after an aggregate has been destroyed) since it is not its job to identify them. Skipped disks can be viewed with -verbose. From now on it is important to configure Disk Check with -what=unassigned. A best practice is not to leave any …
Our Disk check is going to have a new feature. Using the switch ‑‑what=non-zeroed-spare an alarm is sent as soon as non-zeroed spare disks have been found. Depending on wether the zeroing process is currently running or not, a WARNING (including progress) will be sent or else CRITICAL.
In order to facilitate the replacement of a broken hard disk, Disk Check will soon be able to display model, type, manufacturer and rpm using the switch --show_disk_inventory=always|non-ok|never Example of a simulator: $ ./check_netapp_pro.pl Disk -H sim821 --show_inventory_info=always NETAPP_PRO DISK OK - 14 disks …
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 …