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

The replacement boot media that you installed does not have a boot image, so you need to transfer a boot image using a USB flash drive.

Before you begin


  1. Download and copy the appropriate service image from the NetApp Support Site to the USB flash drive.
    1. Download the service image to your work space on your laptop.
    2. Unzip the service image.
      Note: If you are extracting the contents using Windows, do not use winzip to extract the netboot image. Use another extraction tool, such as 7-Zip or WinRAR.
      There are two folders in the unzipped service image file:
      • boot
      • efi
    3. Copy the efi folder to the top directory on the USB flash drive.
      The USB flash drive should have the efi folder and the same Service Image (BIOS) version of what the impaired controller is running.
    4. Remove the USB flash drive from your laptop.
  2. If you have not already done so, close the air duct.
  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 or QSFPs) if they were removed.
  5. Plug the power cable into the power supply and reinstall the power cable retainer.
  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. Complete the reinstallation of the controller module:

    1. Make sure the latch arms are locked in the extended position.
    2. Using the latch arms, push the controller module into the chassis bay until it stops.
      Note: Do not push down on the latching mechanism at the top of the latch arms. Doing so with raise the locking mechanism and prohibit sliding the controller module into the chassis.
    3. Press down and hold the orange tabs on top of the latching mechanism.
    4. Gently push the controller module into the chassis bay until it is flush with the edges of the chassis.
      Note: The latching mechanism arms slide into the chassis.
      The controller module begins to boot as soon as it is fully seated in the chassis.
    5. Release the latches to lock the controller module into place.
    6. If you have not already done so, reinstall the cable management device.
  8. Interrupt the boot process by pressing Ctrl-C to stop at the LOADER prompt.
    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.
  9. 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.
  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 overwrite /etc/ssh/ssh_host_dsa_key.
  13. 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
  14. If the restore is successful, press y on the impaired node when prompted to use the restored copy?.
  15. Press y when you see confirm backup procedure was successful, and then press y when prompted to reboot the node.
  16. Verify that the environmental variables are set as expected.
    1. Take the node to the LOADER prompt.
      From the ONTAP prompt, you can issue the command system node halt -skip-lif-migration-before-shutdown true -ignore-quorum-warnings true -inhibit-takeover true.
    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.
  17. 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.
  18. Exit advanced privilege level on the healthy node.