c. Press down and hold the orange tabs on top of the latching mechanism.
d. Gently push the controller module into the chassis bay until it is flush with the edges of the chassis.
The latching mechanism arms slide into the chassis.
The controller module begins to boot as soon as it is fully seated in the chassis.
e. Release the latches to lock the controller module into place.
f. If you have not already done so, reinstall the cable management device.
8. Interrupt the boot process by pressing Ctrl-C to stop at the LOADER prompt.
If you miss this message, press Ctrl-C, select the option to boot to Maintenance mode, and then halt
the node to boot to LOADER.
9. Although the environment variables and bootargs are retained, you should check that all required boot
environment variables and bootargs are properly set for your system type and configuration using the
printenv bootarg name command and correct any errors using the setenv variable-name
<value>
command.
a. Check the boot environment variables:
â–ª
bootarg.init.boot_clustered
â–ª
partner-sysid
â–ª
bootarg.init.flash_optimized for AFF C190/AFF A220 (All Flash FAS)
â–ª
bootarg.init.san_optimized for AFF A220 and All SAN Array
â–ª
bootarg.init.switchless_cluster.enable
b.
If External Key Manager is enabled, check the bootarg values, listed in the
kenv ASUP output:
â–ª
bootarg.storageencryption.support <value>
â–ª
bootarg.keymanager.support <value>
â–ª
kmip.init.interface <value>
â–ª
kmip.init.ipaddr <value>
â–ª
kmip.init.netmask <value>
â–ª
kmip.init.gateway <value>
c.
If Onboard Key Manager is enabled, check the bootarg values, listed in the
kenv ASUP output:
â–ª
bootarg.storageencryption.support <value>
â–ª
bootarg.keymanager.support <value>
â–ª
bootarg.onboard_keymanager <value>
d.
Save the environment variables you changed with the
savenv command
e.
Confirm your changes using the
printenv variable-name command.
10.
From the LOADER prompt, boot the recovery image from the USB flash drive:
boot_recovery
The image is downloaded from the USB flash drive.
413