Transferring the boot image to the boot media

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.

1. Download and copy the appropriate service image from the Lenovo Data Center 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 fully into the system. Complete the installation of the controller module:
   1. Rotate the locking latches upward, tilting them so that they clear the locking pins, and then lower them into the locked position.
   2. If you have not already done so, reinstall the cable management device.
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 cord into the power supply, reinstall the power cable locking collar, and then connect the power supply to the power source.
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. 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.
8. From the LOADER prompt, boot the recovery image from the USB flash drive: boot_recovery
   The image is downloaded from the USB flash drive.
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 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.
11. 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
12. If the restore is successful, press y on the impaired node when prompted to use the restored copy?.
13. Press y when you see confirm backup procedure was successful, and then press y when prompted to reboot the node.
14. 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.

       Note

       Please take special note the variable labeled

       bootarg.init.vendor_data1
       
       

       This is the system serial number and needs to match for both nodes

    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.
15. 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: 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. High-availability Configuration Guide Monitor the progress of the giveback operation by using the storage failover show-giveback command. 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. Restore automatic giveback if you disabled it using the storage failover modify command.

16. Exit advanced privilege level on the healthy node.