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 node:
a.
From the healthy node, give back the replaced node’s storage:
storage failover giveback
-ofnode replacement_node_name
The replacement node 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
b. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is
possible:
storage failover show
The output from the storage failover show command should not include the System ID changed
on partner message.
6.
Verify that the disks were assigned correctly:
storage disk show -ownership
The disks belonging to the replacement node should show the new system ID. In the following example,
the disks owned by node1 now show the new system ID, 1873775277:
node1> `storage disk show -ownership`
Disk Aggregate Home Owner DR Home Home ID Owner ID DR Home ID
Reserver Pool
----- ------ ----- ------ -------- ------- ------- -------
--------- ---
1.0.0 aggr0_1 node1 node1 - 1873775277 1873775277 -
1873775277 Pool0
1.0.1 aggr0_1 node1 node1 1873775277 1873775277 -
1873775277 Pool0
.
.
.
Option 2: Manually reassign the system ID on systems in a two-node MetroCluster configuration
In a two-node MetroCluster configuration running ONTAP, you must manually reassign disks to the new
controller’s system ID before you return the system to normal operating condition.
About this task
This procedure applies only to systems in a two-node MetroCluster configuration running ONTAP.
435
To Next Page
Loading...
