Skip to main content
NetApp Knowledge Base

CLAM panic due to wrong RCF when updating cluster switch

  1. Last updated
  2. Save as PDF
Views:
175
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
HW
Last Updated:

Applies to

  • ONTAP 9
  • Cluster network switch

Issue

  • Controller  panics during RCF update: 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.17.1P3 (C)
  •  Controller giveback fails: 
   Cluster::system node> storage failover show
   Takeoverby
   Node   Partner Possible State Description
  --------------------------------------------------------------------------
  Node01  Node02  true   Connected to utonetapp-clu-02, Partial giveback
  Node02  Node01   --    Waiting for cluster applications to come online on the local node
                         Offline applications: mgmt, vldb, vifmgr, bcomd, crs.

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.