IBM N7800 Hardware And Service Manual page 149

As the replacement node boots up the second time, it might again display
the prompt warning of a system ID mismatch and asking to override the
system ID. You can respond Y.
If the giveback is vetoed, you can consider forcing giveback by issuing the
following command:
storage failover giveback -ofnode partner_node_name
-require-partner-waiting true -override-vetoes true
If you are using Data ONTAP 8.2, see the Clustered Data ONTAP
High-Availability Configuration Guide on the IBM N series support website for
information on giveback vetoes.
b. Enter the following command from the healthy node:
storage failover giveback -ofnode replacement_node_name
As the replacement node boots up, it might again display the prompt
warning of a system ID mismatch and asking to override the system ID.
You can respond y. The replacement node takes back its storage and
completes booting up to the Data ONTAP prompt.
c. Enter the storage failover show-giveback command to monitor the
progress of the giveback operation.
d. Wait until the storage failover show-giveback command output indicates
that the giveback operation is complete.
e. Enter the storage failover show command to confirm that the HA pair is
healthy and takeover is possible. The output from the storage failover
show command should not include the "System ID changed on partner"
message.
8. Verify that the disks (or gateway LUNs) were assigned correctly by entering the
following command:
storage disk show -sanown
Make sure that the disks belonging to the replacement node show the new
system ID for the replacement node. In the following example, the disks owned
by node2 now show the new system ID, 1873774574:
node1> storage disk show -sanown
Disk Aggregate Home
-------- --------- ----------- ------------- ----------- ---------- -----------
node2:0b.17 aggr1
node1:0a.17 aggr1
.
.
.
9. Verify that the expected volumes are present for each node by entering the
following command:
vol show -node node-name
Manually reassigning the system ID on a stand-alone system in clustered Data
ONTAP:
In a stand-alone system, you must manually reassign disks to the new controller's
system ID and set the bootarg.init.boot_clustered bootarg before you return the
system to normal operating condition.
About this task
This procedure applies only to systems that are:
v Operating in clustered Data ONTAP.
Owner Home ID
node2 node2 1873774574 1873774574 1873774574
node1 node1 118065578
Chapter 5. Replacing N7000 series system devices
Owner ID Reserver
118065578 118065578
123