Documentation
Disk-Check
Checks for failed or offline disks.
Usage
$ check_netapp_pro.pl Disk -H <host> [--what=failed | offline | unassigned | broken | non-zeroed-spare ] [--help] [...]
Description
This plugin checks for failed, offline, unassigned or broken disks. It is a replacement for the deprecated Check DiskFailed.
If checking for failed disks: Returns CRITICAL for each disk which has
attributes is-failed
is not false
or undefined
. For 7-mode filers the
broken-details
are evaluated. So broken disks on 7m filers are detected as
failed disks and --what=broken
is not suported for 7m filers.
The check for non-zeroed spare-disks (--what=non-zeroed-spare
) is
supported only for cluster-mode filers and alarms, if one or more non-zeroed
were found in the spare-container. This check exits with a WARNING if the
process of zeroing is going on but CRITCAL if not zeroed at all.
This check evaluates flags like 'is-failed'. These flags are set to true if a disk is failed and may disappear if the disk is ok. This design of the ZAPI is a bit risky in the sense that false negatives may occur. So we recommend to crosscheck also with the CLI or a native NetApp GUI.
Setting the thresholds (e.g. --warning=1 --critical=2
) sends a WARNING if one
disk is not ok but a CRITICAL alarm if 2 or more disks are non-ok.
Simple Examples
Checks all disks for their is-failed
attribute (cm) or broken-details (7m).
Same as above, but critical disks are at the top.
Checks all disks for their offline
attribute.
Checks for broken disks (disks whose container-type is broken). This is only supported on cm filers.
Checks for failed disks (broken disks are also failed).
Advanced Examples
Hint: The input for advanced examples is shortend. Replace the '...' below with ‑H <your filers ip or host-name>
Checks only the disks matching v5.32
.
Sends a WARNING for one failed disk but a CRITICAL alarm for 2 or more failed disks.