メインコンテンツまでスキップ

MetroCluster システムで誤った「InterclusterBrokenConnectionAlert」が報告されました

Views:
7
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
metrocluster<a>2009386191,</a>
Last Updated:

環境

  • ONTAP 9
  • ファブリック接続MetroCluster

問題

  • ONTAP のアップグレードまたはスイッチオーバー/スイッチバックの処理後、イベントログに「InterclusterBrokenConnectionAlert」イベントが報告されます。
[Node-1: schmd: hm.alert.raised:alert]: Alert Id = InterclusterBrokenConnectionAlert , Alerting Resource = Node-2 raised by monitor system-connect
[Node-1: mgwd: callhome.hm.alert.major:alert]: Call home for Health Monitor process schm: InterclusterBrokenConnectionAlert[Node-2].
  • システムヘルスアラートから報告される内容は次のとおりです。
Cluster1::*> system health alert show -instance
 
Node: Node-1
Monitor: system-connect
Alert ID: InterclusterBrokenConnectionAlert
Alerting Resource: Node-2
Subsystem: MetroCluster
Indication Time: Tue Nov 15 21:58:10 2022
Perceived Severity: Major
Probable Cause: Out_of_service
Description: Connectivity to peer cluster is broken.
Corrective Actions: 1) Ensure that the port is connected to the correct network/switch.
2) Ensure that the intercluster LIF is connected with the peered cluster.
3) Ensure that the peered cluster is up and running by using the command "cluster peer ping". Refer to the MetroCluster Disaster Recovery Guide if the peered cluster is down.
Possible Effect: Communication to the peer cluster is compromised and the replication of configuration between the clusters might stop.
  • このアラートが原因でMetroCluster がデグレード状態になっています:
Cluster1::> system health subsystem show
Subsystem     Health
----------------- ------------------
SAS-connect    ok
Environment    ok
Memory       ok
Service-Processor ok
Switch-Health   ok
CIFS-NDO      ok
Motherboard    ok
IO         ok
MetroCluster    degraded
MetroCluster_Node ok
FHM-Switch     ok
FHM-Bridge     ok
SAS-connect_Cluster ok
13 entries were displayedに関するネットアップのドキュメントを参照してください。

 

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.