Skip to main content
Install and maintain

Recable and give back the controller - AFF A70, AFF A90

Contributors dougthomp
PDFs

Continue the replacement procedure by recabling the storage, network connections and giving back the controller.

Step 1: Recable the system

Recable the controller module's storage and network connections.

Steps

  1. Recable the the controller module to storage and network conntections.

  2. Verify that the cabling is correct by using Active IQ Config Advisor.

    1. Download and install Config Advisor.

    2. Enter the information for the target system, and then click Collect Data.

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

    4. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor.

Step 2: Give back the controller

  1. If your storage system has Encryption configured, you must restore Storage or Volume Encryption functionality using the following procedure to reboot the system:

    1. Boot to Menu and run Option 10

    2. Input the passphrase & backup up data, then do Normal boot see Restore onboard key management encryption keys.

    3. Perform CFO only giveback

    4. Perform Onboard Sync and verify SVM-KEK is set to true see Giveback after MB replacement fails - operation was vetoed by keymanager

    5. Giveback SFO, (no force)

  2. If your system does not have Encryption configured, complete the following procedure to reboot the system:

    1. Boot to Menu and run Option 1.

    2. Give back the controller:

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

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

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

    4. After the giveback has been completed, confirm that the HA pair is healthy and that takeover is possible: storage failover show

  3. If the system is in a MetroCluster configuration, monitor the status of the controller: metrocluster node show

    The MetroCluster configuration takes a few minutes after the replacement to return to a normal state, at which time each controller will show a configured state, with DR Mirroring enabled and a mode of normal. The metrocluster node show -fields node-systemid command output displays the old system ID until the MetroCluster configuration returns to a normal state.

  4. If the controller is in a MetroCluster configuration, depending on the MetroCluster state, verify that the DR home ID field shows the original owner of the disk if the original owner is a controller on the disaster site.

    This is required if both of the following are true:

  5. If your system is in a MetroCluster configuration, verify that each controller is configured: metrocluster node show - fields configuration-state

    node1_siteA::> metrocluster node show -fields configuration-state

dr-group-id            cluster node           configuration-state
-----------            ---------------------- -------------- -------------------
1 node1_siteA          node1mcc-001           configured
1 node1_siteA          node1mcc-002           configured
1 node1_siteB          node1mcc-003           configured
1 node1_siteB          node1mcc-004           configured

4 entries were displayed.

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

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