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

You must have a USB flash drive, formatted to FAT32, with the following items:
  • 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.

Steps

  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. 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 systems using Storage Encryption (NSE), make sure that bootarg.storageencryption.support is set to true. If necessary, reset it by using the setenv command.

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

        ONTAP 9 Disks and Aggregates Power Guide

    2. If necessary, reset any environment variables: setenv environment_variable_name changed_value
    3. Save any changes you made: saveenv
  8. 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.
  9. Boot the recovery image: boot_recovery ontap_image_name.tgz
    Note: If the image.tgz file is named something other than image.tgz, such as boot_recovery 9_4.tgz, you need to include the different file name in the boot_recovery command.
    The system boots to the boot menu and prompts you for the boot image name.
  10. Enter the boot image name that is on the USB flash drive: image_name.tgz
    After image_name.tgz is installed, the system prompts you to restore the backup configuration (the var file system) from the healthy node.
  11. Restore the var file system:
    If your system has... Then...
    A network connection
    1. Press y when prompted to restore the backup configuration.
    2. Set the healthy node to advanced privilege level: set -privilege advanced
    3. Run the restore backup command: system node restore-backup -node local -target-address impaired_node_IP_address
    4. Return the node to admin level: set -privilege admin
    5. Press y when prompted to use the restored configuration.
    6. Press y when prompted to reboot the node.
    No network connection
    1. Press n when prompted to restore the backup configuration.
    2. Reboot the system when prompted by the system.
    3. Select the Update flash from backup config (sync flash) option from the displayed menu.

      If you are prompted to continue with the update, press y.

  12. Although ONTAP 9.4 retains the environment variable settings, it is a best practice to verify that they are set as expected.
    1. Take the node to the LOADER prompt.
    2. Check the environment variable settings with the printenv command.
    3. If an environment variable is not set as expected, modify it with the setenv environment_variable_name changed_value command.
    4. Save your changes using the saveenv command.
    5. Reboot the node.
  13. The next step depends on your system configuration:
    If your system is in... Then...
    A stand-alone configuration You can begin using your system after the node reboots.
    An HA pair After the impaired node is displaying the Waiting for Giveback... message, perform a giveback from the healthy node:
    1. Perform a giveback from the healthy node: storage failover giveback -ofnode partner_node_name

      This initiates the process of returning ownership of the impaired node's aggregates and volumes from the healthy node back to the impaired node.

      Note: If the giveback is vetoed, you can consider overriding the vetoes.

      ONTAP 9 High-Availability Configuration Guide

    2. Monitor the progress of the giveback operation by using the storage failover show-giveback command.
    3. After the giveback operation is complete, confirm that the HA pair is healthy and that takeover is possible by using the storage failover show command.
    4. Restore automatic giveback if you disabled it by using the storage failover modify command.