Checks the states (admin, oper, is-home) of the IP-interfaces (LIF, logical interface).
$ check_netapp_interface -H administrative-status <host> [--ok-state=<string or regex>] [...] [--help]
$ check_netapp_interface -H operational-status <host> [--ok-state=<string or regex>] [...] [--help]
$ check_netapp_interface -H is-home <host> [...] [--help]
This plugin checks each IP-interfaces (LIF) admin- or oper-status plus if it is-home. Alarms if the states do not match up, running (defaults) or true.
filer::> network interface show
Logical Status Network Current Current Is
Vserver Interface Admin/Oper Address/Mask Node Port Home
---------- ---------- ---------- ---------------- ------------ ------- ----
example
lif1 up/up 192.0.2.129/22 node-01
e0d false
node
cluster_mgmt up/up 192.0.2.3/20 node-02
e0c false
node-01
clus1 up/up 192.0.2.65/18 node-01
e0a true
clus2 up/up 192.0.2.66/18 node-01
e0b true
mgmt1 up/up 192.0.2.1/20 node-01
e0c true
node-02
clus1 up/up 192.0.2.67/18 node-02
e0a true
clus2 up/up 192.0.2.68/18 node-02
e0b true
mgmt2 up/up 192.0.2.2/20 node-02
e0d true
vs1
d1 up/up 192.0.2.130/21 node-01
e0d false
d2 up/up 192.0.2.131/21 node-01
e0d true
data3 up/up 192.0.2.132/20 node-02
e0c true
The operational status of data LIFs is determined by the status of the SVM with which the data LIFs are associated. When the SVM is stopped, the operational status of the LIF changes to down. When the SVM is started again, the operational status changes to up
Source: https://docs.netapp.com/us-en/ontap/networking/display_lif_information.html
Possible Status:
By default not_asscociated interfaces are alarmed as CRITICAL. This can be changed with --ok-status=~^(running|not_associated)$.
LIFs from SVMs are named with <svm-name>.<lif-id>. This allows to check LIFs of a specific SVM only with --include=~^<svm-name>\.
Example to check only LIFs on SVM with name svm_s3 : --include=~^svm_s3\.
This can be used also to exclude the interface of intentionally stopped vservers if you are monitoring a MetroCluster enviroment. (e.g. --exclude=~-mc\.)
./check_netapp_interface administrative-status -H filer
NETAPP_PRO INTERFACE OK - 27 ip interfaces checked
pro-nx-02_clus1: up
pro-nx-02_clus2: up
pro-nx-02_mgmt1: up
svm_s3.lif_svm_s3_408: up
svm_s3.lif_svm_s3_693: up
…
Checks all ip-interfaces (LIFs). Would return CRITICAL if the admin-state is not ‘up’
./check_netapp_interface administrative-status -H filer --include=~^svm_s3\.lif_svm
NETAPP_PRO INTERFACE OK - 2 ip interfaces checked
svm_s3.lif_svm_s3_408: up
svm_s3.lif_svm_s3_693: up
Checks only the ip-interfaces whose names begin with lif_svm.
./check_netapp_interface operational-status -H filer
NETAPP_PRO INTERFACE CRITICAL - 27 ip interfaces checked, 9 CRITICAL
cluster_mgmt: not_associated (CRITICAL)
pro-nx-02_clus2: not_associated (CRITICAL)
pro-nx-02_mgmt1: not_associated (CRITICAL)
pro-nx-02_nas_data: running
lif_acp_266: running
pro-nx-01_iscsi_datalif1: running
…
Checks all ip-interfaces (LIFs). Returns CRITICAL if the operational status is not ‘running’.
./check_netapp_interface -H filer operational-status --ok-status=~^(running|not_associated)$
NETAPP_PRO INTERFACE OK - 27 ip interfaces checked
cluster_mgmt: not_associated
lif_acp_266: running
pro-nx-01_iscsi_datalif1: running
pro-nx-02_clus2: not_associated
pro-nx-02_mgmt1: not_associated
pro-nx-02_nas_data: running
…
Checks all the ip-interfaces oper-status and accepts both running and not_associated as OK-status.