Skip to main content
ONTAP MetroCluster

Boot the new MetroCluster IP controllers and restore LIF configuration

Contributors netapp-aoife
PDFs

Boot the new controllers and verify that LIFs are hosted on appropriate nodes and ports before resuming the operation by using the system controller replace resume command.

Boot the new controllers

Boot the new controllers,verify that the bootarg variables are correct and if needed, perform the encryption recovery steps.

About this task

This task must be performed on all the new controllers.

Steps

  1. Halt the node:

    halt

  2. If external key manager is configured, set the related bootargs:

    setenv bootarg.kmip.init.ipaddr <ip-address>

    setenv bootarg.kmip.init.netmask <netmask>

    setenv bootarg.kmip.init.gateway <gateway-address>

    setenv bootarg.kmip.init.interface <interface-id>

  3. Display the boot menu:

    boot_ontap menu

  4. If root encryption is used, select the boot menu option for your key management configuration.

    If you are using…​

    Select this boot menu option…​

    Onboard key management

    Option “10”

    Follow the prompts to provide the required inputs to recover and restore the key-manager configuration.

    External key management

    Option “11”

    Follow the prompts to provide the required inputs to recover and restore the key-manager configuration.

  5. From the boot menu, run option “6”.

    Note Option “6” reboots the node twice before the process completes.

    Respond with “y” to the system ID change prompts. Wait for the second reboot messages:

    Successfully restored env file from boot media...

Rebooting to load the restored env file...

    During one of the reboots after option “6”, the confirmation prompt Override system ID? {y|n} appears. Enter y.

  6. If root encryption is used, select the boot menu option again for your key management configuration.

    If you are using…​

    Select this boot menu option…​

    Onboard key management

    Option “10”

    Follow the prompts to provide the required inputs to recover and restore the key-manager configuration.

    External key management

    Option “11”

    Follow the prompts to provide the required inputs to recover and restore the key-manager configuration.

    Depending on the key manager setting, perform the recovery procedure by selecting option “10” or option “11”, followed by option “6” at the first boot menu prompt. To boot the nodes completely, you might need to repeat the recovery procedure continued by option “1” (normal boot).

  7. Boot the nodes:

    boot_ontap

  8. Wait for the replaced nodes to boot up.

    If either node is in takeover mode, perform a giveback using the storage failover giveback command.

  9. Verify that all ports are in a broadcast domain:

    1. View the broadcast domains:

      network port broadcast-domain show

    2. If a new broadcast domain is created for the data ports on the newly upgraded controllers, delete the broadcast domain:

      Note Only delete the new broadcast domain. Do not delete any of the broadcast domains that existed before starting the upgrade.

      broadcast-domain delete -broadcast-domain <broadcast_domain_name>

    3. Add any ports to a broadcast domain as needed.

      Add or remove ports from a broadcast domain

    4. Add the physical port that will host the intercluster LIFs to the corresponding broadcast domain.

    5. Modify intercluster LIFs to use the new physical port as home port.

    6. After the intercluster LIFs are up, check the cluster peer status and re-establish cluster peering as needed.

      You might need to reconfigure cluster peering.

      Create a cluster peer relationship

    7. Recreate VLANs and interface groups as needed.

      VLAN and interface group membership might be different than that of the old node.

      Create a VLAN

      Combine physical ports to create interface groups

    8. Verify that the partner cluster is reachable and that the configuration is successfully resynchronized on the partner cluster:

      metrocluster switchback -simulate true

  10. If encryption is used, restore the keys using the correct command for your key management configuration.

    If you are using…​

    Use this command…​

    Onboard key management

    security key-manager onboard sync

    For more information, see Restore onboard key management encryption keys.

    External key management

    security key-manager external restore -vserver <svm-name> -node <node-name> -key-server <host_name|IP_address:port> -key-id <key_id> -key-tag key_tag <node-name>

    For more information, see Restore external key management encryption keys.

  11. Verify that the MetroCluster is configured correctly. Check the node status:

    metrocluster node show

    Verify that the new nodes (site_B) are in Waiting for switchback state from site_A.

Verify and restore LIF configuration

Verify that LIFs are hosted on appropriate nodes before you proceed with the automated switchback operation.

About this task

  • This task is performed on site_B.

Caution You must verify that the location of the data LIFs is correct on the new nodes before you perform a switchback. When you switchback the configuration, ONTAP attempts to resume traffic on the home port used by the LIFs. I/O failure can occur when the home port connection to the switch port and VLAN is incorrect.
Steps

  1. Verify that LIFs are hosted on the appropriate node and ports before switchback.

    1. Change to the advanced privilege level:

      set -privilege advanced

    2. Display the LIFs, and confirm that each data LIF is using the correct home port:

      network interface show

    3. Modify any LIFs that aren't using the correct home port:

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

      If the command returns an error, you can override the port configuration:

      vserver config override -command "network interface modify -vserver <svm-name> -home-port <active_port_after_upgrade> -lif <lif_name> -home-node <new_node_name>"

      When entering the network interface modify command within the vserver config override command, you cannot use the tab autocomplete feature. You can create the network interface modify using autocomplete and then enclose it in the vserver config override command.

    4. Confirm that all data LIFs are now on the correct home port:

      network interface show

    5. Return to the admin privilege level:

      set -privilege admin

  2. Revert the interfaces to their home node:

    network interface revert * -vserver <svm-name>

    Perform this step on all SVMs as required.

  3. Resume the operation:

    system controller replace resume

What's next?

Complete the controller upgrade.