MetroCluster release notes
The requested article is not available. Either it doesn't apply to this version of the product or the relevant information is organized differently in this version of the docs. You can search, browse, or go back to the other version.
Illustration of the cluster peering network
Contributors
Suggest changes
-
PDF of this doc site
-
Install a fabric-attached MetroCluster
-
Cable a fabric-attached MetroCluster configuration
-
Plan and install a MetroCluster configuration with array LUNs
-
-
Install a MetroCluster IP configuration
-
Install a stretch MetroCluster configuration
-
Maintain the MetroCluster components
-
Transition from MetroCluster FC to MetroCluster IP
-
Upgrade, refresh, or expand the MetroCluster configuration
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
The two clusters in the MetroCluster configuration are peered through a customer-provided cluster peering network. Cluster peering supports the synchronous mirroring of storage virtual machines (SVMs, formerly known as Vservers) between the sites.
Intercluster LIFs must be configured on each node in the MetroCluster configuration, and the clusters must be configured for peering. The ports with the intercluster LIFs are connected to the customer-provided cluster peering network. Replication of the SVM configuration is carried out over this network through the Configuration Replication Service.
Related information
Illustration of the local HA pairs in a MetroCluster configuration
