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

Contributors netapp-martyh dougthomp 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, you must first remove the controller module from the system and then remove the cover on the controller module.

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

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

  3. Remove and set aside the cable management devices from the left and right sides of the controller module.

    drw 32xx cbl mgmt arm
  4. Loosen the thumbscrew on the cam handle on the controller module.

    drw 8020 cam handle thumbscrew

    legend icon 01

    Thumbscrew

    legend icon 02

    Cam handle

  5. Pull the cam handle downward and begin to 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.

Step 2: Replace the boot media - AFF A300

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

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

  2. Locate the boot media using the following illustration or the FRU map on the controller module:

    drw rxl boot media
  3. 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.
  4. Align the edges of the replacement boot media with the boot media socket, and then gently push it into the socket.

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

  6. Push the boot media down to engage the locking button on the boot media housing.

  7. Close the controller module cover.

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.

  • You must have a USB flash drive, formatted to 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. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.

    2. Reinstall the cable management device and recable the system, as needed.

      When recabling, remember to reinstall the media converters (SFPs) if they were removed.

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

    4. 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, push the cam handle to the closed position, and then tighten the thumbscrew.

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

    5. 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 node to boot to LOADER.

    6. For systems with one controller in the chassis, reconnect the power and turn on the power supplies.

      The system begins to boot and stops at the LOADER prompt.

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

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

    8. 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 node from the healthy node 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.
    9. 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.