Lenovo ThinkSystem DM3010H - Real-Time Clock Battery; Replace the Real-Time Clock Battery - DM3010 H; Step 1: Shut down the Impaired Controller

The power supply LEDs are lit when the power supply comes online.
If you are instructed to return the component, follow all packaging instructions, and use any
packaging materials for shipping that are supplied to you.
5.9. Real-time clock battery
5.9.1. Replace the real-time clock battery - DM3010H
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
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 Lenovo 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
87