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. 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. 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. 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.
  8. 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.
  9. 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.

  10. 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.
  11. 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.