Replace the real-time clock battery - AFF A320

Contributors dougthomp netapp-martyh thrisun

You replace the real-time clock (RTC) battery in the controller module so that your system’s services and applications that depend on accurate time synchronization continue to function.

  • You can use this procedure with all versions of ONTAP supported by your system

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

Step 1: Shut down the node

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: Replace the RTC battery

You need to locate the RTC battery inside the controller module, and then follow the specific sequence of steps.

Step 3: 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 controller cable unplug animated gif

    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.

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

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

Step 4: Replace the RTC battery

drw a320 rtc batt replace animated gif
  1. Remove the PCIe cover.

    1. Unscrew the blue thumbscrew located above the onboard ports at the back of the controller module.

    2. Slide the cover toward you and rotate the cover upward.

    3. Remove the cover and set it aside.

  2. Locate, remove, and then replace the RTC battery:

    1. Using the FRU map, locate the RTC battery on the controller module.

    2. Gently push the battery away from the holder, rotate it away from the holder, and then lift it out of the holder.

      Note Note the polarity of the battery as you remove it from the holder. The battery is marked with a plus sign and must be positioned in the holder correctly. A plus sign near the holder tells you how the battery should be positioned.
    3. Remove the replacement battery from the antistatic shipping bag.

    4. Note the polarity of the RTC battery, and then insert it into the holder by tilting the battery at an angle and pushing down.

  3. Visually inspect the battery to make sure that it is completely installed into the holder and that the polarity is correct.

  4. Reinstall the PCIe cover on the controller module.

Step 5: Reinstall the controller module and setting time/date after RTC battery replacement

After you replace a component within the controller module, you must reinstall the controller module in the system chassis, reset the time and date on the controller, and then boot it.

  1. If you have not already done so, close the air duct or controller module cover.

  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.

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

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

  4. If the power supplies were unplugged, plug them back in and reinstall the power cable retainers.

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

      Note Do not push down on the latching mechanism at the top of the latch arms. Doing so with raise the locking mechanism and prohibit sliding the controller module into the chassis.
    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. If you have not already done so, reinstall the cable management device.

    7. Halt the controller at the LOADER prompt.

  6. Reset the time and date on the controller:

    1. Check the date and time on the healthy node with the show date command.

    2. At the LOADER prompt on the target node, check the time and date.

    3. If necessary, modify the date with the set date mm/dd/yyyy command.

    4. If necessary, set the time, in GMT, using the set time hh:mm:ss command.

    5. Confirm the date and time on the target node.

  7. At the LOADER prompt, enter bye to reinitialize the PCIe cards and other components and let the node reboot.

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

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

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.