One topic I see often during my day to day work is that customers forgott to use a cluster network and install it on other networks like livemigration or management.
With my blogpost today I want to explain why you should use a separated cluster network and what you should configure to get it running.
At first, how does a cluster heartbeat work. You can see it like your own heartbeat. Every cluster node sends every second a heartbeat and ask the other nodes after their status. If 5 heartbeats fail within 10 seconds, the cluster will remove the host and migrate workloads.
So what happens if you set cluster heartbeat to for example livemigration. When a livemigration starts, the cluster heartbeat will fail and you livemigration and cluster node will fail.
Ok .. now some MVPs and IT Pro’s say, you can use other networks as fall back heartbeat networks. Yes you can have fallbacks BUT the cluster will try 3 times to bring the heartbeat through and than change to the oher network. Normally the heartbeat will fail there too.
In your own interest, you should use an own cluster network.
Now lets go to the options that you have to create a cluster network.
1. You can use a physical NIC Team for you Cluster Network
2. You can share a NIC Team via additional VLAN Tag on the Team for example with management
3. For Hyper-V you can create an additional virtual NIC for cluster traffic
After you created your cluster network, you need to do some more steps to guarantee bandwidth for the cluster heartbeat.
1. enable QoS (Quality of Service) on your network for the cluster network
2. configure network connection binding and cluster communication priority like discibed in my last blogpost How to configure cluster traffic priority on a windows server
3. on a Hyper-V Host or with Virtual Machine Manager you need to set a minimum bandwidth for the cluster network interface. I normally use a minimum of 5 to 10%
PowerShell for Hyper-V Host
Set-VMNetworkAdapter -ManagementOS -Name "Cluster NIC Name" -MinimumBandwidthWeight 5
In VMM you use the Hyper-V Port Profil “Cluster Workload”
So that should do the trick. 🙂