Replace a DIMM - AFF A200

Contributors netapp-martyh dougthomp netapp-jsnyder thrisun

You must replace a DIMM in the controller module when your system registers an increasing number of correctable error correction codes (ECC); failure to do so causes a system panic.

About this task
  • All other components in the system must be functioning properly; if not, you must contact technical support.

  • You must replace the failed component with a replacement FRU component you received from your provider.

Step 1: Shut down the impaired controller

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.

  4. If the system has only one controller module in the chassis, turn off the power supplies, and then unplug the impaired node’s power cords from the power source.

Step 2: Open the system

To access components inside the controller, you must first remove the controller module from the system and then remove the cover on the controller module.

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

  2. Loosen the hook and loop strap binding the cables to the cable management device, and then unplug the system cables and SFPs (if needed) from the controller module, keeping track of where the cables were connected.

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

  3. Remove and set aside the cable management devices from the left and right sides of the controller module.

    drw 25xx cable management arm
  4. Squeeze the latch on the cam handle until it releases, open the cam handle fully to release the controller module from the midplane, and then, using two hands, pull the controller module out of the chassis.

    drw 2240 x opening cam latch
  5. Turn the controller module over and place it on a flat, stable surface.

  6. Open the cover by sliding in the blue tabs to release the cover, and then swing the cover up and open.

    drw 2600 opening pcm cover

Step 3: Replace the DIMMs

To replace the DIMMs, locate them inside the controller and follow the specific sequence of steps.

About this task

If you are replacing a DIMM, you need to remove it after you have unplugged the NVMEM battery from the controller module.

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

  2. Check the NVMEM LED on the controller module.

    You must perform a clean system shutdown before replacing system components to avoid losing unwritten data in the nonvolatile memory (NVMEM). The LED is located on the back of the controller module. Look for the following icon:

    drw hw nvram icon
  3. If the NVMEM LED is not flashing, there is no content in the NVMEM; you can skip the following steps and proceed to the next task in this procedure.

  4. If the NVMEM LED is flashing, there is data in the NVMEM and you must disconnect the battery to clear the memory:

    1. Locate the battery, press the clip on the face of the battery plug to release the lock clip from the plug socket, and then unplug the battery cable from the socket.

      drw 2600 nvmem battery unplug
    2. Confirm that the NVMEM LED is no longer lit.

    3. Reconnect the battery connector.

  5. Return to step 2 of this procedure to recheck the NVMEM LED.

  6. Locate the DIMMs on your controller module.

    Note Each system memory DIMM has an LED located on the board next to each DIMM slot. The LED for the faulty blinks every two seconds.
  7. Note the orientation of the DIMM in the socket so that you can insert the replacement DIMM in the proper orientation.

  8. Eject the DIMM from its slot by slowly pushing apart the two DIMM ejector tabs on either side of the DIMM, and then slide the DIMM out of the slot.

    Note Carefully hold the DIMM by the edges to avoid pressure on the components on the DIMM circuit board.

    The number and placement of system DIMMs depends on the model of your system.

    The following illustration shows the location of system DIMMs:

    drw 2600 dimm repl animated gif
  9. Remove the replacement DIMM from the antistatic shipping bag, hold the DIMM by the corners, and align it to the slot.

    The notch among the pins on the DIMM should line up with the tab in the socket.

  10. Make sure that the DIMM ejector tabs on the connector are in the open position, and then insert the DIMM squarely into the slot.

    The DIMM fits tightly in the slot, but should go in easily. If not, realign the DIMM with the slot and reinsert it.

    Note Visually inspect the DIMM to verify that it is evenly aligned and fully inserted into the slot.
  11. Push carefully, but firmly, on the top edge of the DIMM until the ejector tabs snap into place over the notches at the ends of the DIMM.

  12. Locate the NVMEM battery plug socket, and then squeeze the clip on the face of the battery cable plug to insert it into the socket.

    Make sure that the plug locks down onto the controller module.

  13. Close the controller module cover.

Step 4: Reinstall the controller module

After you replace components in the controller module, reinstall it into the chassis.

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

  2. If you have not already done so, replace the cover on the controller module.

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

  5. Complete the reinstallation of the controller module:

If your system is in…​ Then perform these steps…​

An HA pair

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

  1. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.

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

    The controller begins to boot as soon as it is seated in the chassis.

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

  3. Bind the cables to the cable management device with the hook and loop strap.

  4. When you see the message Press Ctrl-C for Boot Menu, press Ctrl-C to interrupt the boot process.

    Note If you miss the prompt and the controller module boots to ONTAP, enter halt, and then at the LOADER prompt enter boot_ontap, press Ctrl-C when prompted, and then boot to Maintenance mode.
  5. Select the option to boot to Maintenance mode from the displayed menu.

A stand-alone configuration

  1. With the cam handle in the open position, firmly push the controller module in until it meets the midplane and is fully seated, and then close the cam handle to the locked position.

    Note Do not use excessive force when sliding the controller module into the chassis to avoid damaging the connectors.
  2. If you have not already done so, reinstall the cable management device.

  3. Bind the cables to the cable management device with the hook and loop strap.

  4. Reconnect the power cables to the power supplies and to the power sources, turn on the power to start the boot process, and then press Ctrl-C after you see the Press Ctrl-C for Boot Menu message.

    Note If you miss the prompt and the controller module boots to ONTAP, enter halt, and then at the LOADER prompt enter boot_ontap, press Ctrl-C when prompted, and then boot to Maintenance mode.
  5. From the boot menu, select the option for Maintenance mode.

