Skip to main content
Install and maintain

Replace the real-time clock battery - AFF A70, AFF A90

Contributors dougthomp
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

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 module

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

  1. On the front of the chassis, use your thumbs to firmly push each drive in until you feel a positive stop. This ensures that the drives are firmly seated against the chassis midplane.

    drw a800 drive seated IEOPS 960

  2. Check the amber NVRAM that status LED located in slot 4/5 on the back of the impaired controller module is off. Look for the NV icon.

    NVRAM attention and status LED location graphic

    Callout number 1

    NVRAM status LED

    Callout number 1

    NVRAM attention LED
    Note If the NVRAM status LED is flashing, it could mean the controller module was not taken over or halted properly (uncommitted data). If the impaired controller module was not successfully taken over by the partner controller module, contact NetApp Support before continuing with this procedure.

    The general behavior of the NVRAM status LED on the impaired controller module is as follows:

    • The NVRAM status LED flashes when power is removed from the controller module and the storage system is in the "waiting for giveback" state, or the controller module is not taken over or halted properly (uncommitted data).

    • The NVRAM status LED flashes when the controller module is removed from the chassis and could mean the controller module is not taken over or halted properly (uncommitted data). Confirm that the controller module has been cleanly takeover by the partner controller module or the impaired controller module shows waiting for giveback. Then, the flashing LED can be ignored (and the controller module can be removed from the chassis).

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

  4. Unplug the controller module power supply cables from the controller module power supplies (PSU).

    Note If your system has DC power, disconnect the power block from the PSUs.

  5. Unplug the system cables and SFP and QSFP modules (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.

  6. Remove the cable management device from the controller module.

  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.

    Controller remove graphic

    Callout number 1

    a Locking latch

    Callout number 2

    Locking pin

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

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

Step 3: Replace the RTC battery

Remove failed RTC battery and install the replacement RTC battery.

  1. Open the controller air duct on the top of the controller.

    1. Insert your fingers in the recesses at the far ends of the air duct.

    2. Lift the air duct and rotate it upward as far as it will go.

  2. Locate the RTC battery under the air duct.

    Replace the RTC battery

    Callout number 1

    RTC battery and 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. Note the polarity of the RTC battery, and then insert it into the holder by tilting the battery at an angle and pushing down.

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

Step 4: Reinstall the controller module

Reinstall the controller module and reboot it.

  1. Ensure the air duct is completely closed by rotating it down as far as it will go.

    It must lie flush against the controller module sheet metal.

  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. Recable the system, as needed.

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

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

    1. Rotate the locking latches upward into the locked position.

  5. Plug the power cords into the power supplies.

    Note If you have DC power supplies, reconnect the power block to the power supplies after the controller module is fully seated in the chassis.

    The controller module boots when power is restored. If it boots to the LOADER prompt, reboot the controller with the boot_ontap command.

  6. Restore automatic giveback if you disabled it by using the storage failover modify -node local -auto-giveback true command.

  7. If AutoSupport is enabled, restore/unsuppress automatic case creation by using the system node autosupport invoke -node * -type all -message MAINT=END command.

Step 5: Reset the time and date on the controller

Note After replacing the RTC battery, inserting controller and powering on first BIOS reset, you will see the following error messages: RTC date/time error. Reset date/time to default RTC power failure error These messages are excpected and you can continue with this procedure.

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

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. At the LOADER prompt on the target controller, check the time and date with the cluster date show command.

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

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

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