Skip to main content

Relocate non-root aggregates from node2 to node3

Contributors netapp-pcarriga netapp-aoife netapp-aherbin
PDFs

Before you can replace node2 with node4, you need to send an AutoSupport message for node2 and then relocate the non-root aggregates that are owned by node2 to node3.

Caution During this procedure, don't relocate aggregates from node3 to node2. Doing so results in aggregates being taken offline and a data outage for the aggregates that are relocated.
Steps

  1. Verify that the partner system ID is set correctly on node3 :

    1. Enter the advanced privilege level:

      set -privilege advanced

    2. Show the partner system ID on node3:

      ha interconnect config show -node <node3-node1>

      The system displays output similar to the following example:

      Show example 
      cluster::*> ha interconnect config show -node <node>
  (system ha interconnect config show)

                       Node: node3-node1
          Interconnect Type: RoCE
            Local System ID: <node3-system-id>
          Partner System ID: <node2-system-id>
       Connection Initiator: local
                  Interface: external

Port   IP Address
----   -----------------
e4a-17   0.0.0.0
e4b-18   0.0.0.0

  2. If "Partner System ID" is incorrect for node3:

    1. Halt node3:

      halt

    2. At the LOADER prompt, set the correct "partner-sysid" value.

      The node3 "partner-sysid" is the system ID of node2, which you can find in the ha interconnect config show output in Step 1.

    3. Save the settings:

      saveenv

    4. At the LOADER prompt, boot node3 into the boot menu:

      boot_ontap menu

    5. Log in to node3.

  3. Send an AutoSupport message to NetApp for node2:

    system node autosupport invoke -node <node2> -type all -message "Upgrading <node2> from <platform_old> to <platform_new>"

  4. Verify that the AutoSupport message was sent:

    system node autosupport show -node <node2> -instance

    The fields "Last Subject Sent:"" and "Last Time Sent:"" contain the message title of the last message that was sent and the time when the message was sent.

  5. Relocate the non-root aggregates:

    1. Set the privilege level to advanced:

      set -privilege advanced

    2. List the aggregates that are owned by node2:

      storage aggregate show -owner-name <node2>

    3. Start aggregate relocation:

      storage aggregate relocation start -node <node2> -destination <node3> -aggregate-list * -ndo-controller-upgrade true

      Note The command locates only non-root aggregates.

    4. When prompted, enter y.

      Relocation occurs in the background. It can take anywhere from a few seconds to a couple of minutes to relocate an aggregate. The time includes both client outage and non-outage portions. The command doesn't relocate any offline or restricted aggregates.

    5. Return to the admin privilege level:

      set -privilege admin

  6. Verify the relocation status of node2:

    storage aggregate relocation show -node <node2>

    The output displays "Done" for an aggregate after it has been relocated.

    Note You must wait until all of the aggregates that are owned by node2 have been relocated to node3 before proceeding to the next step.

  7. Take one of the following actions:

    If relocation of…​ Then…​

    All aggregates was successful

    Go to Step 8.

    Any aggregates failed, or was vetoed

    1. Display a detailed status message:

      storage aggregate show -instance

      You can also check the EMS logs to see the corrective action that is needed.

      Note The event log show command lists any errors that have occurred.

    2. Perform the corrective action.

    3. Set the privilege level to advanced:

      set -privilege advanced

    4. Relocate any failed or vetoed aggregates:

      storage aggregate relocation start -node <node2> -destination <node3> -aggregate-list * -ndo-controllerupgrade true

    5. When prompted, enter y.

    6. Return to the admin privilege level:

      set -privilege admin

    If necessary, you can force the relocation by using one of the following methods:

    • By overriding veto checks:

      storage aggregate relocation start -override-vetoes true -ndo-controller-upgrade

    • By overriding destination checks:

      storage aggregate relocation start -override-destination-checks true -ndocontroller-upgrade

    For more information about the storage aggregate relocation commands, go to References to link to Disk and aggregate management with the CLI and the ONTAP 9 Commands: Manual Page Reference.

  8. Verify that all of the non-root aggregates are online on node3:

    storage aggregate show -node <node3> -state offline -root false

    If any aggregates have gone offline or have become foreign, you must bring them online, once for each aggregate:

    storage aggregate online -aggregate <aggregate_name>

  9. Verify that all of the volumes are online on node3:

    volume show -node <node3> -state offline

    If any volumes are offline on node3, you must bring them online, once for each volume:

    volume online -vserver <Vserver-name> -volume <volume-name>

  10. Verify that node2 doesn't own any online non-root aggregates:

    storage aggregate show -owner-name <node2> -ha-policy sfo -state online

    The command output should not display online non-root aggregates because all of the non-root online aggregates have already been relocated to node3.