Step 5: Reassigning disks
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.
Disk reassignment is only needed when replacing the NVRAM module.
Steps
1.
If the replacement controller is in Maintenance mode (showing the *> prompt), exit Maintenance mode and
go to the LOADER prompt:
halt
2. From the LOADER prompt on the replacement controller, boot the controller and entering y if you are
prompted to override the system ID due to a system ID mismatch.
3. Wait until the Waiting for giveback… message is displayed on the console of the controller with the
replacement module 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. 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.
For more information, see the
Manual giveback commands topic to override the veto.
b. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is
possible: storage failover show
790
To Next Page
Loading...
