Skip to main content
Install and maintain

Replace I/O module - AFF C30 and AFF C60

Contributors netapp-jsnyder
PDFs

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

Before you begin

All other components in the storage system must be functioning properly; if not, you must contact NetApp Support before continuing with this procedure.

About this task

  • If needed, you can turn on the storage system location (blue) LEDs to aid in physically locating the affected storage system. Log into the BMC using SSH and enter the system location-led on command.

    A storage system has three location LEDs: one on the operator display panel and one on each controller. Location LEDs remain illuminated for 30 minutes.

    You can turn them off by entering the system location-led off command. If you are unsure if the LEDs are on or off, you can check their state by entering the system location-led show command.

Step 1: Shut down the impaired controller

Shut down or take over the impaired controller.

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.

Step 2: Replace a failed I/O module

To replace a failed I/O module, locate it in the controller and follow the specific sequence of steps.

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

  2. Unplug cabling from the failed I/O module.

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

  3. Remove the failed I/O module from the controller:

    Remove I/O module
    Callout number 1

    Turn the I/O module thumbscrew counterclockwise to loosen.
    Callout number 2

    Pull the I/O module out of the controller using the port label tab on the left and the thumbscrew.

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

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

    2. Gently push the I/O module all the way into the slot, making sure to properly seat the module into the connector.

      You can use the tab on the left and the thumbscrew to push in the I/O Module.

    3. Turn the thumbscrew clockwise to tighten.

  5. Cable the I/O module.

Step 3: Reboot the controller

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

Steps

  1. Reboot the controller from the LOADER prompt: bye

    Rebooting the impaired controller also reinitializes the I/O modules and other components.

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

  3. Restore automatic giveback from the console of the healthy controller: 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.