Skip to main content
NetApp Knowledge Base

DR CONFIG REPLICATION FAILED Reason: Role already exists in legacy role table

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

Applies to

  • MetroCluster
  • SVM Configuration Replication

Issue

After a rest role is created in the source vserver with a role name and API - /api/network/ip/interfaces a (DR CONFIG REPLICATION FAILED) ERROR AutoSupport was triggered and the SVM configuration state at the destination turns unhealthy:
 
ClusterB::> metrocluster vserver show  
                              Cluster  : ClusterA
                              Vserver  : SVM_A
                      Partner Vserver  : SVM_A-mc
                  Configuration State  : unhealthy

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.