Reassign the root aggregate disks to the new MetroCluster IP controller module
Reassign the root aggregate disks to the new controller module using the system IDs that you gathered earlier.
The old system IDs were identified in Gather information before the upgrade.
You perform the steps in Maintenance mode.
|
Root aggregate disks are the only disks that must be reassigned during the controller upgrade process. Disk ownership of data aggregates is handled as part of the switchover/switchback operation. |
-
Boot the system to Maintenance mode:
boot_ontap maint
-
Display the disks on node_B_1-new from the Maintenance mode prompt:
disk show -a
Before you proceed with disk reassignment, verify that the pool0 and pool1 disks that belong to the node's root aggregate are displayed in the disk show
output. In the following example, the output lists the pool0 and pool1 disks owned by node_B_1-old.The command output shows the system ID of the new controller module (1574774970). However, the old system ID (537403322) still owns the root aggregate disks. This example doesn't show drives owned by other nodes in the MetroCluster configuration.
*> disk show -a Local System ID: 1574774970 DISK OWNER POOL SERIAL NUMBER HOME DR HOME ------------ --------- ----- ------------- ------------- ------------- prod3-rk18:9.126L44 node_B_1-old(537403322) Pool1 PZHYN0MD node_B_1-old(537403322) node_B_1-old(537403322) prod4-rk18:9.126L49 node_B_1-old(537403322) Pool1 PPG3J5HA node_B_1-old(537403322) node_B_1-old(537403322) prod4-rk18:8.126L21 node_B_1-old(537403322) Pool1 PZHTDSZD node_B_1-old(537403322) node_B_1-old(537403322) prod2-rk18:8.126L2 node_B_1-old(537403322) Pool0 S0M1J2CF node_B_1-old(537403322) node_B_1-old(537403322) prod2-rk18:8.126L3 node_B_1-old(537403322) Pool0 S0M0CQM5 node_B_1-old(537403322) node_B_1-old(537403322) prod1-rk18:9.126L27 node_B_1-old(537403322) Pool0 S0M1PSDW node_B_1-old(537403322) node_B_1-old(537403322) . . .
-
Reassign the root aggregate disks on the drive shelves to the new controllers.
If you are using ADP…
Then use this command…
Yes
disk reassign -s <old-sysid> -d <new-sysid> -r <dr-partner-sysid>
No
disk reassign -s <old-sysid> -d <new-sysid>
-
Reassign the root aggregate disks on the drive shelves to the new controllers:
disk reassign -s <old-sysid> -d <new-sysid>
The following example shows reassignment of drives in a non-ADP configuration:
*> disk reassign -s 537403322 -d 1574774970 Partner node must not be in Takeover mode during disk reassignment from maintenance mode. Serious problems could result!! Do not proceed with reassignment if the partner is in takeover mode. Abort reassignment (y/n)? n After the node becomes operational, you must perform a takeover and giveback of the HA partner node to ensure disk reassignment is successful. Do you want to continue (y/n)? y Disk ownership will be updated on all disks previously belonging to Filer with sysid 537403322. Do you want to continue (y/n)? y
-
Verify that the disks of the root aggregate are correctly reassigned:
disk show
storage aggr status
*> disk show Local System ID: 537097247 DISK OWNER POOL SERIAL NUMBER HOME DR HOME ------------ ------------- ----- ------------- ------------- ------------- prod03-rk18:8.126L18 node_B_1-new(537097247) Pool1 PZHYN0MD node_B_1-new(537097247) node_B_1-new(537097247) prod04-rk18:9.126L49 node_B_1-new(537097247) Pool1 PPG3J5HA node_B_1-new(537097247) node_B_1-new(537097247) prod04-rk18:8.126L21 node_B_1-new(537097247) Pool1 PZHTDSZD node_B_1-new(537097247) node_B_1-new(537097247) prod02-rk18:8.126L2 node_B_1-new(537097247) Pool0 S0M1J2CF node_B_1-new(537097247) node_B_1-new(537097247) prod02-rk18:9.126L29 node_B_1-new(537097247) Pool0 S0M0CQM5 node_B_1-new(537097247) node_B_1-new(537097247) prod01-rk18:8.126L1 node_B_1-new(537097247) Pool0 S0M1PSDW node_B_1-new(537097247) node_B_1-new(537097247) ::> ::> aggr status Aggr State Status Options aggr0_node_B_1 online raid_dp, aggr root, nosnap=on, mirrored mirror_resync_priority=high(fixed) fast zeroed 64-bit