Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 2 results
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_ports_e0a_and_e0b_go_down_causing_a_CLAM_panic
      This article describes the solution when both Cluster ports e0a and e0b go down causing a CLAM panic.
    • https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_ports_e0a_and_e0b_go_down_causing_a_CLAM_panic_power_cycle_does_not_resolve
      Cluster ports e0a and e0b go down causing a takeover of one of the nodes Tue Oct 03 11:08:31 CEST [node1: ixgbe/e0b: netif.linkDown:info]: Ethernet e0b: Link down, check cable. PANIC : Received PANIC ...Cluster ports e0a and e0b go down causing a takeover of one of the nodes Tue Oct 03 11:08:31 CEST [node1: ixgbe/e0b: netif.linkDown:info]: Ethernet e0b: Link down, check cable. 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. The steps in Cluster ports e0a and e0b go down causing a CLAM panic have been performed