• You must have a USB flash drive, formatted to FAT32, with at least 4GB capacity.
• A copy of the same image version of ONTAP as what the impaired controller was running. You can
download the appropriate image from the Downloads section on the NetApp Support Site
◦
If NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download
button.
◦
If NVE is not enabled, download the image without NetApp Volume Encryption, as indicated in the
download button.
• If your system is an HA pair, you must have a network connection.
• If your system is a stand-alone system you do not need a network connection, but you must perform an
additional reboot when restoring the var file system.
1. Align the end of the controller module with the opening in the chassis, and then gently push the
controller module halfway into the system.
2. Reinstall the cable management device and recable the system, as needed.
When recabling, remember to reinstall the media converters (SFPs) if they were removed.
3. Insert the USB flash drive into the USB slot on the controller module.
Make sure that you install the USB flash drive in the slot labeled for USB devices, and not in the USB
console port.
4. Push the controller module all the way into the system, making sure that the cam handle clears the
USB flash drive, firmly push the cam handle to finish seating the controller module, push the cam
handle to the closed position, and then tighten the thumbscrew.
The node begins to boot as soon as it is completely installed into the chassis.
5. Interrupt the boot process to stop at the LOADER prompt by pressing Ctrl-C when you see Starting
AUTOBOOT press Ctrl-C to abort….
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.
6. For systems with one controller in the chassis, reconnect the power and turn on the power supplies.
The system begins to boot and stops at the LOADER prompt.
7. 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.switchless_cluster.enable
b. If External Key Manager is enabled, check the bootarg values, listed in the
kenv
ASUP output:
▪
bootarg.storageencryption.support <value>
14