Lenovo ThinkSystem DM3010H - Step 1: Shut down the Impaired Controller; Step 2: Remove Controller Module

All other components in the system must be functioning properly; if not, you must contact technical
support.
You must replace the failed component with a replacement FRU component you received from your
provider.
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.
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_down_h
The following AutoSupport message suppresses automatic case creation for two hours:
cluster1:*> system node autosupport invoke -node * -type all -message MAINT=2h
2.
If the impaired controller is part of an HA pair, 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 Remove controller module.
Waiting for giveback… Press Ctrl-C, and then respond y.
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 controller module
Remove the controller module from the system and then remove the controller module cover.
Steps
64