Skip to main content

Move non-root aggregates and NAS data LIFs owned by node2 from node3 to node4

Contributors netapp-pcarriga netapp-aoife netapp-aherbin
PDFs

After verifying the network configuration on node4, you need to relocate the NAS data LIFs owned by node2 from node3 to node4 and confirm that the SAN LIFs exist on node4.

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.

You verify that the LIFs are healthy and located on the correct ports after you bring node4 online.

Note If you are changing the port speed of the T6-based Ethernet network interface cards or motherboard ports, you might observe malformed packets being received after the speed conversion. See NetApp Bugs Online Bug ID 1570339 and the knowledge base article CRC errors on T6 ports after converting from 40GbE to 100GbE for guidance.
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 system pauses the operation at this stage in the network reachability check.

  2. 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 node2 to the new controller, node4.
    The controller replacement operation pauses after the resource relocation is complete.

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

  4. If necessary, restore and revert displaced LIFs or manually migrate and modify the node2 LIFs that failed to relocate automatically to node4.

    Restore and revert displaced LIFs

    1. List any displaced LIFs:

      cluster controller-replacement network displaced-interface show

    2. If any LIFs are displaced, restore the home node back to node4:

      cluster controller-replacement network displaced-interface restore-home-node -node <node4_nodename> -vserver <vserver name> -lif-name <lif_name>
    Manually migrate and modify LIFs

    1. Migrate the LIFs that failed to relocate automatically to node4:

      network interface migrate -vserver <vserver name> -lif <lif_name> -destination-node <node4_nodename> -destination-port <port_on_node4>

    2. Modify the home node and home port for the migrated LIFs:

      network interface modify -vserver <vserver_name> -lif <data_lif_name> -home-node <node4_nodename> -home-port <home_port>

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