Skip to main content
NetApp Stage KB

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

  1. Last updated
  2. Save as PDF
Views:
2
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

 

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.