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
� > prompt, exit Maintenance
mode and go to the LOADER prompt: halt
Step 2. From the LOADER prompt on the replacement controller, boot the controller, entering y if you are
prompted to override the system ID due to a system ID mismatch:boot_ontap
Step 3. Wait until the Waiting for giveback... message is displayed on the replacement controller console
and then, from the healthy controller, verify that the new partner system ID has been automatically
assigned.
Example
node1> storage failover show
Takeover
Node Partner Possible State Description
------------ ------------ -------- -------------------------------------
node1 node2 false System ID changed on partner (Old:
151759755, New: 151759706), In takeover
node2 node1 - Waiting for giveback (HA mailboxes)
Step 4. From the healthy controller, verify that any coredumps are saved:
a. Change to the advanced privilege level: set -privilege advanced
You can respond Y when prompted to continue into advanced mode. The advanced mode
prompt appears (*>).
b. Save any coredumps: system node run -node local-node-name partner savecore
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
d. Return to the admin privilege level: set -privilege admin
Step 5. Give back the controller:
a. From the healthy controller, give back the replaced controller's storage: storage failover
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.
Find the High-
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: ssttoorraaggee ffaaiilloovveerr sshhooww
The output from the ssttoorraaggee ffaaiilloovveerr sshhooww command should not include the System ID
changed on partner message.
Step 6. Verify that the expected volumes are present for each controller: vol show -node node-name
Step 7. If you disabled automatic takeover on reboot, enable it from the healthy controller: storage failover
modify -node replacement-node-name -onreboot true
Chapter 5. Hardware replacement procedures 57
To Next Page
Loading...
Need help?
General