Step 5: Run system-level diagnostics

After installing a new DIMM, you should run diagnostics.

What you’ll need

Your system must be at the LOADER prompt to start System Level Diagnostics.

About this task

All commands in the diagnostic procedures are issued from the node where the component is being replaced.

Steps
  1. If the node to be serviced is not at the LOADER prompt, perform the following steps:

    1. Select the Maintenance mode option from the displayed menu.

    2. After the node boots to Maintenance mode, halt the node: halt

      After you issue the command, you should wait until the system stops at the LOADER prompt.

      Note During the boot process, you can safely respond y to prompts:
      • A prompt warning that when entering Maintenance mode in an HA configuration, you must ensure that the healthy node remains down.

  2. At the LOADER prompt, access the special drivers specifically designed for system-level diagnostics to function properly: boot_diags

    During the boot process, you can safely respond y to the prompts until the Maintenance mode prompt (*>) appears.

  3. Run diagnostics on the system memory: sldiag device run -dev mem

  4. Verify that no hardware problems resulted from the replacement of the DIMMs: sldiag device status -dev mem -long -state failed

    System-level diagnostics returns you to the prompt if there are no test failures, or lists the full status of failures resulting from testing the component.

  5. Proceed based on the result of the preceding step:

If the system-level diagnostics tests…​ Then…​

Were completed without any failures

  1. Clear the status logs: sldiag device clearstatus

  2. Verify that the log was cleared: sldiag device status

    The following default response is displayed:

    SLDIAG: No log messages are present.

  3. Exit Maintenance mode: halt

    The node displays the LOADER prompt.

  4. Boot the node from the LOADER prompt: bye

  5. Return the node to normal operation:

    If your node is in an HA pair, perform a give back: storage failover giveback -ofnode replacement_node_name

    Note: If you disabled automatic giveback, re-enable it with the storage failover modify command.

    If your node is in a stand-alone configuration, proceed to the next step. No action is required.

    You have completed system-level diagnostics.

Resulted in some test failures

Determine the cause of the problem:

  1. Exit Maintenance mode: halt

    After you issue the command, wait until the system stops at the LOADER prompt.

  2. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis:

    • If you have two controller modules in the chassis, leave the power supplies turned on to provide power to the other controller module.

    • If you have one controller module in the chassis, turn off the power supplies and unplug them from the power sources.

  3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.

  4. Boot the controller module you are servicing, interrupting the boot by pressing Ctrl-C when prompted to get to the Boot menu:

    • If you have two controller modules in the chassis, fully seat the controller module you are servicing in the chassis.

      The controller module boots up when fully seated.

    • If you have one controller module in the chassis, connect the power supplies, and then turn them on.

  5. Select Boot to maintenance mode from the menu.

  6. Exit Maintenance mode by entering the following command: halt

    After you issue the command, wait until the system stops at the LOADER prompt.

  7. Rerun the system-level diagnostic test.

  1. Proceed based on the result of the preceding step:

    If the system-level diagnostics tests…​ Then…​

    Were completed without any failures

    1. Clear the status logs: sldiag device clearstatus

    2. Verify that the log was cleared: sldiag device status

      The following default response is displayed:

      SLDIAG: No log messages are present.

    3. Exit Maintenance mode: halt

      The node displays the LOADER prompt.

    4. Boot the node from the LOADER prompt: bye

    5. Return the node to normal operation:

      If your node is in an HA pair, perform a give back: storage failover giveback -ofnode replacement_node_name

      Note If you disabled automatic giveback, re-enable it with the storage failover modify command.

      If your node is in a stand-alone configuration, proceed to the next step. No action is required.

      You have completed system-level diagnostics.

    Resulted in some test failures

    Determine the cause of the problem:

    1. Exit Maintenance mode: halt

      After you issue the command, wait until the system stops at the LOADER prompt.

    2. Turn off or leave on the power supplies, depending on how many controller modules are in the chassis:

      • If you have two controller modules in the chassis, leave the power supplies turned on to provide power to the other controller module.

      • If you have one controller module in the chassis, turn off the power supplies and unplug them from the power sources.

    3. Verify that you have observed all the considerations identified for running system-level diagnostics, that cables are securely connected, and that hardware components are properly installed in the storage system.

    4. Boot the controller module you are servicing, interrupting the boot by pressing Ctrl-C when prompted to get to the Boot menu:

      • If you have two controller modules in the chassis, fully seat the controller module you are servicing in the chassis.

        The controller module boots up when fully seated.

      • If you have one controller module in the chassis, connect the power supplies, and then turn them on.

    5. Select Boot to maintenance mode from the menu.

    6. Exit Maintenance mode by entering the following command: halt

      After you issue the command, wait until the system stops at the LOADER prompt.

    7. Rerun the system-level diagnostic test.

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