Skip to main content
NetApp Knowledge Base

CONTAP-45188: Intermittent "InterclusterBrokenConnectionAlert" in four/eight-node Fabric-attached MetroCluster configuration

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

Issue

System health alert "InterclusterBrokenConnectionAlert" triggered intermittently in 4/8 -node Fabric-attached MetroCluster configuration.
Note: Alert is false and can be ignored when auto-cleared within 5 minutes
Example:
cluster_A::> system health alert show
Node: node_A1
Resource: node_A1
Severity: Major
Indication Time: Mon Dec 02 20:40:47 2019
Suppress: false
Acknowledge: false
Probable Cause: Connectivity to peer cluster is broken.
Possible Effect: Communication to the peer cluster is compromised and
the replication of configuration between the clusters
might stop.
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.

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.