Skip to main content
Install and maintain

Replace I/O module - AFF A70, AFF A90

Contributors dougthomp 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 controller

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.

About this task

  • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for the impaired controller SCSI blade. The cluster kernel-service show command (from priv advanced mode) displays the node name, quorum status of that node, availability status of that node, and operational status of that node.

    Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must be resolved before you proceed with the replacement.

  • 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: system node autosupport invoke -node * -type all -message MAINT=<# of hours>h

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

    Note When you see Do you want to disable auto-giveback?, enter y.

  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

    Take over or halt 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

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

    Take over or halt 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 controller module and follow the specific sequence of steps.

  1. On the front of the chassis, use your thumbs to firmly push each drive in until you feel a positive stop. This ensures that the drives are firmly seated against the chassis midplane.

    drw a800 drive seated IEOPS 960

  2. Go to the rear of the chassis. If you are not already grounded, properly ground yourself.

  3. Disconnect power by pulling the controller module out about three inches:

    Note If your storage system has DC power supplies units (PSUs), disconnect the power cable block from the PSUs.

    1. Press down on both of the locking latches, and then rotate both latches downward at the same time.

    2. Pull the controller module about 3 inches out of the chassis to disengage power.

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

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

  5. Rotate the cable management tray down by pulling the buttons on the inside of the cable management tray and rotating it down.

  6. Remove the I/O module from the controller module:

    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

    Cam locking button

    1. Depress the cam latch button.

      The cam latch moves away from the controller module.

    2. Rotate the cam latch down as far as it will go. For horizontal modules, rotate the cam away from the module as far as it will go.

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

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

  7. Set the I/O module aside.

  8. Install the replacement I/O module into the target slot:

    1. Align the I/O module with the edges of the slot.

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

  9. Cable the I/O module.

  10. Repeat the remove and install steps to replace additional modules for the controller.

  11. Reinstall the controller module into the chassis.

    Note If you have DC power supplies, reconnect the cable blocks to the PSUs.

  12. Rotate the cable management tray into the locked position.

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: set privilege advanced

    2. Reboot the BMC: sp reboot

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

    Note This reinitializes the I/O cards and other components and reboots the node.
    Note Be sure to exit Maintenance mode after completing the conversion.

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

  4. 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 & Replacements page for further information.