Skip to main content
Install and maintain

Transfer the boot image to the boot media - AFF A700s

Contributors netapp-martyh
PDFs

You can install the system image to the replacement boot media using by using either the image on second boot media installed in the controller module, the primary method to restore the system image, or by transferring the boot image to the boot media using a USB flash drive when the secondary boot media restore failed or if the image.tgz file is not found on the secondary boot media.

Option 1: Transfer files to the boot media using backup recovery from the second boot media

You can install the system image to the replacement boot media using the image on second boot media installed in the controller module. This is the primary method for transferring the boot media files to the replacement boot media in systems with two boot media in the controller module.

The image on the secondary boot media must contain an image.tgz file and must not be reporting failures. If image.tgz file is missing or the boot media reports failures, you cannot use this procedure. You must transfer the boot image to the replacement boot media using the USB flash drive replacement procedure.

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.

      Closing the air duct

      Callout number 1

      Air duct

      Callout number 2

      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. 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 controller begins to boot as soon as it is completely installed into the chassis.

  7. 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 controller to boot to LOADER.

  8. From the LOADER prompt, boot the recovery image from the secondary boot media: boot_recovery

    The image is downloaded from the secondary boot media.

  9. When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.

  10. After the image is installed, start the restoration process:

    1. Record the IP address of the impaired controller 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.

  11. From the partner controller 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

  12. After the configuration synchronization is complete without errors, 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 controller.

  14. Exit advanced privilege level on the healthy controller.

Option 2: Transfer 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.

  • You must have a USB flash drive, formatted to FAT32, with at least 4GB capacity.

  • 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 NVE is enabled, download the image with NetApp Volume Encryption, as indicated in the download button.

    • If NVE is not enabled, download the image without NetApp Volume Encryption, as indicated in the download button.

  • 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. 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.

      Closing the air duct

      Callout number 1

      Air duct

      Callout number 2

      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 controller 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.

    If you miss this message, press Ctrl-C, select the option to boot to Maintenance mode, and then halt the controller 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-Flash SAN Array

      • bootarg.init.switchless_cluster.enable

    2. If External Key Manager is enabled, check the bootarg values, listed in the kenv ASUP output:

      • bootarg.storageencryption.support <value>

      • bootarg.keymanager.support <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:

      • bootarg.storageencryption.support <value>

      • bootarg.keymanager.support <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 controller 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 controller.

  14. From the partner controller 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 controller.

  17. Verify that the environmental variables are set as expected.

    1. Take the controller 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 savenv command.

    5. Reboot the controller.

  18. With the rebooted impaired controller displaying the Waiting for giveback…​ message, perform a giveback from the healthy controller:

    If your system is in…​ Then…​

    An HA pair

    After the impaired controller is displaying the Waiting for giveback…​ message, perform a giveback from the healthy controller:

    1. From the healthy controller: storage failover giveback -ofnode partner_node_name

      The impaired controller takes back its storage, finishes booting, and then reboots and is again taken over by the healthy controller.

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

      HA pair management

    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.

  19. Exit advanced privilege level on the healthy controller.