Skip to main content
NetApp Stage KB

DR partner nodes unexpected reboot when MetroCluster IP NSO is performed

Applies to

MetroCluster IP

Issue

DR partner nodes unexpected reboot when MetroCluster IP NSO is performed, and the output of metrocluster operation show can be with errors or symptoms including:

(warning): Unable to validate SAN cache during Switchover. Reason: Failed to contact peer cluster "FASxxx" at addresses: 10.x.x.x, 10.x.x.x. RPC: Remote system error [from mgwd on node "FASxxx" (VSID: -3) to mgwd at 10.x.x.x, 10.x.x.x] in the remote cluster. Contact technical support for assistance in purging the SAN cache. FASxxx (warning): Unable to prepare the partner cluster for a pending switchback operation. Reason: Failed to contact peer cluster "FASxxx" at addresses: 10.x.x.x

Or

FASxxxx-2::*> metrocluster switchover

Warning: negotiated switchover is about to start. It will stop all the data Vservers on cluster "FASxxxx-1" and automatically restart them on cluster "FASxxxx-2". Do you want to continue? {y|n}: y

....

Verifying partner cluster connectivity.MetroCluster switchover completed with errors in auto heal. Reason: Exceeded the maximum number of retries for the command in phase Auto heal started: Failed to reach partner cluster "FASxxxx-1". Verify that the remote cluster nodes are up and healthy

 

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.
45b3b4f7-ecec-4061-972b-9ebb509a2462