Skip to main content
NetApp Knowledgebase

DR Config Replication AutoSupport messages triggered due to missing cluster peer on one cluster in a MetroCluster

Views:
107
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster
  • metrocluster vserver show displays error

Apply failed for Object: vserverPeer_permission_api_byuuid Method: baseline. Reason: A cluster that is peered with the MetroCluster partner cluster is not peered with the local cluster

 

Issue

DR Config Replication Failed Autosupport messages are sent due to the following error:

A cluster that is peered with the MetroCluster partner cluster is not peered with the local cluster

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support