Remove the controller module, replace the boot media and transfer the boot image to the boot media - AFF A400

Contributors dougthomp netapp-martyh thrisun

To replace the boot media, you must remove the impaired controller module, install the replacement boot media, and transfer the boot image to a USB flash drive.

Step 1: Remove the controller module

To access components inside the controller module, you must remove the controller module from the chassis.

You can use the following animation, illustration, or the written steps to remove the controller module from the chassis.

Steps
  1. If you are not already grounded, properly ground yourself.

  2. Release the power cable retainers, and then unplug the cables from the power supplies.

  3. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFPs (if needed) from the controller module, keeping track of where the cables were connected.

    Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are organized.

  4. Remove the cable management device from the controller module and set it aside.

  5. Press down on both of the locking latches, and then rotate both latches downward at the same time.

    The controller module moves slightly out of the chassis.

    drw A400 Remove controller

    legend icon 01

    Locking latches

    legend icon 02

    Slide controller out of chassis

  6. Slide the controller module out of the chassis.

    Make sure that you support the bottom of the controller module as you slide it out of the chassis.

  7. Place the controller module on a stable, flat surface.

Step 2: Replace the boot media

You must locate the boot media in the controller module (see the FRU map on the controller module), and then follow the directions to replace it.

Before you begin

Although the contents of the boot media is encrypted, it is a best practice to erase the contents of the boot media before replacing it. For more information, see the Statement of Volatility for your system on the NetApp Support Site.

Note You must log into the NetApp Support Site to display the Statement of Volatility for your system.

You can use the following animation, illustration, or the written steps to replace the boot media.

Steps
  1. Open the air duct:

    drw A400 open air duct

    legend icon 01

    Locking tabs

    legend icon 02

    Slide air duct toward back of controller

    legend icon 03

    Rotate air duct up

    1. Press the locking tabs on the sides of the air duct in toward the middle of the controller module.

    2. Slide the air duct toward the back of the controller module, and then rotate it upward to its completely open position.

  2. Locate and remove the boot media from the controller module:

    drw A400 Replace boot media

    legend icon 01

    Press blue button

    legend icon 02

    Rotate boot media up and remove from socket

    1. Press the blue button at the end of the boot media until the lip on the boot media clears the blue button.

    2. Rotate the boot media up and gently pull the boot media out of the socket.

  3. Align the edges of the replacement boot media with the boot media socket, and then gently push it into the socket.

  4. Check the boot media to make sure that it is seated squarely and completely in the socket.

    If necessary, remove the boot media and reseat it into the socket.

  5. Lock the boot media in place:

    1. Rotate the boot media down toward the motherboard.

    2. Placing a finger at the end of the boot media by the blue button, push down on the boot media end to engage the blue locking button.

    3. While pushing down on the boot media, lift the blue locking button to lock the boot media in place.

  6. Close the air duct.

Step 3: Transfer 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.

Before you begin
  • You must have a USB flash drive, formatted to MBR/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. 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 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. 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:

      • 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. If the controller is in a stretch or fabric-attached MetroCluster, you must restore the FC adapter configuration:

    1. Boot to Maintenance mode: boot_ontap maint

    2. Set the MetroCluster ports as initiators: ucadmin modify -m fc -t initiator adapter_name

    3. Halt to return to Maintenance mode: halt

    The changes will be implemented when the system is booted.