check_netapp_vserver (vserver's state)

Checks if a vserver is running or in another state.

Usage

$ check_netapp_vserver state -H <host> [...] [--help]
$ check_netapp_vserver state -H <host> --ok-state=[…] […] [--help]

Description

The vserver plugin retrieves the vserver state and compares ist with the value of --ok-state (string or regular expression) which defaults to running.

Important Parameters

--include / --exclude: Include or exclude volumes based on their name. The SVM-name is pre-fixed to the volume-name so that you can filter also based on the SVM-name.

For all other parameters consult --help on the commandline.

Example

Check all vservers for their state using the --ok-state default:

$ check_netapp_vserver state -H filer 
NETAPP VSERVER STATE OK - 5 vservers checked
na-01.vserv_b: running
na-01.vserv_a: running
na-02.vserv_a: running
na-02.vserv_b: running
na-00.vserv_a: running

Checking vServer on a Metrocluster

In a metrocluster, the vservers are arranged in pairs, with one of the two always down. To exclude these intentionally stopped vservers, simply set the --exclude=~-mc$ option on the dormant cluster node.

Example without --exclude=~-mc$:

$ check_netapp_vserver state 
NETAPP VSERVER CRITICAL - 8 vservers checked, 4 CRITICAL
NAS2_prbsvm1-mc: stopped (CRITICAL)
NAS2_svm1-mc: stopped (CRITICAL)
NAS2_daphne-mc: stopped (CRITICAL)
NAS2_svm2-mc: stopped (CRITICAL)
NAS1_svm3: running
NAS1_svm2: running
NAS1_svm1: running
NAS1_daphne: running

Example with --exclude=~-mc$:

$ check_netapp_vserver state --exclude=~-mc$
NETAPP VSERVER OK - 4 vservers checked
4 instances skipped because of --include/--exclude settings
NAS1_svm1: running
NAS1_daphne: running
NAS1_svm3: running
NAS1_svm2: running