Skip to main content
NetApp Knowledge Base

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

Last Updated:

Applies to

  • ONTAP 9
  • CIFS


  • Event log shows:  hm.alert.raised


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.


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.