Skip to main content
NetApp Knowledge Base

Node out of quorum during cluster switch reboot due to improper cluster network cabling

  1. Last updated
  2. Save as PDF
Views:
922
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • Cluster Network Switches
  • Connectivity, Liveliness and Availability Monitor (CLAM)

Issue

  • During a cluster switch upgrade/reboot, the data traffic connectivity is lost briefly.
  • Node data LIFs failover to another node
  • Review of the EMS log file output shows the cluster is out of quorum:
[Node-02: kltp: clam.node.ooq:EMERGENCY]: Node (name=Node-01, ID=1000) is out of "CLAM quorum" (reason=node in minority).
[Node-02: kltp: clam.node.ooq:EMERGENCY]: Node (name=Node-03, ID=1002) is out of "CLAM quorum" (reason=node in minority).
 
  • Both cluster ports of the affected nodes go down at the same time:

[Node-01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-01, port e0a.
[Node-01: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0a on node Node-01 has gone down unexpectedly.
 

[Node-01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-01, port e0b.
[Node-01: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e0b on node Node-01 has gone down unexpectedly.

  • Nodes may encounter CLAM panic and reboot:

[Node-01: gop_eq_thread: sk.panic:alert]: Panic String: Received PANIC packet from partner, receiving message is (Coredump and takeover initiated because Connectivity, Liveliness and Availability Monitor (CLAM) has determined this node is out of quorum.) in SK process gop_eq_thread on release 9.10.1P6 (C)

  • The cluster applications of the affected nodes would go offline.

 

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.