MetroCluster release notes
Choose a controller upgrade procedure
Suggest changes
PDFs
The controller upgrade procedure you use depends on the platform model and type of MetroCluster configuration.
In an upgrade procedure, the controllers are replaced with a new controller model. The storage shelf models are not upgraded.
-
In switchover and switchback procedures, the MetroCluster switchover operation is used to provide nondisruptive service to clients while the controller modules on the partner cluster are upgraded.
-
In an ARL-based controller upgrade procedure, the aggregate relocation operations are used to nondisruptively move data from the old configuration to the new, upgraded configuration.
Supported controller upgrades
Select your Current platform from the FC or IP table below. If the intersection of the Current platform row and Target platform column is blank, the upgrade is not supported.
|
For supported upgrades using system controller replace commands in a four-node MetroCluster IP configuration, refer to the table in Upgrade controllers in a four-node MetroCluster IP configuration using switchover and switchback with "system controller replace" commands (ONTAP 9.13.1 and later)
|
Supported MetroCluster IP controller upgrades
-
If your platform is not listed, there is no supported controller upgrade combination.
-
When you perform a controller upgrade, the old and the new platform type must match:
-
You can upgrade a FAS system to a FAS system, or an AFF A-Series to an AFF A-Series.
-
You cannot upgrade a FAS system to an AFF A-Series, or an AFF A-Series to an AFF C-Series.
For example, if the platform you want to upgrade is a FAS8200, you can upgrade to a FAS9000. You cannot upgrade a FAS8200 system to an AFF A700 system.
-
-
All nodes (old and new) in the MetroCluster configuration must be running the same ONTAP version.
The following table shows the supported platform combinations for upgrading an AFF or FAS system in a MetroCluster IP configuration:
-
Note 1: For this upgrade use the procedure Upgrade controllers from AFF A700/FAS9000 to AFF A900/FAS9500 in a MetroCluster IP configuration using switchover and switchback (ONTAP 9.10.1 or later)
-
Note 2: Controller upgrades are supported on systems running ONTAP 9.13.1 or later.
-
Note 3: The target platform cannot have internal drives until after the controller upgrade is complete. You can add the internal drives after the upgrade.
-
Note 4: Requires replacement of the controller modules.
The following table shows the supported platform combinations for upgrading an ASA system in a MetroCluster IP configuration:
-
Note 1: Controller upgrades are supported on systems running ONTAP 9.13.1 or later.
Supported MetroCluster FC controller upgrades
-
If your platform is not listed, there is no supported controller upgrade combination.
-
When you perform a controller upgrade, the old and the new platform type must match:
-
You can upgrade a FAS system to a FAS system, or an AFF A-Series to an AFF A-Series.
-
You cannot upgrade a FAS system to an AFF A-Series, or an AFF A-Series to an AFF C-Series.
For example, if the platform you want to upgrade is a FAS8200, you can upgrade to a FAS9000. You cannot upgrade a FAS8200 system to an AFF A700 system.
-
-
All nodes (old and new) in the MetroCluster configuration must be running the same ONTAP version.
The following table shows the supported platform combinations for upgrading an AFF or FAS system in a MetroCluster FC configuration:
-
Note 1: For upgrading controllers when FCVI connections on existing FAS8020 or AFF8020 nodes use ports 1c and 1d, see the following Knowledge base article.
-
Note 2: Controller upgrades from AFF A300 or FAS8200 platforms using onboard ports 0e and 0f as FC-VI connections are only supported on the following systems:
-
ONTAP 9.9.1 and earlier
-
ONTAP 9.10.1P9
-
ONTAP 9.11.1P5
-
ONTAP 9.12.1GA
-
ONTAP 9.13.1 and later
For more information, review the Public Report.
-
-
Note 3: For this upgrade refer to Upgrade controllers from AFF A700/FAS9000 to AFF A900/FAS9500 in a MetroCluster FC configuration using switchover and switchback (ONTAP 9.10.1 or later)
-
Note 4: Controller upgrades are supported on systems running ONTAP 9.13.1 or later.
The following table shows the supported platform combinations for upgrading an ASA system in a MetroCluster FC configuration:
| Source MetroCluster FC platform | Destination MetroCluster FC platform | Supported? |
|---|---|---|
ASA A400 |
ASA A400 |
Yes |
ASA A900 |
No |
|
ASA A900 |
ASA A400 |
No |
ASA A900 |
Yes (see Note 1) |
-
Note 1: Controller upgrades are supported on systems running ONTAP 9.14.1 or later.
Choose a procedure that uses the switchover and switchback process
After reviewing the supported upgrade combinations, choose the correct controller upgrade procedure for your configuration.
MetroCluster type |
Upgrade method |
ONTAP version |
Procedure |
|---|---|---|---|
IP |
Upgrade with 'system controller replace' commands |
9.13.1 and later |
|
FC |
Upgrade with 'system controller replace' commands |
9.10.1 and later |
|
FC |
Manual upgrade with CLI commands (AFF A700/FAS9000 to AFF A900/FAS9500 only) |
9.10.1 and later |
|
IP |
Manual upgrade with CLI commands (AFF A700/FAS9000 to AFF A900/FAS9500 only) |
9.10.1 and later |
|
FC |
Manual upgrade with CLI commands |
9.8 and later |
|
IP |
Manual upgrade with CLI commands |
9.8 and later |
Choosing a procedure using aggregate relocation
In an ARL-based controller upgrade procedure, the aggregate relocation operations are used to nondisruptively move data from the old configuration to the new, upgraded configuration.
| MetroCluster type | Aggregate relocation | ONTAP version | Procedure |
|---|---|---|---|
FC |
Using "system controller replace" commands to upgrade controller models in the same chassis |
9.10.1 and later |
|
FC |
Using |
9.8 and later |
|
FC |
Using |
9.5 through 9.7 |
|
FC |
Using manual ARL commands |
9.8 |
|
FC |
Using manual ARL commands |
9.7 and earlier |