Skip to main content
NetApp Knowledge Base

MetroCluster Configuration receiving InterclusterBrokenConnectionAlert

  1. Last updated
  2. Save as PDF
Views:
100
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • ONTAP

Issue

  • MetroCluster configuration receiving InterclusterBrokenConnectionAlert
  • Event logs: 24-01-10T20:43:19+01:00 172.XX.XX.XX [Node1-02: hm.alert.raised:ALERT]: Alert Id = InterclusterBrokenConnectionAlert , Alerting Resource = Node1-01 raised by monitor system-connect
  • Cluster Peer Ping Shows:

Node2::> cluster peer ping
Node: Node2-01 Destination Cluster: Node1
Destination Node IP Address Count TTL RTT(ms) Status
---------------- ---------------- ----- ---- ------- -------------------------
Node1-01     172.XX.XX.XX 1 64 0.838 interface_reachable
Node1-01     212.XX.XX.XX 1 - - unreachable
Node1-02     172.XX.XX.XX 1 64 0.835 interface_reachable
Node1-02     212.XX.XX.XX 1 - - unreachable

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.