Hi Experts,
Have the following two questions, hopefully should be straightforward. Here goes,
1. Any problem with using a common private layer 2 VLAN / network for each of the heartbeat and live migration networks for multiple separate clusters (as shown below)? AFAIK each individual cluster should have its own separate vlan / network id for heartbeat traffic though I'm not aware what exactly could go wrong.
Cluster 1
Node1 - VLAN100 - 10.192.168.1.x - Heartbeat network
- VLAN101 - 10.192.168.2.x - LM network
Node2 - VLAN100 - 10.192.168.1.x - Heartbeat network
- VLAN101 - 10.192.168.2.x - LM network
Cluster 2
Node1 - VLAN100 - 10.192.168.1.x - Heartbeat network
- VLAN101 - 10.192.168.2.x - LM network
Node2 - VLAN100 - 10.192.168.1.x - Heartbeat network
- VLAN101 - 10.192.168.2.x - LM network
2. when the DCs and DNS servers are separated from the cluster nodes by a firewall which ports and services would the cluster IP / name need access to? I know the cluster name and ip needs to be registered in DNS and cluster object (will be pre-created in this case) created in AD, etc so assuming whatever ports we need to allow for the node names and IPs has to be allowed for the cluster name and IP as well.
Thank you for your help in advance :)