Skip to main content

Move node1 non-root aggregates and NAS data LIFs from node2 to the upgraded node1

Contributors netapp-pcarriga
PDFs

After you verify network configuration on node1 and before you relocate aggregates from node2 to node1, you verify that the NAS data LIFs belonging to node1 that are currently on node2 are relocated from node2 to node1. You must also verify that the SAN LIFs exist on node1.

About this task

Remote LIFs handle traffic to SAN LUNs during the upgrade procedure. Moving SAN LIFs is not necessary for cluster or service health during the upgrade. SAN LIFs are not moved unless they need to be mapped to new ports. After you bring node1 online, you must verify that the LIFs are healthy and located on the appropriate ports.

Steps

  1. Resume the relocation operation:

    system controller replace resume

    The system performs the following tasks:

    • Cluster quorum check

    • System ID check

    • Image version check

    • Target platform check

    • Network reachability check

    The operation pauses at this stage in the network reachability check.

  2. Perform a network reachability check:

    network port reachability show -node node1

    Confirm that all connected ports, including the interface group and VLAN ports, show their status as OK.

  3. For the following upgrades, you must reassign the FCP SAN LIFs.

    Existing system Replacement system

    AFF A250

    AFF A30, AFF A50

    AFF C250

    AFF C30, AFF C60

    AFF A800

    AFF A70, AFF A90

    AFF C800

    AFF C80

    For all other system upgrades, proceed to Step 4.

    1. Reassign FCP SAN LIFs used for FCP or FC-NVMe data access to the correct home ports:

      network interface show -vserver <vserver_hosting_fcp_lifs>

    2. For LIFs with the current node as the upgraded node1 and the current port reports "status oper" as "-" (because the port existed on the AFF A800 node but does not exist on the AFF A90 node), modify the current port before it can be brought online.

      Verify that physical connectivity is established to the FC target port where the FC LIF needs to be moved:

      1. Set the LIF status to "down":

        network interface modify -vserver <vserver_name> -lif <lif_name> -status-admin down

      2. Modify the home port of the LIF:

        network interface modify -vserver <vserver_name> -lif <lif_name> - home-node <node1> -home-port <FC_target_port>

      3. Set the LIF status to "up":

        network interface modify -vserver <vserver> -lif <lif_name> -status-admin up

      Repeat Substeps a and b for each FC SAN LIF that is home on node1.

  4. Resume the relocation operation:

    system controller replace resume

    The system performs the following checks:

    • Cluster health check

    • Cluster LIF status check

    After performing these checks, the system relocates the non-root aggregates and NAS data LIFs owned by node1 to the new node1.

    The controller replacement operation pauses after the resource relocation is complete.

  5. Check the status of the aggregate relocation and NAS data LIF move operations:

    system controller replace show-details

    If the controller replacement procedure is paused, check and correct the error, if any, and then issue resume to continue the operation.

  6. If necessary, restore and revert any displaced LIFs. List any displaced LIFs:

    cluster controller-replacement network displaced-interface show

    If any LIFs are displaced, restore the home node back to node1:

    cluster controller-replacement network displaced-interface restore-home-node

  7. Resume the operation to prompt the system to perform the required post-checks:

    system controller replace resume

    The system performs the following post-checks:

    • Cluster quorum check

    • Cluster health check

    • Aggregates reconstruction check

    • Aggregate status check

    • Disk status check

    • Cluster LIF status check

    • Volume check