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.
You must be sure to issue the commands in this procedure on the correct node:
• The impaired node is the node on which you are performing maintenance.
• The replacement node is the new node that replaced the impaired node as part of this procedure.
• The healthy node is the DR partner of the impaired node.
Steps
1. If you have not already done so, reboot the replacement node, interrupt the boot process by entering
Ctrl-C, and then select the option to boot to Maintenance mode from the displayed menu.
You must enter
Y when prompted to override the system ID due to a system ID mismatch.
2.
View the old system IDs from the healthy node:
metrocluster node show -fields node-
systemid,dr-partner-systemid
In this example, the Node_B_1 is the old node, with the old system ID of 118073209:
70
To Next Page
Loading...
