Skip to main content
Install and maintain

Replace a fan - AFF A800

Contributors dougthomp Copilot
PDFs

Replace a fan module in your AFF A800 system when a fan fails or is not operating efficiently, as this can affect system cooling and overall performance. The replacement process involves shutting down the impaired controller, removing it, replacing the fan module, reinstalling the controller, and then returning the failed part to NetApp.

Step 1: Shut down the impaired controller

Shut down 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:

    1. Enter the following command from the console of the healthy controller:

      storage failover modify -node impaired_node_name -auto-giveback false

    2. Enter y when you see the prompt Do you want to disable auto-giveback?

  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 -halt true

    The -halt true parameter brings you to the LOADER prompt.

Step 2: Remove the controller module

You must remove the controller module from the chassis when you replace the controller module or replace a component inside the controller module.

Steps

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

  2. Ensure that all drives in the chassis are firmly seated against the midplane by using your thumbs to push each drive until you feel a positive stop.

    Video - Confirm drive seating
    Seat the drives

  3. Check the controller drives based on the system status:

    1. On the healthy controller, check if any active RAID group is in a degraded state, failed state, or both:

      storage aggregate show -raidstatus !*normal*

      • If the command returns There are no entries matching your query. continue to go to the next sub-step to check for missing drives.

      • If the command returns any other results, collect the AutoSupport data from both controllers and contact NetApp Support for further assistance.

        system node autosupport invoke -node * -type all -message '<message_name>'

    2. Check for missing drive issues for both the file system or spare drives:

      event log show -severity * -node * -message-name *disk.missing*

      • If the command returns There are no entries matching your query. continue to go to the next step.

      • If the command returns any other results, collect the AutoSupport data from both controllers and contact NetApp Support for further assistance.

        system node autosupport invoke -node * -type all -message '<message_name>'

  4. Remove the power cable retainers, then unplug the cables from the power supplies.

  5. Loosen the hook and loop strap on the cable management device. Unplug the system cables and SFP/QSFP modules (if needed) from the controller module. Note each cable's location.

    Leave the cables in the cable management device so that when you reinstall the cable management device, the cables are organized.

  6. Remove the cable management device from the controller module and set it aside.

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

    The controller module moves slightly out of the chassis.

    Removing the controller module

    Callout number 1

    Locking latch

    Callout number 2

    Locking pin

  8. Slide the controller module out of the chassis and place it on a stable, flat surface.

    Support the bottom of the controller module while sliding it out of the chassis.

Step 3: Replace a fan

Locate the failed fan module and replace it with a new fan module.

Steps

  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 locking tabs on the side of the fan module, and then lifting the fan module straight out of the controller module.

    Removing the fan

    Callout number 1

    Fan locking tabs

    Callout number 2

    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 until the locking latches click into place.

Step 4: Reinstall the controller module

Reinstall the controller module and reboot it.

Steps

  1. Align the end of the controller module with the opening in the chassis, and then gently push the controller module halfway into the system.

    Note Do not completely insert the controller module in the chassis until instructed to do so.

  2. Recable the system, as needed.

    If you removed the media converters (QSFPs or SFPs), remember to reinstall them if you are using fiber optic cables.

  3. Complete the reinstallation of the controller module:

    1. Firmly push the controller module into the chassis until it meets the midplane and is fully seated.

      The locking latches rise when the controller module is fully seated.

      Note Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.

    2. Rotate the locking latches upward, tilting them so that they clear the locking pins, and then lower them into the locked position.

    3. Plug the power cords into the power supplies, reinstall the power cable locking collar, and then connect the power supplies to the power source.

      The controller module begins to boot as soon as power is restored. Be prepared to interrupt the boot process.

    4. If you have not already done so, reinstall the cable management device.

  4. Return the impaired controller 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.

  6. If AutoSupport is enabled, restore/unsuppress automatic case creation:

    system node autosupport invoke -node * -type all -message MAINT=END.

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