メインコンテンツへスキップ

クラスタポートがダウンし、CLAMパニックが発生する

Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

環境

  • ONTAP 9
  • 接続性、稼働性、および可用性モニター(CLAM)

問題

ごく短時間でノードの両方のクラスタポートがダウンしたことによるCLAMパニック
 

Sat Aug 10 22:02:37 -0400 [node2: kernel: netif.linkDown:info]: Ethernet e3a: Link down, check cable.

Sat Aug 10 22:02:55 -0400 [node2: kernel: netif.linkDown:info]: Ethernet e3b: Link down, check cable.

Sat Aug 10 22:03:54 -0400 [node1: kltp: clam.received.quorum:debug]: Local node received a quorum update from Cluster node (name=node3, ID=1002).
Sat Aug 10 22:03:54 -0400 [node1: kltp: callhome.clam.node.ooq:EMERGENCY]: Call home for NODE(S) OUT OF CLUSTER QUORUM.
Sat Aug 10 22:03:54 -0400 [node1: kltp: clam.node.ooq:EMERGENCY]: Node (name=node2, ID=1005) is out of "CLAM quorum" (reason=quorum update).
Sat Aug 10 22:03:54 -0400 [node1: kltp: clam.node.avail.change:debug]: The availability status of node (name=node2, ID=1005) changed from Available to Unavailable.
Sat Aug 10 22:03:54 -0400 [node1: ThreadHandlerun: clam.update.partner.state:info]: CLAM on node (ID=1004) updated failover state of partner (ID=1005) to nohb.
Sat Aug 10 22:03:54 -0400 [node1: clam_bg: clam.quorum.epoch:debug]: CLAM set the quorum epoch on local node to 223.
Sat Aug 10 22:03:54 -0400 [node1: ThreadHandlerun: clam.takeover:info]: Local node (name=node1, ID=1004) initiated takeover of partner node (name=node2, ID=1005, state=193) result=successful, type=panic.

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.