Lenovo ThinkSystem DM3010H - 5.10. Chassis Replacement

Step 5: Set time/date after RTC battery replacement
1.
Reset the time and date on the controller:
a.
Check the date and time on the healthy controller with the
show date command.
b.
At the LOADER prompt on the target controller, check the time and date.
c.
If necessary, modify the date with the
set date mm/dd/yyyy command.
d.
If necessary, set the time, in GMT, using the
set time hh:mm:ss command.
e.
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.
Restore automatic giveback by using the
storage failover modify -node local -auto
-giveback true command.
5.
If an AutoSupport maintenance window was triggered, end it by using the
system node
autosupport invoke -node * -type all -message MAINT=END command.
Step 6: Return the failed part to Lenovo
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.10. Chassis
5.10.1. Overview of chassis replacement - DM3010H
To replace the chassis, you must move the power supplies, hard drives, and
controller module or modules from the impaired chassis to the new chassis, and
swap out the impaired chassis from the equipment rack or system cabinet with
the new chassis of the same model as the impaired chassis.
All other components in the system must be functioning properly; if not, you must contact technical
support.
•
You can use this procedure with all versions of ONTAP supported by your system.
•
This procedure is written with the assumption that you are moving all drives and controller
module or modules to the new chassis, and that the chassis is a new component from Lenovo.
•
This procedure is disruptive. For a two-controller cluster, you will have a complete service
outage and a partial outage in a multi-node cluster.
92