Skip to main content
NetApp Knowledge Base

METROCLUSTER SWITCHOVER FAILED during ONTAP upgrade

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

Applies to

  • 2 node MetroCluster with SnapMirror cluster peers
  • Switchover / Switchback
  • Peer cluster
  • Automated NDU

Issue

  • Autosupports triggered titled "METROCLUSTER SWITCHOVER FAILED" after switchover is initiated.

metrocluster operation show displays the following:

Operation: switchover
State: completed-with-manual-recovery-needed
Errors: <switchover_target_cluster> (manual recovery required): Internal error. Unable to migrate Vserver peer relationships. Reason: (Failed to communicate with peer cluster "<external_cluster>".). Contact technical support for assistance

  • Event log shows:

[<node>: mgwd: cpeer.addr.stable.down:error]: Stable address <IP> of cluster <source/destination_cluster>, in IPspace <IPspace_name>, cannot be contacted.

  • This issue only affects SnapMirror/SnapVault following the otherwise successful switchover.
  • SnapMirror peer does Not exist

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.