Transferring the boot image to the boot media using a USB flash drive

This procedure should only be used if the secondary boot media restore failed or if the image.tgz file is not found on the secondary boot media.

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.

Steps

  1. If you are not already grounded, properly ground yourself.
  2. If you have not already done so, close the air duct:
    1. Swing the air duct all the way down to the controller module.
    2. Slide the air duct toward the risers until the locking tabs click into place.
    3. Inspect the air duct to make sure that it is properly seated and locked into place.


      Air duct
      Risers
  3. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.
  4. Reinstall the cable management device and recable the system, as needed.
    When recabling, remember to reinstall the media converters (SFPs) if they were removed.
  5. Recable the power supply, and then connect it to the power source.
    Make sure that you reattach the power cable locking collar on the power cord.
  6. 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.
  7. Gently push the controller module all the way into the system until the controller module locking hooks begin to rise, firmly push on the locking hooks to finish seating the controller module, and then swing the locking hooks into the locked position over the pins on the controller module.
    The node begins to boot as soon as it is completely installed into the chassis.
  8. Interrupt the boot process by pressing Ctrl-C to stop at the LOADER prompt.
  9. 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 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

      • 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
  10. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery
    The image is downloaded from the USB flash drive.
  11. When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.
  12. After the image is installed, start the restoration process:
    1. Record the IP address of the impaired node that is displayed on the screen.
    2. Press y when prompted to restore the backup configuration.
    3. Press y when prompted to confirm that the backup procedure was successful.
  13. Press y when prompted whether to use the restored copy, and then press y when prompted to reboot the node.
  14. From the partner node in advanced privilege level, start the configuration synchronization using the IP address recorded in the previous step: system node restore-backup -node local -target-address impaired_node_IP_address
  15. After the configuration synchronization is complete without errors, press y when prompted to confirm that the backup procedure was successful.
  16. Press y when prompted whether to use the restored copy, and then press y when prompted to reboot the node.
  17. 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.
  18. With the rebooted impaired node displaying the Waiting for Giveback... message, perform a giveback from the healthy node:
    If your system is in... Then...
    An HA pair After the impaired node is displaying the Waiting for Giveback... message, perform a giveback from the healthy node:
    1. From the healthy node: storage failover giveback -ofnode partner_node_name

      The impaired node takes back its storage, finishes booting, and then reboots and is again taken over by the healthy 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 using the storage failover modify command.
    A two-node MetroCluster configuration Proceed to the next step.

    The MetroCluster healing and switchback procedures are done in the next task in the replacement process.

  19. Exit advanced privilege level on the healthy node.