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.flash_optimized
â–ª
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.
8. Set your network connection type at the LOADER prompt:
â—¦
If you are configuring DHCP:
ifconfig e0a -auto
13