Skip to main content
NetApp Knowledge Base

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

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

Applies to

  • MetroCluster
  • ONTAP 9
  • DR CONFIG REPLICATION FAILED

Issue

  • An AutoSupport message is received: DR CONFIG REPLICATION FAILED
  • One or more Vservers are shown as "degraded" in the output of metrocluster vserver show:
ClusterB::*> metrocluster vserver show -vserver SVM_A

                              Cluster  : ClusterA
                              Vserver  : SVM_A
                      Partner Vserver  : SVM_A-mc
                  Configuration State  : degraded
                        Stream Status  : operation-failed
                    Corrective Action  : Resynchronize the configuration using "metrocluster vserver resync" command. Contact technical support for assistance if
configuration-state does not change to healthy.
                            Failed Row : Table Name: rest_roles_ui, Operation: get, Fields: SVM_A-mc a4_rest_role /api/svms readonly -
                         Failed Reason : Apply failed for Object: rest_roles_ui Method: baseline. Reason: Role already exists in legacy role table.
                 Last apply fail time  : 2/23/2023 08:37:06

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.