Choose your transition procedure
Suggest changes
PDFs
When transitioning to a MetroCluster IP configuration, you must have a combination of supported platform models.
You should also ensure that the MetroCluster IP platform is an appropriate size for the load that you are transitioning from the MetroCluster FC configuration to the MetroCluster IP configuration.
Supported platform combinations
-
The transition procedures all require ONTAP 9.8 or later unless stated otherwise in the notes or as required by an individual platform.
-
All nodes in the MetroCluster configuration must be running the same ONTAP version. For example, if you have an eight-node configuration, all eight nodes must be running the same ONTAP version. Refer to the Hardware universe for the minimum supported ONTAP version for your combination.
|
|
Supported AFF and FAS transition combinations
The following tables show the supported platform combinations. You can transition from platforms in the first column to platforms listed as supported in the columns to the right, as indicated by the colored table cells.
For example, transitioning from a MetroCluster FC configuration consisting of AFF8060 controller modules to an IP configuration consisting of AFF A400 controller modules is supported.
The tables are split into two groups:
-
Group 1 shows combinations for transitions to AFF A150, AFF A20, FAS2750, AFF A220, FAS500f, AFF C250, AFF A250, FAS50, AFF C30, AFF A30, FAS8200, AFF A300, AFF A320, FAS8300, AFF C400, AFF A400, and FAS8700 systems.
-
Group 2 shows combinations for transitions to AFF C60, AFF A50, FAS70, FAS9000, AFF A700, AFF A70, AFF C800, AFF A800, FAS9500, AFF A900, AFF C80, FAS90, AFF A90, and AFF A1K systems.
The following notes apply to both groups:
-
Note 1: This platform combination requires ONTAP 9.11.1 or later.
-
Note 2: You must have a 40GbE interface for the local cluster interfaces on the FC nodes.
-
Note 3: You must have a 100GbE interface for the local cluster interfaces on the FC nodes.
Review the supported combinations for transitions to AFF A150, AFF A20, FAS2750, AFF A220, FAS500f, AFF C250, AFF A250, FAS50, AFF C30, AFF A30, FAS8200, AFF A300, AFF A320, FAS8300, AFF C400, AFF A400, and FAS8700 systems.
Review the supported combinations for transitions to AFF C60, AFF A50, FAS70, FAS9000, AFF A700, AFF A70, AFF C800, AFF A800, FAS9500, AFF A900, AFF C80, FAS90, AFF A90, and AFF A1K systems.
Supported ASA transition platform combinations
The following table shows the supported platform combinations for ASA systems.
| Source MetroCluster FC platform | Target MetroCluster IP platform | Supported? |
|---|---|---|
ASA A400 |
ASA A400 |
Yes |
ASA A900 |
No |
|
ASA A900 |
ASA A400 |
No |
ASA A900 |
Yes |
Choose your transition procedure
You must select a transition procedure depending on your existing MetroCluster FC configuration.
A transition procedure replaces the back-end FC switch fabric or FC-VI connection with an IP switch network. The exact procedure depends on your starting configuration.
The original platforms and FC switches (if present) are retired at the end of the transition procedure.
Starting configuration |
Disruptive or nondisruptive |
Requirements |
Procedure |
|---|---|---|---|
Four or eight node |
Nondisruptive |
New storage shelves are supported on new platforms. |
|
Two node |
Disruptive |
New storage shelves are supported on both original and new platforms. |
|
Two node |
Disruptive |
New storage shelves are supported on both original and new platforms. Old storage shelves must be retired. |
|
Two node |
Disruptive |
Old storage shelves are not supported on new platforms. Old storage shelves must be retired. |