Skip to main content
NetApp Knowledge Base

InterclusterBrokenConnectionAlert is seen even though MetroCluster is healthy

Views:
125
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:
4/22/2024, 4:24:49 PM

Applies to

MetroCluster

Issue

  • The following error is seen:
::> system health alert show
Node: node01
Alert ID: InterclusterBrokenConnectionAlert
Resource: resource1
Severity: Major
Indication Time: Tue Apr 9 14:39:24 2024
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.
  • All other checks report that the MetroCluster is healthy:
::> cluster peer show
Peer Cluster Name         Cluster Serial Number Availability   Authentication
------------------------- --------------------- -------------- --------------
cluster-01                 1-80-000000           Available      ok
cluster-02                 1-80-000001           Available      ok
 
::> cluster peer health show
Node                      
             Ping-Status               RDB-Health Cluster-Health Availability
---------- --------------------------- --------- --------------- ------------
node-01      Data: interface_reachable
             ICMP: -                   true      true            true

::> metrocluster check show

Component           Result
------------------- ---------
nodes               ok
lifs                ok
config-replication  ok
aggregates          ok
clusters            ok
connections         not-applicable
volumes             ok

::> cluster peer ping
Destination Node IP Address       Count  TTL RTT(ms) Status
---------------- ---------------- ----- ---- ------- -------------------------
node-01           10.10.10.10        1   64   0.33    interface_reachable

 

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.