Skip to main content
Effective December 3 - NetApp adopts Microsoft’s Business-to-Customer (B2C) identity management to simplify and provide secure access to NetApp resources. For accounts that did not pre-register (prior to Dec 3) access to your NetApp data may take up to 1 hour as your legacy NSS ID is synchronized to the new B2C identity. To learn more, Read the FAQ and Watch the video.
NetApp Knowledge Base

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

Views:
164
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 the 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.

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support