Heartbeat connection has default gateway
[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 queries the Win32_NetworkAdapterConfiguration WMI class to determine whether a value is set for the DefaultIPGateway key. If a value is set, it indicates that a default gateway has been configured for this network interface.
If the Exchange Server Analyzer finds a value set for the DefaultIPGateway key on the network interface used for the cluster heartbeat network, a warning is displayed.
Because private cluster networks are used for internal cluster communications, it is not necessary to configure a default gateway. To eliminate possible communication issues, it is recommended that you remove all unnecessary network traffic from the network adapter that is used as the cluster private network adapter.
To correct this warning
Open the Network Connections window. Either right-click My Network Places, and then click Properties, or if My Network Places is not displayed on the desktop, click Start, click Programs, click Accessories, click Communications, and then click Network Connections.
In the Network Connections window, right-click the network adapter being used for the private network, and then click Properties.
Select Internet Protocol (TCP/IP), and then click Properties.
In the Use the following IP address area, delete the default gateway IP address.
Click OK twice to save the changes.
Repeat steps 1-5 for each node in the cluster.
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).