Skip to main content
NetApp Knowledge Base

CMCCTB-87: Failed switchovers on disaster seen with no disaster or user input

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

Issue

  • Call home for switchover vetoed is seen but no switchover is attempted:

Call home for METROCLUSTER SWITCHOVER VETOED
  • Errors seen showing all nodes are online:

Node_1 (overridable veto): Both DR partner nodes are online. Either shut down the remote nodes manually, then try the command again, or use the "-override-vetoes" parameter to force the remote nodes to shut down.
  • Audit logs show no CLI commands were ran.
  • Tiebreaker logs show no switchover attempts.
  • MGWD logs show API calls for switchover on disaster:

ERR: metrocluster::PATCH: MCC patch: action 1 (switchover) specified 
NOTICE: metrocluster::PATCH: REST SO; forcedOnDisaster: yes, dryRun: no, controllerReplacement: no 
INFO: metrocluster::drc: Transition: normal>SO-in-progress ev so_start. 

 

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.