Heartbeat network speed set to auto sense/auto detect
[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]
Topic Last Modified: 2005-11-18
The Microsoft® Exchange Server Analyzer Tool queries the Win32_NetworkAdapter Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the NetConnectionID key. If the value for the NetConnectionID key contains the string Internal, or HEART, it indicates that the interface is the cluster private (heartbeat) network.
The Exchange Server Analyzer also reads the following registry value to determine the link speed and duplex settings for the network interface card being used for the cluster heartbeat network:
Additionally, the Exchange Server Analyzer also reads the following registry value to determine whether automatic network speed detection is enabled:
If the value for the 0 key contains the string AUTO, it indicates that automatic network speed detection is enabled.
If the Exchange Server Analyzer determines that both SpeedDuplex is set to 0 and automatic network speed detection is enabled for the cluster heartbeat network, a warning is displayed.
Communication between server cluster nodes is critical for smooth cluster operations. If you use a multiple speed Ethernet network adapter for cluster communications and configure the adapter to automatically detect the network speed, the adapter may cause problems within the cluster. During the detection process, packets cannot be handled by the adapter and must be queued. Some adapters may unintentionally trigger the automatic detection process to reoccur occasionally. Therefore, communications are queued and communication delayed. Delays of this kind may cause cluster nodes not to receive critical packets promptly and may cause premature failover of cluster resources. It is recommended that the heartbeat network in a cluster be manually set to 10 megabits and half-duplex. This configuration will provide sufficient bandwidth and reliable communication.
To correct this warning
- Configure the heartbeat network interface card for a link speed of 10 megabits and a duplex setting of half-duplex. Because the configuration steps for each network card are different, follow the instructions from your hardware provider to correctly configure the heartbeat network. Configuring these options may require an updated driver.
For more information about the recommended settings for the private network in a Windows server cluster, see the Microsoft Knowledge Base article 258750, "Recommended Private 'Heartbeat' Configuration on a Cluster Server" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=258750).