Skip to main content
Install and maintain

Remove the controller, replace the boot media, and transfer the boot image - AFF A900

Contributors dougthomp netapp-martyh netapp-adityaw
PDFs

You must unplug the controller module, remove and open the controller module, locate and replace the boot media in the controller, and then transfer the image to the replacement boot media.

Step 1: Remove the controller module

To access components inside the controller, 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 cables from the impaired controller module, and keep track of where the cables were connected.

  3. Slide the terra cotta button on the cam handle downward until it unlocks.

    Animation - Remove the controller
    Release the controller

    Callout number 1

    Cam handle release button

    Callout number 2

    Cam handle

  4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then 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.

  5. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module.

    Lift the cover off the controller module

    Callout number 1

    Controller module cover locking button

Step 2: Replace the boot media

You must locate the boot media in the controller and follow the directions to replace it.

Steps

  1. Lift the black air duct at the back of the controller module and then locate the boot media using the following illustration or the FRU map on the controller module:

    Animation - Replace boot media
    Remove boot media

    Callout number 1

    Press release tab

    Callout number 2

    Boot media

  2. Press the blue button on the boot media housing to release the boot media from its housing, and then gently pull it straight out of the boot media socket.

    Note Do not twist or pull the boot media straight up, because this could damage the socket or the boot media.

  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. Push the boot media down to engage the locking button on the boot media housing.

  6. Reinstall the controller module lid by aligning the pins on the lid with the slots on the motherboard carrier, and then slide the lid into place.

Step 3: Transfer the boot image to the boot media

You can install the system image to the replacement boot media using a USB flash drive with the image installed on it. However, you must restore the var file system during this procedure.

Before you begin

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

  • Download 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. Use the version -v command to display if your version of ONTAP supports NVE. If the command output displays <10no- DARE>, your version of ONTAP does not support NVE.

    • If NVE is supported by your version of ONTAP, download the image with NetApp Volume Encryption, as indicated in the download button.

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

  • 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 have not done so, download and copy the appropriate service image from the NetApp Support Site to the USB flash drive.

    1. Download the service image from the Downloads link on the page, 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.

      The USB flash drive should have the appropriate ONTAP image of what the impaired controller is running.

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

  3. Recable the controller module, as needed.

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

  5. Push the controller module all the way into the system, making sure that the cam handle clears the USB flash drive, firmly push the cam handle to finish seating the controller module, and then push the cam handle to the closed position.

    The controller begins to boot as soon as it is completely installed into the chassis.

  6. Interrupt the boot process to stop at the LOADER prompt by pressing Ctrl-C when you see Starting AUTOBOOT press Ctrl-C to abort…​.

    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.

  7. Set your network connection type at the LOADER prompt:

    • If you are configuring DHCP: ifconfig e0a -auto

      Note The target port you configure is the target port you use to communicate with the impaired controller from the healthy controller during var file system restore with a network connection. You can also use the e0M port in this command.

    • If you are configuring manual connections: ifconfig e0a -addr=filer_addr -mask=netmask -gw=gateway-dns=dns_addr-domain=dns_domain

      • filer_addr is the IP address of the storage system.

      • netmask is the network mask of the management network that is connected to the HA partner.

      • gateway is the gateway for the network.

      • dns_addr is the IP address of a name server on your network.

      • dns_domain is the Domain Name System (DNS) domain name.

        If you use this optional parameter, you do not need a fully qualified domain name in the netboot server URL. You need only the server's host name.

    Note Other parameters might be necessary for your interface. You can enter help ifconfig at the firmware prompt for details.

  8. 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 iniitator adapter_name

    3. Halt to return to Maintenance mode: halt

    The changes will be implemented when the system is booted.