You can use this procedure only for controller upgrade.

The MetroCluster IP switches (switch type, vendor, and model) and the firmware version must be supported on the existing and new controllers in your upgrade configuration.

The MetroCluster IP systems must be running the same ONTAP version at both sites.

When you upgrade from systems that have more slots or ports than the new system, you need to verify that there are sufficient slots and ports on the new system.

You can use this procedure to upgrade controllers in a four-node MetroCluster IP configuration using NSO based automated switchover and switchback.

Performing an upgrade using aggregate relocation (ARL) with “systems controller replace” commands is not supported for a four-node MetroCluster IP configuration.

If it is enabled on your system, disable end-to-end encryption before performing the upgrade.

You must use the automated NSO controller upgrade procedure to upgrade the controllers at both sites in sequence.

This automated NSO based controller upgrade procedure gives you the capability to initiate controller replacement to a MetroCluster disaster recovery (DR) site. You can only initiate a controller replacement at one site at a time.

To initiate a controller replacement at site A, you need to run the controller replacement start command from site B. The operation guides you to replace controllers of both the nodes at site A only. To replace the controllers at site B, you need to run the controller replacement start command from site A. A message displays identifying the site at which the controllers are being replaced.

cluster_A at site_A

cluster_B at site_B