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
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:
storage failover show
In the command output, you should see a message that the system ID has changed on the impaired
controller, showing the correct old and new IDs. In the following example, node2 has undergone
replacement and has a new system ID of 151759706.
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)
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 the `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
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.
If the giveback is vetoed, you can consider overriding the vetoes.
Find the High-Availability Configuration content for your version of ONTAP 9
631
To Next Page
Loading...
