Transferring the boot image to the boot media in a two-node MetroCluster configuration

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

  • 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. 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 image version of ONTAP as what the impaired controller was 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 installation of the controller module:
    1. Plug the power cord into the power supply, reinstall the power cable locking collar, and then connect the power supply to the power source.
    2. Firmly push the controller module into the chassis until it meets the midplane and is fully seated.
      The locking latches rise when the controller module is fully seated.
      Note: Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.

      The controller module begins to boot as soon as it is fully seated in the chassis. Be prepared to interrupt the boot process.

    3. Rotate the locking latches upward, tilting them so that they clear the locking pins, and then lower them into the locked position.
    4. 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. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery
    The image is downloaded from the USB flash drive.
  10. When prompted, either enter the name of the image or accept the default image displayed inside the brackets on your screen.
  11. After the image is installed, start the restoration process:
    1. Press n when prompted to restore the backup configuration.
    2. Press y when prompted to reboot to start using the newly installed software.
      You should be prepared to interrupt the boot process when prompted.
  12. As the system boots, press Ctrl-C after you see the Press Ctrl-C for Boot Menu message., and when the Boot Menu is displayed select option 6.
  13. 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.