What's new in MetroCluster features
Suggest changes
PDFs
Each release of the ONTAP 9 data management software delivers new and enhanced features that improve the capabilities, manageability, and performance of ONTAP MetroCluster configurations.
For details about known issues, limitations, and upgrade cautions affecting ONTAP MetroCluster configurations, refer to the ONTAP 9 Release Notes. You must sign in with your NetApp account or create an account to access the Release Notes.
| Supported features in MetroCluster configuration | Description and where to learn more | Available beginning |
|---|---|---|
Fibrebridge firmware update using credentials |
You can update the firmware on Fibrebridge bridges using credentials if they are required by the server to download the firmware package. |
ONTAP 9.16.1 |
SVM data mobility support for migrating MetroCluster configurations |
ONTAP supports the following MetroCluster SVM migrations:
|
ONTAP 9.16.1 |
MD5 authentication support for BGP peer groups |
ONTAP supports MD5 authentication on BGP peer groups to protect BGP sessions. When MD5 is enabled, BGP sessions can only be established and processed among authorized peers, preventing potential disruptions of the session by an unauthorized actor. |
ONTAP 9.16.1 |
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 |
MetroCluster IP support for NVMe |
The NVMe/TCP front-end host protocol is supported on four-node MetroCluster IP configurations. |
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 |
S3 object storage support on mirrored and unmirrored aggregates |
You can enable an S3 object storage server on an SVM in a mirrored or unmirrored aggregate in MetroCluster IP and FC configurations. |
ONTAP 9.14.1 |
Support for provisioning an S3 bucket on mirrored and unmirrored aggregates in a MetroCluster cluster |
You can create a bucket on a mirrored or unmirrored aggregate in MetroCluster configurations. |
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 |
MetroCluster IP support for NVMe |
The NVMe/FC protocol is supported on four-node MetroCluster IP configurations. |
ONTAP 9.12.1 |
IPsec support for front-end host protocol in MetroCluster IP and MetroCluster fabric-attached configurations |
IPsec support for front-end host protocol (such as NFS and iSCSI) is available in MetroCluster IP and MetroCluster fabric-attached configurations. |
ONTAP 9.12.1 |
Transition 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 |
Consistency groups |
Consistency groups are supported in MetroCluster configurations. |
ONTAP 9.11.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 eight-node MetroCluster configurations |
Permanent eight-node clusters are supported in IP and Fabric-attached MetroCluster configurations. |
ONTAP 9.9.1 |