Before you set up cluster peering, you should confirm that the IPspace, connectivity, port, IP address, subnet, firewall, and cluster-naming requirements are met.
The subnet used in each cluster for intercluster communication must meet the following requirements:
For example, in a six-node cluster, the subnet used for intercluster communication must have six available IP addresses.
The intercluster network must be configured so that cluster peers have pair-wise full-mesh connectivity, which means that each pair of clusters in a cluster peer relationship has connectivity among all of their intercluster LIFs.
A cluster's intercluster LIFs must use the same IP address version: all IPv4 addresses or all IPv6 addresses. Similarly, all of the intercluster LIFs of the peered clusters must use the same IP addressing version.
The ports that will be used for intercluster communication must meet the following requirements:
The ports added to a broadcast domain can be physical network ports, VLANs, or interface groups (ifgrps).
If you want to dedicate ports to intercluster communication, you can create a broadcast domain specifically for intercluster communication.
Firewalls and the intercluster firewall policy must allow the following:
Although HTTPS is not required when you set up cluster peering, HTTPS is required later if you use OnCommand System Manager to configure data protection. However, if you use the command-line interface to configure data protection, HTTPS is not required to configure cluster peering or data protection.
The default intercluster firewall policy allows access through the HTTPS protocol and from all IP addresses (0.0.0.0/0), but the policy can be altered or replaced.
Clusters must meet the following requirements:
You cannot create a cluster peering relationship with any cluster that has the same name or is in a peer relationship with a cluster of the same name.
Cluster peers can be in different time zones.