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.

Boot the new controllers

You must boot the new controllers, taking care to ensure that the bootarg variables are correct and, if needed, perform the encryption recovery steps.

Steps

  1. Halt the new nodes:

    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-addres>

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

  3. Check if the partner-sysid is the current:

    printenv partner-sysid

    If the partner-sysid is not correct, set it:

    setenv partner-sysid <partner-sysID>

  4. Display the ONTAP boot menu:

    boot_ontap menu

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

  6. From the boot menu, select “(6) Update flash from backup config”.

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

  7. At the LOADER prompt, verify the bootarg values and update the values as needed.

    Use the steps in Set the MetroCluster IP bootarg variables.

  8. Verify that the partner-sysid is the correct:

    printenv partner-sysid

    If the partner-sysid is not correct, set it:

    setenv partner-sysid <partner-sysID>

  9. 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).

  10. Wait for the replaced nodes to boot.

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

  11. 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> -node <node> -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.

  12. 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. Don't delete any of the broadcast domains that existed before starting the upgrade.

      broadcast-domain delete -broadcast-domain <broadcast_domain_name>

    3. Add ports to a broadcast domain as needed.

      Add or remove ports from a broadcast domain

    4. Recreate VLANs and interface groups as needed.

      VLAN and interface group membership might differ from the old node.

      Create a VLAN

      Combinine physical ports to create interface groups

Verify and restore LIF configuration

Verify that LIFs are hosted on appropriate nodes and ports as mapped out at the beginning of the upgrade procedure.

About this task
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.

What's next?

Switchback the MetroCluster configuration.