Node is out of CLAM quorum: Cluster Network Disruption
Applies to
- Clustered Data ONTAP 8
- ONTAP 9
Issue
- A Node is out of 'CLAM quorum'.
Autosupport: NODE(S) OUT OF CLUSTER QUORUM - A node panics due to CLAM out of quorum:
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 mcc_ic_kill_pkt_handler on release 9.14.1P1 (C) - In some cases, the following EMS events are seen prior to the panic, when CSM is unable to create a session to the partner node:
kernel: csm.createSessionFailed:debug]: Cluster Session Manager (CSM) failed to create ....
CsmMpAgentThread: csm.createSessionFailed:debug]: Cluster Session Manager (CSM) failed to create session (req=pg1ntap1a:dblade, rsp=pg1ntap1b:dblade, uniquifier=0b064d5bdca6caaf) with transport type UNASSIGNED, session tag CTRAN, record state STARTING, CSM error CSM_CONNABORTED, low-level error UNKNOWN, socket error 0, and TLS error 0
