Cabling the cluster peering connections
PDF of this doc site
Install a fabric-attached MetroCluster
Cable a fabric-attached MetroCluster configuration
Install and cable MetroCluster components
- Install and cable MetroCluster components
- Configure hardware for sharing a Brocade 6510 FC fabric during transition
Plan and install a MetroCluster configuration with array LUNs
Install and cable the MetroCluster components in a configuration with array LUNs
- Install and cable the MetroCluster components in a configuration with array LUNs
- Cable a fabric-attached MetroCluster configuration
Install a MetroCluster IP configuration
- Configure the MetroCluster hardware components
Install a stretch MetroCluster configuration
- Cable a two-node SAS-attached stretch MetroCluster configuration
- Cable a two-node bridge-attached stretch MetroCluster configuration
- Install and Configure MetroCluster Tiebreaker
- Perform switchover, healing, and switchback
Maintain the MetroCluster components
- Hot add storage to a MetroCluster FC configuration
Transition from MetroCluster FC to MetroCluster IP
- Transition nondisruptively from a MetroCluster FC to a MetroCluster IP configuration (ONTAP 9.8 and later)
Upgrade, refresh, or expand the MetroCluster configuration
- Expand a two-node MetroCluster FC configuration to a four-node configuration
- Install a fabric-attached MetroCluster
You must cable the controller module ports used for cluster peering so that they have connectivity with the cluster on the 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.
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 higher throughput for the cluster peering traffic.
Each MetroCluster site is configured as a peer to its partner site. You should be familiar with the prerequisites and guidelines for configuring the peering relationships and when deciding whether to use shared or dedicated ports for those relationships.