MetroCluster release notes
What's new in MetroCluster features
Suggest changes
PDFs
Learn about the new MetroCluster features.
| Supported features in MetroCluster configuration | Description and where to learn more | Available beginning | ||
|---|---|---|---|---|
MetroCluster IP support for end-to-end encryption |
End-to-end encryption is supported on AFF A400, FAS8300, and FAS8700 systems to encrypt back-end traffic, such as NVlog and storage replication data, between the sites in a MetroCluster IP configuration. |
ONTAP 9.15.1 |
||
Volume limit increase for four-node MetroCluster IP configurations on AFF A800 and AFF C800 systems |
In four-node MetroCluster IP configurations, the following volume limits for AFF A800 and AFF C800 systems have increased:
|
ONTAP 9.15.1 |
||
Volume limit increase for four-node MetroCluster IP configurations on AFF A900 systems |
In four-node MetroCluster IP configurations, the following volume limits for AFF A900 systems have increased:
|
ONTAP 9.14.1 |
||
Transition from MetroCluster FC to MetroCluster IP using a shared switch for MetroCluster IP and Ethernet attached storage |
You can transition nondisruptively from a MetroCluster FC to a MetroCluster IP configuration using a shared storage switch. |
ONTAP 9.13.1 |
||
Nondisruptive transitions from an eight-node MetroCluster FC configuration to a MetroCluster IP configuration |
You can nondisruptively transition workloads and data from an existing eight-node MetroCluster FC configuration to a new MetroCluster IP configuration. |
ONTAP 9.13.1 |
||
Four-node MetroCluster IP configuration upgrades using switchover and switchback |
You can upgrade controllers in a four-node MetroCluster IP configuration using switchover and switchback with |
ONTAP 9.13.1 |
||
Mediator-assisted automatic unplanned switchover (MAUSO) is triggered for an environmental shutdown |
If one site shuts down gracefully due to an environmental shutdown, MAUSO is triggered. |
ONTAP 9.13.1 |
||
Eight-node MetroCluster IP configurations support |
You can upgrade the controllers and storage in an eight-node MetroCluster IP configuration by expanding the configuration to become a temporary twelve-node configuration and then removing the old DR groups. |
ONTAP 9.13.1 |
||
MetroCluster IP configuration conversion to a shared storage MetroCluster switch configuration |
You can convert a MetroCluster IP configuration to a shared storage MetroCluster switch configuration. |
ONTAP 9.13.1 |
||
MetroCluster automatic forced switchover feature in a MetroCluster IP configuration |
You can enable the MetroCluster automatic forced switchover feature in a MetroCluster IP configuration. This feature is an extension of the Mediator-assisted unplanned switchover (MAUSO) feature. |
ONTAP 9.12.1 |
||
S3 on an SVM on an unmirrored aggregate in a MetroCluster IP configuration |
You can enable an ONTAP Simple Storage Service (S3) object storage server on an SVM on an unmirrored aggregate in a MetroCluster IP configuration. |
ONTAP 9.12.1 |
||
Transitioning from a MetroCluster FC configuration to an AFF A250 or FAS500f MetroCluster IP configuration |
You can transition from a MetroCluster FC configuration to an AFF A250 or FAS500f MetroCluster IP configuration. |
ONTAP 9.11.1 |
||
Configuration of layer 3 MetroCluster IP address in MetroCluster IP configurations |
You can edit the MetroCluster IP address, netmask, and gateway for nodes in a layer 3 configuration. |
ONTAP 9.10.1 |
||
Simplified controller upgrade of nodes in a MetroCluster FC configuration |
The upgrade procedure for the upgrade process using switchover and switchback has been simplified. |
ONTAP 9.10.1 |
||
IP support for shared link at layer 3 |
MetroCluster IP configurations can be implemented with IP-routed (layer 3) back-end connections. |
ONTAP 9.9.1 |
||
Support for 8-node clusters |
Permanent 8-node clusters are supported in IP and Fabric-attached configurations. |
ONTAP 9.9.1 |
||
Simplified interface to manage IP MetroCluster operations with System Manager |
You can manage IP MetroCluster operations with System Manager, including setting up IP MetroCluster sites, pairing the sites, and configuring the clusters. |
ONTAP 9.8 |
||
IP MetroCluster switchover and switchback with System Manager |
You can use System Manager to perform all the steps of planned or unplanned switchover and switchback procedures for IP MetroCluster configurations. |
ONTAP 9.8 |
||
Transition from MetroCluster FC to MetroCluster IP configurations |
Transition of workloads and data from an existing four-node MetroCluster FC configuration to a new MetroCluster IP configuration is supported. |
ONTAP 9.8 |
||
New upgrade and refresh procedures |
Hardware upgrade or refresh of four-node MetroCluster FC and IP configurations is supported. |
ONTAP 9.8 |
||
Unmirrored aggregates |
Unmirrored aggregates are supported in MetroCluster IP configurations. |
ONTAP 9.8 |
||
MetroCluster compliant switches |
MetroCluster IP configurations can support switches which are not NetApp validated provided that they are compliant with NetApp specifications. |
ONTAP 9.7 |
||
Private layer 2 network sharing |
MetroCluster IP configurations with supported Cisco switches can share existing networks for ISLs, rather than using dedicated MetroCluster ISLs. Earlier ONTAP versions require dedicated ISLs. The MetroCluster IP switches are dedicated to the MetroCluster configuration and cannot be shared. Only the MetroCluster ISL ports on the MetroCluster IP switches can connect to the shared switches.
|
ONTAP 9.6 |
||
MetroCluster switchover and switchback |
You can allow one cluster site to take over the tasks of another cluster site. This capability allows you to facilitate maintenance or recovery from disasters. |
ONTAP 9.6 |
