Skip to main content
Install and maintain

Replace an NVDIMM - AFF A320

Contributors

You must replace the NVDIMM in the controller module when your system registers that the flash lifetime is almost at an end or that the identified NVDIMM is not healthy in general; failure to do so causes a system panic.

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 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 are using NetApp Storage Encryption, you must have reset the MSID using the instructions in the Returning SEDs to unprotected mode.

  • If you have a SAN system, you must have checked event messages (cluster kernel-service show) for impaired controller SCSI blade. The cluster kernel-service show command 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=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

    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: Remove the controller module

To access components inside the controller module, you must remove the controller module from the chassis.

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

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

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

    drw a320 cable management arms

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

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

  5. Remove the controller module from the chassis:

    drw a320 controller remove animated gif
    1. Insert your forefinger into the latching mechanism on either side of the controller module.

    2. Press down on the orange tab on top of the latching mechanism until it clears the latching pin on the chassis.

      The latching mechanism hook should be nearly vertical and should be clear of the chassis pin.

    3. Gently pull the controller module a few inches toward you so that you can grasp the controller module sides.

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

Step 3: Replace the NVDIMM

To replace the NVDIMM, you must locate it in the controller module using the NVDIMM map label on top of the air duct, and then replace it following the specific sequence of steps.

drw a320 nvdimm replace animated gif
  1. Open the air duct and then locate the NVDIMM in slot 11 on your controller module.

    Note The NVDIMM looks significantly different than system DIMMs.
  2. Note the orientation of the NVDIMM in the socket so that you can insert the NVDIMM in the replacement controller module in the proper orientation.

  3. Eject the NVDIMM from its slot by slowly pushing apart the two NVDIMM ejector tabs on either side of the NVDIMM, and then slide the NVDIMM out of the socket and set it aside.

    Note Carefully hold the NVDIMM by the edges to avoid pressure on the components on the NVDIMM circuit board.
  4. Remove the replacement NVDIMM from the antistatic shipping bag, hold the NVDIMM by the corners, and then align it to the slot.

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

  5. Locate the slot where you are installing the NVDIMM.

  6. Insert the NVDIMM squarely into the slot.

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

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

  8. Close the air duct.

Step 4: Install the controller module

After you have replaced the component in the controller module, you must reinstall the controller module into the chassis.

  1. If you have not already done so, close the air duct at the rear of the controller module and reinstall the cover over the PCIe cards.

  2. 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.
  3. Cable the management and console ports only, so that you can access the system to perform the tasks in the following sections.

    Note You will connect the rest of the cables to the controller module later in this procedure.
  4. Complete the reinstallation of the controller module:

    1. Make sure the latch arms are locked in the extended position.

    2. Using the latch arms, push the controller module into the chassis bay until it stops.

    3. Press down and hold the orange tabs on top of the latching mechanism.

    4. Gently push the controller module into the chassis bay until it is flush with the edges of the chassis.

      Note The latching mechanism arms slide into the chassis.

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

    5. Release the latches to lock the controller module into place.

    6. Recable the power supply.

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

Step 5: Restore the controller module to operation

You must recable the system, give back the controller module, and then reenable automatic giveback.

  1. 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.

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

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

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