Skip to main content
NetApp Stage KB

MetroCluster switchback fails vserver degraded configuration replication failed

Views:
1
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
MetroCluster
Last Updated:

 

Applies to

  • MetroCluster IP
  • ONTAP 9
  • MetroCluster in switchover

Issue

  • metrocluster switchback fails
  • metrocluster operation history shows:
Failed to validate the node and cluster components before the switchback operation.
CL02 (non-overridable veto): The Vserver configuration state was set to "degraded" because configuration replication failed. Reason: MetroCluster Vserver stream operation failed. Run the "metrocluster vserver show -configuration-state degraded -fields corrective-action" command to view detailed recovery information. The configuration replication operation will be retried and the Vserver configuration state might change.
  • metrocluster vserver show output shows reason for failure as:
Unrecoverable error during configuration replication, requires manual intervention. Error: Cannot find ports in IPspace "Default" on Node "CL01-N01" for placing LIF "CL01-N01_LIF01" in Vserver "SVM01_CL01".
  • network port show output shows that there are ports available in ipspace Default for the LIF

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.
cc0bd521-2a5a-4f4e-95bb-3e12f176c2c8