Lenovo ThinkSystem DM3000 series Hardware Installation And Maintenance Manual page 63

Verifying the system ID change on an HA system
You must confirm the system ID change when you boot the replacement controller and then verify that the
change was implemented.
This procedure applies only to systems running ONTAP in an HA pair.
Step 1. If the replacement controller is in Maintenance mode (showing the
mode and go to the LOADER prompt: halt
From the LOADER prompt on the replacement controller, boot the controller, entering y if you are
Step 2.
prompted to override the system ID due to a system ID mismatch:boot_ontap
Wait until the Waiting for giveback... message is displayed on the replacement controller console
Step 3.
and then, from the healthy controller, verify that the new partner system ID has been automatically
assigned.
Example
node1> storage failover show
Node
------------
node1
node2
Step 4. From the healthy controller, verify that any coredumps are saved:
Change to the advanced privilege level: set -privilege advanced
a.
You can respond Y when prompted to continue into advanced mode. The advanced mode
prompt appears (*>).
Save any coredumps: system node run -node local-node-name partner savecore
b.
c. Wait for savecore command to complete before issuing the giveback.You can enter the
following command to monitor the progress of the savecore command: system node run -node
local-node-name partner savecore -s
Return to the admin privilege level: set -privilege admin
d.
Step 5. Give back the controller:
From the healthy controller, give back the replaced controller's storage: storage failover
a.
giveback -ofnode replacement_node_name
The replacement controller takes back its storage and completes booting.
If you are prompted to override the system ID due to a system ID mismatch, you should enter
y.
Note: If the giveback is vetoed, you can consider overriding the vetoes.
Availability Configuration Guide for your version of ONTAP 9
b. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is
possible: s s t t o o r r a a g g e e f f a a i i l l o o v v e e r r s s h h o o w w
The output from the s s t t o o r r a a g g e e f f a a i i l l o o v v e e r r s s h h o o w w command should not include the System ID
changed on partner message.
Verify that the expected volumes are present for each controller: vol show -node node-name
Step 6.
If you disabled automatic takeover on reboot, enable it from the healthy controller: storage failover
Step 7.
modify -node replacement-node-name -onreboot true
Takeover
Partner Possible
------------ --------
node2 false
node1 -
� >
State Description
-------------------------------------
System ID changed on partner (Old:
151759755, New: 151759706), In takeover
Waiting for giveback (HA mailboxes)
.
Chapter 5 Hardware replacement procedures
prompt, exit Maintenance
Find the High-
57