Skip to main content
NetApp Knowledge Base

Nodes stuck in boot after MetroCluster site relocating

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

Applies to

  • MetroCluster IP
  • AFF-A/C400
  • FAS 8300/8700
  • Site relocation

Issue

  • After moving one cluster of a MetroCluster to another location, both nodes are not booting up
  • ISCSI sessions to remote cluster timing out
    [node_A_1:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.2016-07.com.netapp:e7beb047-01b4-11eb-92bf-d039ea1ca5f6 (type: dr_partner, address: 192.168.10.5:65200). Reason: session login timed out.
  • Nodes stuck in boot
    MCC mode detected; checking DR state, flags: 0x1
    Local MCC state 32 (switchback_recovery_pending)
    Boot state: 0x4
    _MCC DR state check failed, retrying after 2 seconds...
    _MCC DR state check failed, retrying after 2 seconds...
    FWU 2nd trigger point
    FWU has no post firmware update action registered.
    _Checking MCC DR state... [enter Ctrl-C(resume), S(status), L(link)]

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.