Skip to main content
Install and maintain

Replace an I/O module - AFF A900

Contributors dougthomp netapp-adityaw netapp-martyh
PDFs

To replace an I/O module, you must perform a specific sequence of tasks.

  • 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

Shut down or take over the impaired controller using one of the following options.

Option 1: Most systems

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

Before you begin

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 controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see Synchronize a node with the cluster.

Steps

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

    The following AutoSupport command 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 controller: storage failover modify –node local -auto-giveback false

  3. Take the impaired controller to the LOADER prompt:

    If the impaired controller 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)

    Halt or take over the impaired controller from the healthy controller: storage failover takeover -ofnode impaired_node_name

    When the impaired controller 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 controller, you must determine the status of the controller and, if necessary, take over the controller so that the healthy controller continues to serve data from the impaired controller 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 controller shows false for eligibility and health, you must correct the issue before shutting down the impaired controller; see Synchronize a node with the cluster.

  • 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 command: system node autosupport invoke -node * -type all -message MAINT=number_of_hours_downh

    The following AutoSupport command 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 controller: storage failover modify –node local -auto-giveback false

  3. Take the impaired controller to the LOADER prompt:

    If the impaired controller 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)

    Halt or take over the impaired controller from the healthy controller: storage failover takeover -ofnode impaired_node_name

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

Step 2: Replace I/O modules

To replace an I/O module, locate it within the chassis and follow the specific sequence of steps.

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

  2. Unplug any cabling associated with the target I/O module.

    Make sure that you label the cables so that you know where they came from.

  3. Remove the target I/O module from the chassis:

    1. Depress the lettered and numbered cam button.

      The cam button moves away from the chassis.

    2. Rotate the cam latch down until it is in a horizontal position.

      The I/O module disengages from the chassis and moves about 1/2 inch out of the I/O slot.

    3. Remove the I/O module from the chassis by pulling on the pull tabs on the sides of the module face.

      Make sure that you keep track of which slot the I/O module was in.

      Animation - Remove/install I/O module

      Removing a PCIe module

    Callout number 1

    Lettered and numbered I/O cam latch

    Callout number 2

    I/O cam latch completely unlocked

  4. Set the I/O module aside.

  5. Install the replacement I/O module into the chassis by gently sliding the I/O module into the slot until the lettered and numbered I/O cam latch begins to engage with the I/O cam pin, and then push the I/O cam latch all the way up to lock the module in place.

  6. Recable the I/O module, as needed.

Step 3: Reboot the controller

After you replace an I/O module, you must reboot the controller module.

Note If the new I/O module is not the same model as the failed module, you must first reboot the BMC.
Steps

  1. Reboot the BMC if the replacement module is not the same model as the old module:

    1. From the LOADER prompt, change to advanced privilege mode: priv set advanced

    2. Reboot the BMC: sp reboot

  2. From the LOADER prompt, reboot the node: bye

    Note This reinitializes the PCIe cards and other components and reboots the node.

  3. If your system is configured to support 10 GbE cluster interconnect and data connections on 40 GbE NICs, convert these ports to 10 GbE connections by using the nicadmin convert command from Maintenance mode. See Convert 40GbE NIC ports into multiple 10GbE ports for 10GbE connectivity for more information.

    Note Be sure to exit Maintenance mode after completing the conversion.

  4. Return the node to normal operation: storage failover giveback -ofnode impaired_node_name

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

Step 4: Return the failed part to NetApp

Return the failed part to NetApp, as described in the RMA instructions shipped with the kit. See the Part Return and Replacements page for further information.