Replace a fan — FAS500f

Contributors dougthomp netapp-martyh thrisun

You replace a fan with a new fan module when it fails.

Step 1: Shut down the impaired controller

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

You must remove the controller module from the chassis when you replace a fan module.

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

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

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

  3. Release the power cable retainers, and then unplug the cables from the power supplies.

  4. Insert your forefinger into the latching mechanism on either side of the controller module, press the lever with your thumb, and gently pull the controller a few inches out of the chassis.

    Note If you have difficulty removing the controller module, place your index fingers through the finger holes from the inside (by crossing your arms)
    drw a250 pcm remove install

    legend icon 01

    Lever

    legend icon 02

    Latching mechanism

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

  6. Turn the thumbscrew on the front of the controller module anti-clockwise and open the controller module cover.

    drw a250 open controller module cover

    legend icon 01

    Thumbscrew

    legend icon 02

    Controller module cover.

Step 3: Replace a fan

To replace a fan, remove the failed fan module and replace it with a new fan module.

You can use the following video or the tabulated steps to replace a fan:

  1. Identify the fan module that you must replace by checking the console error messages or by locating the lit LED for the fan module on the motherboard.

  2. Remove the fan module by pinching the side of the fan module, and then lifting the fan module straight out of the controller module.

    drw a250 replace fan

    legend icon 01

    Fan module

  3. Align the edges of the replacement fan module with the opening in the controller module, and then slide the replacement fan module into the controller module.

Step 4: Reinstall the controller module

After you replace a component within the controller module, you must reinstall the controller module in the system chassis and boot it.

  1. Close the controller module cover and tighten the thumbscrew.

    drw a250 close controller module cover

    legend icon 01

    Controller module cover

    legend icon 02

    Thumbscrew

  2. Insert the controller module into the chassis:

    1. Ensure the latching mechanism arms are locked in the fully extended position.

    2. Using both hands, align and gently slide the controller module into the latching mechanism arms until it stops.

    3. Place your index fingers through the finger holes from the inside of the latching mechanism.

    4. Press your thumbs down on the orange tabs on top of the latching mechanism and gently push the controller module over the stop.

    5. Release your thumbs from the top of the latching mechanisms and continue pushing until the latching mechanisms snap into place.

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

    The controller module should be fully inserted and flush with the edges of the chassis.

  3. Recable the system, as needed.

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

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

Step 5: 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.