Skip to main content
NetApp Knowledge Base

Missing MCC Bootargs After Option 6 Prevent DR Partner Connectivity

Views:
4
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
CORE
Last Updated:

Applies to

  • ONTAP MetroCluster IP configurations
  • Headswap/Upgrade scenarios

Issue

  • After performing a headswap and executing boot menu Option 6 (Update flash from backup config), MetroCluster nodes are unable to detect or reconnect to the DR partner. The following message is observed during boot:
  • Jun 01 12:16:27 [node:iscsi.session.stateChanged:notice]: iSCSI session state is changed to Reconnecting for the target iqn.xxx (type: dr_partner, address: 172.1.1.4:65200). Reason: session login timed out.
  • When booting to Maintenance Mode, the required MetroCluster (MCC) boot arguments are found to be missing:
    • Bootarg Example Value
      bootarg.mcc.port_a_ip_config 192.168.10.2/24,0,0,192.168.10.4,192.168.10.3
      bootarg.mcc.port_b_ip_config 192.168.20.2/24,0,0,192.168.20.4,192.168.20.3
      bootarg.mgwd.cluster_uuid 11111111-2222-3333-4444-555555555555
      bootarg.mgwd.partner_cluster_uuid aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee
      bootarg.mcc.pri_partner_uuid 12345678-1234-1234-1234-123456789abc
      bootarg.mcc.aux_partner_uuid abcdef12-3456-7890-abcd-ef1234567890
      bootarg.mcc_iscsi.node_uuid fedcba98-7654-3210-fedc-ba9876543210
      bootarg.mcc.adp_enabled true
      bootarg.mcc.local_config_id <local_config_id>
      bootarg.mcc.dr_partner <dr_partner_id>

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.