DR CONFIG REPLICATION FAILED Reason: Role already exists in legacy role table
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