Skip to main content
NetApp Knowledge Base

MetroCluster IP - Unable to switchback after motherboard replacement

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

Applies to

  • MetroCluster IP
  • ONTAP 9
  • Motherboard replacement

Issue

After motherboard replacement aggregate healing fails before switchback
 
Example:
 
ClusterA::> metrocluster operation show
       Operation: heal-aggregates
           State: failed
      Start Time: 3/30/2023 21:27:19
        End Time: 3/30/2023 21:30:36
          Errors: Failed to validate the node and cluster components before the heal-aggregates operation.
ClusterA::ClusterA-01 (non-overridable veto): Unable to issue the DR operation for partners (ClusterB-01). Make sure that the node is healthy before retrying the operation. If this condition persists, contact technical support for further assistance.
ClusterA::ClusterA-02 (non-overridable veto): Unable to process the DR operation for partners (ClusterB-02) due to an internal error (The local node is too busy processing other operations. Use the "system node run -node <node name> sysstat" command to check the status of the system, or wait a few minutes and then try the command again. If the problem persists, contact technical support for assistance.).

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.