Documentation

Checks if the disk paths follow a given pattern (A/B, B/A, AABB, ABAB, ...).

$ check_netapp_pro.pl DiskPaths2 -H <host> -w <n> -c <n> [...] [--help]

This plugin checks each disk for redundant paths. Alarms if a disk does not have a connection pattern as defined by --port_pattern_ok. Also checks if the primary and secondary host-adapters are different.

WARNING: This check is in ALPHA-state. Especially the config-sets have not been cross-checked and are likely to result in false-negatives! We are still in the process of developing reliable configurations. Any feedback is highly appreciated.

This check will replace DiskPaths in a future release.

CLI Equivalents

On the command-line you would type storage show disk -p and check, if column PRIMARY PORT and SECONDARY PORT both have a value of A or B.

7-Mode:

sim812> storage show disk -p
PRIMARY PORT SECONDARY PORT SHELF BAY
------- ---- --------- ---- ---------
v4.16 B v0.16 A ? ?
v4.17 B v0.17 A ? ?
v4.18 B v0.18 A ? ?
(...)
v5.27 B v1.27 A ? ?
v5.28 B v1.28 A ? ?
v5.29 B v1.29 A ? ?
v5.32 B v1.32 A ? ?

Cluster-Mode:

cluster1::> storage disk show -port
Primary Port Secondary Port Type Shelf Bay
--------------- ---- --------------- ---- ------ ----- ---
cluster1-01:v4.16
B cluster1-01:v0.16
A FCAL - -
cluster1-01:v4.17
B cluster1-01:v0.17
A FCAL - -
cluster1-01:v4.18
B cluster1-01:v0.18
A FCAL - -
(...)
cluster1-02:v5.32
B cluster1-02:v1.32
A FCAL - -
56 entries were displayed.

Consider using -v for inspection, if you are not satisfied with the result.

Handling of Unassigned Disks

If disks are unassigned (e.g. if they are not assigned to an owner after having destroyed an aggregate) they are silently skipped. You can use the verbose mode (--verbose|-v) to list these disks.

Please keep in mind that it is a best practice to not leave disks unassigned. So we highy recommend to have a check based on the Disk-check (--what=unassigend) configured too.

Configuration Sets

The check can either be configured on the commandline or by pointing --config to a file with a predefined set of commandline arguments (e.g. --config=JobSnapMirror.set).

We deliver several of such sets for different purposes like the monitoring of SnapMirror Jobs. These files can be used as they are but also as template for your own predefined sets.

Where to store set-files

Set-files with no leading slash are expected to be in ./config wheras a file-name prefixed with a slash is considered to be an absolut path (e.g. /usr/local/nagios/config/my.set).

We recommend to save your own set-files outside of the check_netapp_pro/scripts directory, so that your set-files survive the next update.

Mixing the config-set and commandline-arguments

Commandline arguments can be used together with a config-set file and will in case of a conflict overrule the arguments in the set-file. Keep in mind, that command-line arguments which can be repeated won't conflict with a second argument of the same name and therefore will be ammended and not overruled.

Possible Enhancements

The following metrics may be of interest for future enhancements of the cluster-mode check:

• path-quality: The percentage of the error threshold. 0% NO ERROR 1-20% LOW ERROR, available to load balancing and error retry code. 21-99% MEDIUM ERROR, load balancing and error retry code will not switch to this path. 100-? HIGH_ERROR, Excessive errors EMS event will be logged.

• path-io-kbps: Rolling average of kilobytes per second read and written to this path.

• path-link-errors: Number of link errors reported on the path.

Please contact NAPRO-EMAIL-DEVELOPER to request these enhancements.