Skip to main content
NetApp Knowledge Base

MetroCluster dr config replication failed node hangs

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

Applies to

  • MetroCluster FC
  • ONTAP 9
  • DR Config Replication Failed error message
  • Cluster node not responsive

Issue

  • DR Config Replication Failed error messages are seen:

 

Issue #1: Failed SVM: c61a2744a3b8d89abc4c30b52c7242cc5ec3f0d992c1abbcabcb85bcb2e1b2d4 (syncing)

Secure ASUP checked against 2 signatures, no further analysis possible.

Cluster Name: NAFAS9000NBGSR1

Vserver: SVM01

Partner Vserver: SVM01-mc

Stream: 08ded1gz-9e46-11e9-8e9c-00a098abc550

Configuration State: healthy

Corrective Action: -

Creation Time on the source: 1/4/2023 07:51:49

Failed Row: -

Reason for Failure: -

Last Fail Time: -

Stream Status: idle

Is out of sync: false

Failed object: -

configuration Resume Time: -

Reason for Failure: -

  • One cluster node is unresponsive, data is not being served from the node.

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.