Skip to main content
ONTAP MetroCluster

Complete the MetroCluster IP controller upgrade

Contributors netapp-aoife netapp-sarajane
PDFs

Complete the automated controller upgrade process by verifying the network reachability and restoring any monitoring configuration.

Verify network reachability

The automation operation runs verification system checks and then pauses so you can verify the network reachability. After verification, the resource regain phase is initiated and the automation operation executes switchback at site A and pauses at the post upgrade checks. After you resume the automation operation, it performs the post upgrade checks and if no errors are detected, marks the upgrade as complete.

Steps

  1. Verify the network reachability by following the console message.

  2. After you complete the verification, resume the operation:

    system controller replace resume

  3. The automation operation performs heal-aggregate, heal-root-aggregate, and switchback operations at site A, and the post upgrade checks. When the operation pauses, manually check the SAN LIF status and verify the network configuration by following the console message.

  4. After you complete the verification, resume the operation:

    system controller replace resume

  5. Check the post upgrade checks status:

    system controller replace show

    If the post upgrade checks didn't report any errors, the upgrade is complete.

  6. After you complete the controller upgrade, log in at site B and verify that the replaced controllers are configured correctly.

Upgrade the nodes on cluster_A

You must repeat the upgrade tasks to upgrade the nodes on cluster_A at site A.

Steps

  1. Repeat the steps to upgrade the nodes on cluster_A, beginning with Prepare for the upgrade.

    When you repeat the procedure, all example references to the clusters and nodes are reversed.

Re-add internal drives to the new controller

If you upgraded from a system that only has external drives to a system that has external and internal drives (disks and controllers in the same chassis), you can add or re-seat the disks that you removed or unseated from the internal slots of the new system. You can do this at any time after the upgrade is completed on both sites and the cluster is in a healthy state.

After you re-add or re-seat the drives, they can be used in ONTAP as required.

Note This task only applies to certain upgrade combinations. Refer to remove internal drives from the chassis on the new controller for more information.

Reconfigure ONTAP Mediator

Manually configure ONTAP Mediator which was automatically removed before you started the upgrade.

  1. Use the steps in Configure ONTAP Mediator from a MetroCluster IP configuration.

Restore Tiebreaker monitoring

If the MetroCluster configuration was previously configured for monitoring by the Tiebreaker software, you can restore the Tiebreaker connection.

  1. Use the steps in Add MetroCluster configurations.

Configure end-to-end encryption

If it is supported on your system, you can encrypt back-end traffic, such as NVlog and storage replication data, between the MetroCluster IP sites. Refer to Configure end-to-end encryption for more information.