Skip to main content
ONTAP MetroCluster

Prepare the network configuration of the old MetroCluster IP controllers

Contributors netapp-aoife
PDFs

After you gather information and resume the operation, the automation operation proceeds with the switchover.

Before you begin

Before initiating switchover, the automation operation pauses so you can manually verify that all LIFs are “up” at site B. If necessary, bring any LIFs that are “down” to “up” and resume the automation operation by using the system controller replace resume command.

The automation operation initiates the switchover operations. After these operations complete, the operation pauses at paused for user intervention so you can rack and install the controllers, boot the partner controllers, and reassign the root aggregate disks to the new controller module from flash backup using the sysids gathered earlier.

About this task
Steps

  1. Boot the old nodes and then log in to the nodes:

    boot_ontap

  2. If the system you are upgrading to uses shared cluster/HA ports, verify that the MetroCluster IP interfaces are using supported IP addresses.

    Use the following information to determine whether the new system uses shared cluster/HA ports:

    Shared cluster/HA ports

    The systems listed in the following table use shared cluster/HA ports:

    AFF and ASA systems FAS systems

    • AFF A20

    • AFF A30

    • AFF C30

    • AFF A50

    • AFF C60

    • AFF C80

    • AFF A70

    • AFF A90

    • AFF A1K

    • FAS70

    • FAS90

    1. Verify the IP addresses of the MetroCluster interfaces on the old controllers:

      metrocluster configuration-settings interface show

    2. If the MetroCluster interfaces are using 169.254.17.x or 169.254.18.x IP addresses, refer to the Knowledge Base article "How to modify the properties of a MetroCluster IP interface" to modify the interface IP addresses before you proceed with the upgrade.

      Caution Upgrading to any system that uses shared cluster/HA ports isn't supported if the MetroCluster interfaces are configured with 169.254.17.x or 169.254.18.x IP addresses.

  3. Modify the intercluster LIFs on the old controllers to use a different home port than the ports used for HA interconnect or MetroCluster IP DR interconnect on the new controllers.

    Note This step is required for a successful upgrade.

    The intercluster LIFs on the old controllers must use a different home port than the ports used for HA interconnect or MetroCluster IP DR interconnect on the new controllers. For example, when you upgrade to AFF A90 controllers, the HA interconnect ports are e1a and e7a, and the MetroCluster IP DR interconnect ports are e2b and e3b. You must move the intercluster LIFs on the old controllers if they are hosted on ports e1a, e7a, e2b, or e3b.

    For port distribution and allocation on the new nodes, refer to the Hardware Universe.

    1. On the old controllers, view the intercluster LIFs:

      network interface show -role intercluster

      Take one of the following actions depending on whether the intercluster LIFs on the old controllers use the same ports as the ports used for HA interconnect or MetroCluster IP DR interconnect on the new controllers.

      If the intercluster LIFs…​ Go to…​

      Use the same home port

      Substep b

      Use a different home port

      Step 4

    2. Modify the intercluster LIFs to use a different home port:

      network interface modify -vserver <vserver> -lif <intercluster_lif> -home-port <port-not-used-for-ha-interconnect-or-mcc-ip-dr-interconnect-on-new-nodes>

    3. Verify that all intercluster LIFs are on their new home ports:

      network interface show -role intercluster -is-home false

      The command output should be empty, indicating that all intercluster LIFs are on their respective home ports.

    4. Revert any LIFs that are not on their home ports:

      network interface revert -lif <intercluster_lif>

      Repeat the command for each intercluster LIF that is not on the home port.

  4. Assign the home port of all data LIFs on the old controller to a common port that is the same on both the old and new controller modules.

    Caution If the old and new controllers don't have a common port, you don't need to modify the data LIFs. Skip this step and go directly to Step 5.

    1. Display the LIFs:

      network interface show

      All data LIFs including SAN and NAS will be admin “up” and operationally “down” since those are up at switchover site (cluster_A).

    2. Review the output to find a common physical network port that is the same on both the old and new controllers that is not used as a cluster port.

      For example, “e0d” is a physical port on old controllers and is also present on new controllers. “e0d” is not used as a cluster port or otherwise on the new controllers.

      Refer to the Hardware Universe for the port usage of each platform model.

    3. Modify all data LIFS to use the common port as the home port:

      network interface modify -vserver <svm-name> -lif <data-lif> -home-port <port-id>

      In the following example, this is “e0d”.

      For example:

      network interface modify -vserver vs0 -lif datalif1 -home-port e0d

  5. Modify broadcast domains to remove the VLAN and physical ports that need to be deleted:

    broadcast-domain remove-ports -broadcast-domain <broadcast-domain-name>-ports <node-name:port-id>

    Repeat this step for all VLAN and physical ports.

  6. Remove any VLAN ports using cluster ports as member ports and interface groups using cluster ports as member ports.

    1. Delete VLAN ports:

      network port vlan delete -node <node-name> -vlan-name <portid-vlandid>

      For example:

      network port vlan delete -node node1 -vlan-name e1c-80

    2. Remove physical ports from the interface groups:

      network port ifgrp remove-port -node <node-name> -ifgrp <interface-group-name> -port <portid>

      For example:

      network port ifgrp remove-port -node node1 -ifgrp a1a -port e0d

    3. Remove VLAN and interface group ports from the broadcast domain:

      network port broadcast-domain remove-ports -ipspace <ipspace> -broadcast-domain <broadcast-domain-name>-ports <nodename:portname,nodename:portname>,..

    4. Modify interface group ports to use other physical ports as member as needed:

      ifgrp add-port -node <node-name> -ifgrp <interface-group-name> -port <port-id>

  7. Halt the nodes:

    halt -inhibit-takeover true -node <node-name>

    This step must be performed on both nodes.

  8. Verify that the nodes are at the LOADER prompt and collect and preserve the current environment variables.

  9. Gather the bootarg values:

    printenv

  10. Power off the nodes and shelves at the site where the controller is being upgraded.

What's next?

Set up and netboot the new controllers.