Skip to main content

This Site will be down for up to 3 hours on December 2, 2023 from 8 PM - 11 PM PST, to deploy an infrastructure update.

NetApp Knowledge Base

Unable to reboot node in a MetroCluster IP (boot order)

Views:
335
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • MetroCluster IP
  • ONTAP 9.3 and later
  • Both clusters rebooted

Issue

During boot of both sites of a MetroCluster IP the following message is displayed:

Dec 06 03:52:47 [ClusterA:ha.partner.dbladeId:debug]: D-blade ID of the partner node is 707e7e25-bf8c-11e7-ae42-00a09897cb9f
MCC DR state check failed, retrying after 2 seconds...
MCC DR state check failed, retrying after 2 seconds...

Checking MCC DR state... [enter Ctrl-C(resume), S(status), L(link)]...........

The display of the "." behind the message is the indicator for this issue.

 

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.
Scan to view the article on your device