Health monitor raises "hm.alert.raised" due to NoStandbyLifCifsNdo_Alert

• Event log shows:  hm.alert.raised

Example:

Tue May 29 08:09:21 2018 [node-name: nchmd: hm.alert.raised:critical]: params: {'alert_id': 'NoStandbyLifCifsNdo_Alert', 'alerting_resource': 'svm-name', 'detailed_info': 'Alert Id = NoStandbyLifCifsNdo_Alert , Alerting Resource = svm-name', 'monitor': 'node-connect'}

• System health alert shows:

::> system health alert show
Node: node-name
Resource: svm-name
Severity: Minor
Indication Time: Tue May 29 08:09:21 2018
Suppress: false
Acknowledge: false
Probable Cause: Vserver "svm-name" is actively serving data
over CIFS through node "node-mame", and there are
CIFS files opened persistently over continuously
available shares. However, its partner node
"other node-name" is not exposing any active data LIFs
for the Vserver.
Possible Effect: In the event that node "node-name" fails, node
"other node-mame" will witness the condition very
quickly. If a data LIF for Vserver
"svm-name" existed on node "node-name",
that node would have the capability to bring active
connections away from node "other-node-name"
non-disruptively and faster than waiting for the data
LIF to fail over and the client to recover on its own.
Corrective Actions: Create a data LIF on node "node-name" for Vserver
"svm-name", or move an existing one to that node.