Recommended private "Heartbeat" configuration on a cluster server

The information that is traveling across the heartbeat network is small, but latency is critical for communication. If you have the same the speed and duplex settings, this helps to make sure that you have reliable communication. 

If you are not sure of the supported speed of your card and connecting devices, or your manufacturer's recommended settings, Microsoft recommends that you set all the devices on that path of 10 MB/Sec and Half Duplex. This configuration will provide sufficient bandwidth and reliable communication. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
174812 The effects of using Autodetect setting on cluster network interface card
Note: Microsoft does not recommend the use of any type of fault-tolerant adapter or "Teaming" for the heartbeat. If you require redundancy for your heartbeat connection, use multiple network adapters set to Internal Communication Only and define their network priority in the Cluster configuration. Issues seen with early multi-ported network adapters, verify that your firmware and driver are at the most current revision if you use this technology.
Reference:
http://support.microsoft.com/KB/258750
http://blogs.technet.com/b/askcore/archive/2008/02/06/troubleshooting-cluster-logs-101-why-did-the-resources-failover-to-the-other-node.aspx

Comments

Popular posts from this blog

vRA/vRO workflows

How to generate HPS Report for Windows