Skip to main content
Install and maintain

Replace I/O module - FAS70 and FAS90

Contributors netapp-jsnyder
PDFs

Use this procedure to replace a failed I/O module.

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

  • All other components in the storage 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 a failed I/O module

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

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

  2. Unplug any cabling on the target I/O module.

  3. Rotate the cable management tray down by pulling the buttons on both sides on the inside of the cable management tray and then rotate the tray down.

    Note This following illustration shows removing a horizontal and vertical I/O module. Typically, you will only remove one I/O module.

    Remove I/O module

    Callout number 1

    I/O cam latch

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

  4. Remove the target I/O module from the enclosure:

    1. Depress the cam button on the target module.

    2. Rotate the cam latch away from the module as far as it will go.

    3. Remove the module from the enclosure by hooking your finger into the cam lever opening and pulling the module out of the enclosure.

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

  5. Set the I/O module aside.

  6. Install the replacement I/O module into the enclosure:

    1. Align the module with the edges of the enclosure slot opening.

    2. Gently slide the module into the slot all the way into the enclosure, and then rotate the cam latch all the way up to lock the module in place.

  7. Cable the I/O module.

  8. Rotate the cable management tray up to the closed position.

Step 3: Reboot the controller

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

Steps

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

    This reinitializes the I/O cards and other components and reboots the node.

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

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