Recable the system and reassign disks - AFF A320
Continue the replacement procedure by recabling the storage and confirming disk reassignment.
Step 1: Recable the system
After running diagnostics, you must recable the controller module’s storage and network connections.
Recable the system.
Verify that the cabling is correct by using Active IQ Config Advisor.
Download and install Config Advisor.
Enter the information for the target system, and then click Collect Data.
Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and all disks appear in the output, correcting any cabling issues you find.
Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor.
Step 2: Reassign disks
If the storage system is in an HA pair, the system ID of the new controller module is automatically assigned to the disks when the giveback occurs at the end of the procedure. 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.
If the replacement controller is in Maintenance mode (showing the
*>prompt, exit Maintenance mode and go to the LOADER prompt:
From the LOADER prompt on the replacement controller, boot the controller, entering
yif you are prompted to override the system ID due to a system ID mismatch:
Wait until the
Waiting for giveback…message is displayed on the replacement controller console 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)
From the healthy controller, verify that any coredumps are saved:
Change to the advanced privilege level:
set -privilege advanced
You can respond
Ywhen prompted to continue into advanced mode. The advanced mode prompt appears (*>).
Save any coredumps:
system node run -node local-node-name partner savecore
Wait for the `savecore`command to complete before issuing the giveback.
You can enter the following command to monitor the progress of the savecore command:
system node run -node local-node-name partner savecore -s
Return to the admin privilege level:
set -privilege admin
Give back the controller:
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
If the giveback is vetoed, you can consider overriding the vetoes.
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 showcommand should not include the System ID changed on partner message.
Verify that the disks were assigned correctly:
storage disk show -ownership
The disks belonging to the replacement controller 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 . . .
Verify that the expected volumes are present for each controller:
vol show -node node-name
If you disabled automatic takeover on reboot, enable it from the healthy controller:
storage failover modify -node replacement-node-name -onreboot true