Relocate node2’s non-root aggregates from node3 to node4


Having relocated node2’s non-root aggregates to node3, you now must relocate them from node3 to node4.

  1. Enter the following command on either controller, and examine the output to identify which non-root aggregates to relocate:

    storage aggregate show -owner-name <node3> -home-id <node2_system_id>

  2. Relocate the aggregates by completing the following substeps:

    1. Access the advanced privilege level by entering the following command on either node:

      set -privilege advanced

    2. Enter the following command:

      storage aggregate relocation start -node <node3> -destination <node4> -aggregate-list <aggr_name1, aggr_name2…​> -ndo-controller-upgrade true

      The aggregate list is the list of aggregates owned by node4 that you obtained in Step 1.

    3. When prompted, enter y.

      Relocation occurs in the background. It could 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 does not relocate any offline or restricted aggregates.

    4. Return to the admin level:

      set -privilege admin

  3. Check the relocation status:

    storage aggregate relocation show -node <node3>

    The output will display Done for an aggregate after it has been relocated.

    Note Wait until all the node2 aggregates have been relocated to node4 before proceeding to the next step.
  4. Take one of the following actions:

    If relocation of…​ Then…​

    All aggregates was successful

    Go to Step 5.

    Any aggregates failed, or were vetoed

    1. Check the EMS logs for the corrective action.

    2. Perform the corrective action.

    3. Access the advanced privilege level by entering the following command on either node:

      set -privilege advanced

    4. Relocate any failed or vetoed aggregates:

      storage aggregate relocation start -node <node3> destination <node4> -aggregate-list <aggr_name1, aggr_name2…​> ndo-controller-upgrade true

      The aggregate list is the list of failed or vetoed aggregates.

    5. When prompted, enter y.

    6. Return to the admin level by entering the following command:

      set -privilege admin

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

    • Overriding veto checks:

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

    • Overriding destination checks:

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

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

  5. Verify that all node2 non-root aggregates are online and their state on node4:

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

    The node2 aggregates were listed in the output of the command in Step 1.

  6. If any aggregate has gone offline or become foreign, bring it online by using the following command for each aggregate:

    storage aggregate online -aggregate <aggr_name>

  7. Verify that all the volumes in node2 aggregates are online on node4:

    volume show -node <node4> -state offline

  8. If any volumes are offline on node4, bring them online:

    volume online -vserver <vserver-name> -volume <volume_name>

  9. Send a post-upgrade AutoSupport message to NetApp for node4:

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