controller-replace-recable-reassign-disks.adoc

permalink	sidebar	keywords	summary
fas2600/controller-replace-recable-reassign-disks.html	sidebar	fas2600, how to recable the system, how to reassign disks	You must recable the storage and confirm disk reassignment.

Recable the system and reassign disks - FAS2600

Continue the replacement procedure by recabling the storage and confirming disk reassignment.

Step 1: Recable the system

../_include/recable_system_after_controller_rep.adoc

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. In a stand-alone system, you must manually reassign the ID to the disks. You must use the correct procedure for your configuration.

Option 1: Verify the system ID change on an HA system

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.

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, entering y if you are prompted to override the system ID due to a system ID mismatch: boot_ontap

3. 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)

4. From the healthy controller, verify that any coredumps are saved:

   1. Change to the advanced privilege level: set -privilege advanced

      You can respond Y when prompted to continue into advanced mode. The advanced mode prompt appears (*>).

   2. Save any coredumps: system node run -node local-node-name partner savecore

   3. 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

   4. Return to the admin privilege level: set -privilege admin

5. If your storage system has Storage or Volume Encryption configured, you must restore Storage or Volume Encryption functionality by using one of the following procedures, depending on whether you are using onboard or external key management:

   • Restore onboard key management encryption keys

   • Restore external key management encryption keys

6. Give back the controller:

   1. 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.

      Note	If the giveback is vetoed, you can consider overriding the vetoes.

      Find the High-Availability Configuration content for your version of ONTAP 9

   2. 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 show command should not include the System ID changed on partner message.

7. 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
   .
   .
   .

8. Verify that the expected volumes are present for each controller: vol show -node node-name

9. If you disabled automatic takeover on reboot, enable it from the healthy controller: storage failover modify -node replacement-node-name -onreboot true

Option 2: Manually reassign the system ID on a stand-alone system in ONTAP

../_include/standalone_reassign_sysid.adoc