Should I manually add missing mcc.'xxxx' bootargs to node configuration after boot device replacement?
Applies to
ONTAP 9
MetroCluster FC
MetroCluster IP
Answer
The following MetroCluster-only bootargs are cleared whenever the node recognizes that a boot device has been replaced, or whenever the current configuration is missing from the boot device and needs to be restored from backup.
bootarg.mcc.adp_enabled
bootarg.mcc.dr_aux_partner
bootarg.mcc.dr_aux_partner_uuid
bootarg.mcc.dr_partner
bootarg.mcc.dr_partner_uuid
bootarg.mcc.e0a.cfg
bootarg.mcc.e0b.cfg
bootarg.mcc.local_config_id
There is no need to manually add the bootargs at the LOADER prompt.
The bootargs are automatically restored to the boot device upon a successful copy of the varfs backup configuration back to the boot device from disk using option 6. This process involves issuing option '6' at the boot menu when prompted, and allowing the node to boot up until 'waiting for giveback'. After issuing a 'CFO-only' giveback to the node, only the root aggregate will migrate back to the affected node to allow the varfs configuration to be fully copied to the boot device.
The full process to follow can be accessed here: How to use boot menu option "(6) Update flash from backup config." within ONTAPAdditional Information