Skip to main content
NetApp Knowledge Base

Cluster went out of CLAM quorum during cluster switch updates

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

Applies to

  • ONTAP 9
  • AutoSupport: NODE(S) OUT OF CLUSTER QUORUM
  • Cluster switch updates
  • Connectivity, Liveness, Availability Monitor (CLAM)

Issue

  • All the nodes in the cluster went out of quorum during the cluster switch updates, where one switch was updated at a time.
  • The following errors were observed in the EMS-LOG-FILE:

[node-06: kltp: callhome.clam.node.ooq:EMERGENCY]: Call home for NODE(S) OUT OF CLUSTER QUORUM.
[node-06: kltp: clam.node.ooq:EMERGENCY]: Node (name=node-01, ID=1000) is out of "CLAM quorum" (reason=node in minority).
[node-06: kltp: clam.node.ooq:EMERGENCY]: Node (name=node-02, ID=1001) is out of "CLAM quorum" (reason=node in minority).
[node-06: kltp: clam.node.ooq:EMERGENCY]: Node (name=node-03, ID=1002) is out of "CLAM quorum" (reason=node in minority).
[node-06: kltp: clam.node.ooq:EMERGENCY]: Node (name=node-04, ID=1003) is out of "CLAM quorum" (reason=node in minority).

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.