Replace a PCIe card - AFF A320

Contributors dougthomp netapp-martyh thrisun

To replace a PCIe card, you must disconnect the cables from the cards, remove the SFP and QSFP modules from the cards before removing the riser, reinstall the riser, and then reinstall the SFP and QSFP modules before cabling the cards.

  • You can use this procedure with all versions of ONTAP supported by your system

  • All other components in the system must be functioning properly; if not, you must contact technical support.

Step 1: Shut down the impaired node

You can shut down or take over the impaired controller using different procedures, depending on the storage system hardware configuration.

Option 1: Most configurations

To shut down the impaired node, you must determine the status of the node and, if necessary, take over the node so that the healthy node continues to serve data from the impaired node storage.

About this task

If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy node shows false for eligibility and health, you must correct the issue before shutting down the impaired node; see the Administration overview with the CLI.

Steps
  1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh

    The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h

  2. Disable automatic giveback from the console of the healthy node: storage failover modify –node local -auto-giveback false

  3. Take the impaired node to the LOADER prompt:

    If the impaired node is displaying…​ Then…​

    The LOADER prompt

    Go to the next step.

    Waiting for giveback…​

    Press Ctrl-C, and then respond y when prompted.

    System prompt or password prompt (enter system password)

    Take over or halt the impaired node:

    • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode impaired_node_name

      When the impaired node shows Waiting for giveback…​, press Ctrl-C, and then respond y.

Option 2: Controller is in a MetroCluster

Note Do not use this procedure if your system is in a two-node MetroCluster configuration.

To shut down the impaired node, you must determine the status of the node and, if necessary, take over the node so that the healthy node continues to serve data from the impaired node storage.

  • If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or a healthy node shows false for eligibility and health, you must correct the issue before shutting down the impaired node; see the Administration overview with the CLI.

  • If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration State is configured and that the nodes are in an enabled and normal state (metrocluster node show).

Steps
  1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh

    The following AutoSupport message suppresses automatic case creation for two hours: cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h

  2. Disable automatic giveback from the console of the healthy node: storage failover modify –node local -auto-giveback false

  3. Take the impaired node to the LOADER prompt:

    If the impaired node is displaying…​ Then…​

    The LOADER prompt

    Go to the next step.

    Waiting for giveback…​

    Press Ctrl-C, and then respond y when prompted.

    System prompt or password prompt (enter system password)

    Take over or halt the impaired node:

    • For an HA pair, take over the impaired node from the healthy node: storage failover takeover -ofnode impaired_node_name

      When the impaired node shows Waiting for giveback…​, press Ctrl-C, and then respond y.

Step 2: Remove the controller module

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

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

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

  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.

    drw a320 controller cable unplug animated gif

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

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

  5. Remove the controller module from the chassis:

    drw a320 controller remove animated gif
    1. Insert your forefinger into the latching mechanism on either side of the controller module.

    2. Press down on the orange tab on top of the latching mechanism until it clears the latching pin on the chassis.

    The latching mechanism hook should be nearly vertical and should be clear of the chassis pin.

    1. Gently pull the controller module a few inches toward you so that you can grasp the controller module sides.

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

Step 3: Replace a PCIe card

You must remove the PCIe riser containing the failed PCIe card from the controller module, remove the failed PCIe card from the riser, install the replacement PCIe card in the riser, and then reinstall the riser into the controller module.

drw a320 pci card replace animated gif
  1. Remove the cover over the PCIe risers by unscrewing the blue thumbscrew on the cover, slide the cover toward you, rotate the cover upward, lift it off the controller module, and then set it aside.

  2. Remove the riser with the failed PCIe card:

    1. Remove any SFP or QSFP modules that might be in the PCIe cards.

    2. Place your forefinger into the hole on the left side of the riser module and grasp the riser with your thumb.

    3. Lift the riser straight out of the socket and set it aside.

  3. Replace the card in the riser:

    1. Place the riser on a stable surface, and then turn the riser so that you can access the PCIe card.

    2. Place your thumbs just below the bottom edge of the PCIe card on either side of the socket, and then gently push up to release the card from the socket.

    3. Slide the card out of the riser and set it aside.

    4. Align the replacement card bezel with the edge of the riser and the outside edge of the card with the alignment guide on the left side of the riser.

    5. Gently slide the card until the card connector aligns with the riser socket, and then gently push the card down into the socket.

  4. Reinstall the riser in the controller module:

    1. Align the riser over the opening so that the front edges of the riser are directly over the openings on the riser bay.

    2. Aligning the back edge of the riser so that the pins on the underside of the riser are over the holes in the sheet metal at the back riser bay.

    3. Apply even downward pressure to seat the riser straight down into the socket on the controller module.

    4. Reinstall the PCIe riser cover on the controller module.

Sep 4: Install the controller module

After you have replaced the component in the controller module, you must re-install the controller module into the chassis, and then boot it to Maintenance mode.

  1. If you have not already done so, close the air duct at the rear of the controller module and reinstall the cover over the PCIe cards.

  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.

    drw a320 controller install animated gif
    Note Do not completely insert the controller module in the chassis until instructed to do so.
  3. Cable the management and console ports only, so that you can access the system to perform the tasks in the following sections.

    Note You will connect the rest of the cables to the controller module later in this procedure.
  4. Complete the reinstallation of the controller module:

    1. Make sure the latch arms are locked in the extended position.

    2. Using the latch arms, push the controller module into the chassis bay until it stops.

    3. Press down and hold the orange tabs on top of the latching mechanism.

    4. Gently push the controller module into the chassis bay until it is flush with the edges of the chassis.

      Note The latching mechanism arms slide into the chassis.

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

    5. Release the latches to lock the controller module into place.

    6. Recable the power supply.

    7. If you have not already done so, reinstall the cable management device.

    8. Interrupt the normal boot process by pressing Ctrl-C.

Step 5: Restore the controller module to operation

After completing diagnostics, you must recable the system, give back the controller module, and then reenable automatic giveback.

  1. Recable the system, as needed.

    If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables.

  2. Return the node to normal operation by giving back its storage: storage failover giveback -ofnode impaired_node_name

  3. If automatic giveback was disabled, reenable it: storage failover modify -node local -auto-giveback true

Step 6: Return the failed part to NetApp

After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions shipped with the kit. Contact technical support at NetApp Support, 888-463-8277 (North America), 00-800-44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help with the replacement procedure.