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

  • 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 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. 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. For systems running ONTAP 9.3 and earlier, verify that the environment variables are set as expected:
    Note: If you are running ONTAP 9.4 or later, the environment variables are persistent and should be set correctly. However, it is a best practice to verify the settings once your system has been restored.
    1. From the LOADER prompt, verify that the environment variables are set as expected: printenv
      • For AFF systems, make sure that bootarg.init.flash_optimized is set to true. If necessary, reset it by using the setenv command.
      • For systems using Storage Encryption (NSE), make sure that is set to true. If necessary, reset it by using the setenv command.

        If you are using KMIP servers, make sure that the* variables are properly set, usually during boot.

        ONTAP 9 Disks and Aggregates Power Guide

      • For systems using UTA2 adapters, make sure that the card settings by using the ucadmin command, and then make any necessary changes by using the ucadmin modify command.
    2. If necessary, reset any environment variables: setenv environment_variable_name changed_value
    3. Save any changes you made: saveenv
  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.