Requirements for using this MetroCluster IP upgrade procedure

01/09/2025 Contributors

Verify that your system meets all the requirements before performing the controller upgrade.

Platforms supported by this procedure

The platforms must be running ONTAP 9.8 or later.
The target (new) platform must be a different model than the original platform.
You can only upgrade specific platform models using this procedure in a MetroCluster IP configuration.
- For information on what platform upgrade combinations are supported, review the MetroCluster IP upgrade table in Choose a controller upgrade procedure.
  
  Refer to Choosing an upgrade or refresh method for additional procedures.

This procedure applies to controller modules in a MetroCluster IP configuration.
All controllers in the configuration should be upgraded during the same maintenance period.

Operating the MetroCluster configuration with different controller types is not supported outside of this maintenance activity.
The MetroCluster IP systems must be running the same ONTAP version at both sites.
The MetroCluster IP switches (switch type, vendor, and model) and firmware version must be supported on the existing and new controllers in your upgrade configuration.

Refer to the Hardware Universe or the IMT for supported switches and firmware versions.
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.

Before you start the upgrade, refer to the Hardware Universe to verify the number of slots and ports on the new system.
If it's enabled on your system, disable end-to-end encryption before performing the upgrade.
If the new platform has fewer slots than the original system, or if it has fewer or different types of ports, you might need to add an adapter to the new system.
You reuse the IP addresses, netmasks, and gateways of the original platforms on the new platforms.

The following example names are used in this procedure:

What's next?