Skip to main content
Install and maintain

Replacing the real-time clock battery - AFF A900

Contributors dougthomp netapp-adityaw netapp-martyh
PDFs

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 impaired controller

Shut down or take over the impaired controller using one of the following options.

Option 1: Most systems

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

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

  • 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 controller: storage failover modify –node local -auto-giveback false

  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 (enter system password)

    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

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. Unplug the cables from the impaired controller module, and keep track of where the cables were connected.

  3. Slide the terra cotta button on the cam handle downward until it unlocks.

    Animation - Remove the controller
    Release the controller

    Callout number 1

    Cam handle release button

    Callout number 2

    Cam handle

  4. Rotate the cam handle so that it completely disengages the controller module from the chassis, and then slide the controller module out of the chassis.

    Make sure that you support the bottom of the controller module as you slide it out of the chassis.

  5. Place the controller module lid-side up on a stable, flat surface, press the blue button on the cover, slide the cover to the back of the controller module, and then swing the cover up and lift it off of the controller module.

Lift the cover off the controller module

Callout number 1

Controller module cover locking button

Step 3: Replace the RTC battery

To replace the RTC battery, you must locate the failed battery in the controller module, remove it from the holder, and then install the replacement battery in the holder.

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

  2. Locate the RTC battery.

    Animation - Replace RTC battery
    Remove and install the RTC battery

    Callout number 1

    RTC battery

    Callout number 2

    RTC battery housing

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

  4. Remove the replacement battery from the antistatic shipping bag.

  5. Locate the empty battery holder in the controller module.

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

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

  8. Reinstall the controller module cover.

Step 4: Reinstall the controller module and set time/date

After you replace the RTC battery, you must reinstall the controller module. If the RTC battery has been left out of the controller module for more than 10 minutes, you may have to reset the time and date.

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

      Important 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, and then turn on the power to start the boot process.

    5. Halt the controller at the LOADER prompt.

Note If your system stops at the boot menu, select the option for "Reboot node" and respond y when prompted, then boot to LOADER by pressing Ctrl-C.

  1. Reset the time and date on the controller:

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

    2. At the LOADER prompt on the target controller, 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 controller.

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

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

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

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.