Documentation

MetroClusterVserver-Check

Checks the configuration state of MetroCluster-vservers.

Usage

$ check_netapp_pro.pl MetroClusterVserver -H <host> [-s <node>] [...] [--help]

Description

This check gets the configuration-state of metrocluster-vservers and returns OK if they equal 'healthy'. Otherwise it returns CRITICAL.

By evaluating also the reason for failure, specific reasons can be defined which will suppress an alarm.

Other switches allow to include or exclude a single vserver or groups of verserves matching a pattern.

Simple Examples

[S1] ./check_netapp_pro.pl MetroClusterVserver -H filer

Check all MetroCluster vservers for their configuration-state.

NETAPP_PRO VSERVER CRITICAL - 2 metrocluster-vservers checked, 1 critical and 0 warning
svm_vie-mc: unhealthy configuration-state, reason: hudriwudri found in configuration
svm_1_star: healthy configuration-state

[S2] ./check_netapp_pro.pl MetroClusterVserver -H filer --skip_reason='hudriwudri found in configuration'

Same as above, but stay cool in case of a hudriwudri-problem.

NETAPP_PRO VSERVER OK - 2 metrocluster-vservers checked
svm_vie-mc: unhealthy configuration-state, reason: hudriwudri found in configuration
svm_1_star: healthy configuration-state

Advanced Examples

Hint: The input for advanced examples is shortend. Replace the '...' below with ‑H <your filers ip or host-name>

[A1] ./check_netapp_pro.pl MetroClusterVserver ... -s xnode10

Check all vservers on the node 'xnode10'

[A2] ./check_netapp_pro.pl MetroClusterVserver ... -I ^svm_cifs

Check all vservers whose name starts with 'svm_cifs' on all nodes. E.g. svm_cifs10, svm_cifs20, ...