Transferring the boot image to the boot media

You can install the system image to the replacement boot media using a USB flash drive with the image installed on it. However, you must restore the var file system during this procedure.

Before you begin


  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. Recable the controller module, as needed.
  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, and then push the cam handle to the closed position.
    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. 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.
    1. 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
    2. If External Key Manager is enabled, check the bootarg values, listed in the kenv ASUP output:
      • <value>
      • <value>
      • kmip.init.interface <value>
      • kmip.init.ipaddr <value>
      • kmip.init.netmask <value>
      • kmip.init.gateway <value>
    3. If Onboard Key Manager is enabled, check the bootarg values, listed in the kenv ASUP output:
      • <value>
      • <value>
      • bootarg.onboard_keymanager <value>
    4. Save the environment variables you changed with the savenv command
    5. Confirm your changes using the printenv variable-name command.
  7. Set your network connection type at the LOADER prompt:
    • If you are configuring DHCP: ifconfig e0a -auto
      Note: The target port you configure is the target port you use to communicate with the impaired node from the healthy node during var file system restore with a network connection. You can also use the e0M port in this command.
    • If you are configuring manual connections: ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain
      • filer_addr is the IP address of the storage system.
      • netmask is the network mask of the management network that is connected to the HA partner.
      • gateway is the gateway for the network.
      • dns_addr is the IP address of a name server on your network.
      • dns_domain is the Domain Name System (DNS) domain name.

        If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL. You need only the server’s host name.

      Note: Other parameters might be necessary for your interface. You can enter help ifconfig at the firmware prompt for details.
  8. If the controller is in a stretch or fabric-attached MetroCluster, you must restore the FC adapter configuration:
    1. Boot to Maintenance mode: boot_ontap maint
    2. Set the MetroCluster ports as initiators: ucadmin modify -m fc -t iniitator adapter_name
    3. Halt to return to Maintenance mode: halt
    The changes will be implemented when the system is booted.