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.
Cabling the cluster peering connections
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
You must cable the controller module ports used for cluster peering so that they have connectivity with the cluster on their partner site.
This task must be performed on each controller module in the MetroCluster configuration.
At least two ports on each controller module should be used for cluster peering.
The recommended minimum bandwidth for the ports and network connectivity is 1 GbE.
Steps
-
Identify and cable at least two ports for cluster peering and verify they have network connectivity with the partner cluster.
Cluster peering can be done on dedicated ports or on data ports. Using dedicated ports provides a higher throughput for the cluster peering traffic.
