Skip to main content
NetApp Stage KB

Option 6 resets ha-config from mcc or mccip to ha during boot_recovery process in 4-node MetroCluster

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

 

 

Applies to

  • ONTAP 9
  • AFF A400
  • FAS8300
  • AFF A800
  • 4-Node Metrocluster FC
  • 4-Node Metrocluster IP

Issue

  • During a maintenance that requires the boot_recovery procedure to be performed (ARL headswap, boot device replacement) on an AFF A400 or FAS8300 running 9.7.X in a 4-node Metrocluster configuration, the backup configuration file must be restored onto the new boot media prior to booting back into ONTAP on the affected node.
  • It is noted that attempts to restore the VARFS backup configuration file using option 6 at the special boot menu fails.
  • You may see similar console messages appear as below in a 4-node Metrocluster FC configuation.
Jun 13 08:09:04 [Node1:fci.adapter.error:notice]: Fibre Channel adapter driver encountered error "Either the platform does not support this type of FC/FCVI adapter, or the platform supports the adapter but the chassis and controller variables are not set correctly." on adapter 2a.
Jun 13 08:09:04 [Node1:fci.adapter.error:notice]: Fibre Channel adapter driver encountered error "Either the platform does not support this type of FC/FCVI adapter, or the platform supports the adapter but the chassis and controller variables are not set correctly." on adapter 2b.
Jun 13 08:09:29 [Node1:scsitarget.slifct.fwAutoBoot:notice]: FC target HBA 1c firmware version updated from 11.4.277.0 to 12.2.390.0. The controller will be rebooted automatically to enable the new HBA firmware.
Rebooting after updating Emulex FC firmware.

 

 

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.