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

Contributors netapp-martyh thrisun dougthomp

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 - AFF A250

To access components inside the controller module, you must first remove the controller module from the system, and then remove the cover on the controller module.

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

  2. Unplug the controller module power supplies from the source.

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

  4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever with your thumb, and gently pull the controller a few inches out of the chassis.

    Note If you have difficulty removing the controller module, place your index fingers through the finger holes from the inside (by crossing your arms)
    drw a250 pcm remove install

    legend icon 01

    Lever

    legend icon 02

    Latching mechanism

  5. Using both hands, grasp the controller module sides and gently pull it out of the chassis and set it on a flat, stable surface.

  6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover.

    drw a250 open controller module cover

    legend icon 01

    Thumbscrew

    legend icon 02

    Controller module cover.

  7. Lift out the air duct cover.

    drw a250 remove airduct cover

Step 2: Replace the boot media

You locate the failed boot media in the controller module by removing the air duct on the controller module before you can replace the boot media.

You need a #1 magnetic Phillips head screw driver to remove the screw that holds the boot media in-place. Due to the space constraints within the controller module, you should also have a magnet to transfer the screw on to so that you do not loose it.

You can use the following video or the tabulated steps to replace the boot media:

  1. Locate and replace the impaired boot media from the controller module.

    drw a250 replace boot media

    legend icon 01

    Remove the screw securing the boot media to the motherboard in the controller module.

    legend icon 02

    Lift the boot media out of the controller module.

    1. Using the #1 magnetic screw driver remove the screw from the impaired boot media, and set it aside safely on the magnet.

    2. Gently lift the impaired boot media directly out of the socket and set it aside.

    3. Remove the replacement boot media from the antistatic shipping bag and align it into place on the controller module.

    4. Using the #1 magnetic screw driver insert and tighten the screw on the boot media.

      Note Do not apply force when tightening the screw on the boot media; you might crack it.

Step 3: Transfer the boot image to the boot media

The replacement boot media that you installed is without a boot image so you need to transfer a boot image using a USB flash drive.

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

    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, install the air duct.

      drw a250 install airduct cover
    3. Close the controller module cover and tighten the thumbscrew.

      drw a250 close controller module cover

      legend icon 01

      Controller module cover

      legend icon 02

      Thumbscrew

    4. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.

    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. Push the controller module all the way into the chassis:

      1. Place your index fingers through the finger holes from the inside of the latching mechanism.

      2. Press your thumbs down on the orange tabs on top of the latching mechanism and gently push the controller module over the stop.

      3. Release your thumbs from the top of the latching mechanisms and continue pushing until the latching mechanisms snap into place.

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

    The controller module should be fully inserted and flush with the edges of the chassis.

    1. 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.san_optimized for 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.