Skip to main content
NetApp Knowledge Base

CLAM panic during switch reboot activity

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

Applies to

  • ONTAP 9
  • FAS/AFF
  • Cluster Network Switch

Issue

  • During a cluster switch reboot activity, one of the two nodes in the cluster panics with the following panic string:

PANIC: 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.1P7 (C) on Tue Oct 22 23:42:14 CST 2024

  • Node 1 panicked when switch 2 was rebooted. Prior to that, switch 1 had already been rebooted.

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.