Dedicated cluster heartbeat not found
[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 reads the following registry entry to determine the defined role for each network interface resource in the Exchange server cluster:
A value of 1 indicates the network resource has been configured as a dedicated private (heartbeat) network. A value of 2 indicates the network resource has been configured as a dedicated public network (client access). A value of 3 indicates the network resource has been configured as a mixed network that allows both heartbeat traffic and client access traffic.
The Exchange Server Analyzer queries the Win32_Service Microsoft Windows® Management Instrumentation (WMI) class to determine the value of the Started key for the Cluster service (ClusSvc). A value of True indicates the Cluster service is started and a value of False indicates the Cluster service is not running.
If the Exchange Server Analyzer does not find a network resource in an Exchange cluster configured as a dedicated private network, a warning is displayed.
Configuring a dedicated private network to use for the cluster heartbeat is a recommended best practice for all Exchange Server clusters. Communication between nodes is critical for smooth cluster operations. You must configure the networks that you use for cluster communication optimally and follow all hardware compatibility list requirements. For networking configuration, two or more independent networks must connect the nodes of a cluster to avoid a single point of failure. Using two local area networks is typical. Microsoft Product Support Services does not support the configuration of a cluster with nodes connected by only one network.
To correct this warning
If not already present, add network interface cards to each node in the Exchange cluster and configure the network interface cards as a private network in Cluster Administrator.
If additional network cards are present but being used for mixed networks, you should modify the configuration by re-configuring the appropriate networks to act as a dedicated private network.
For more information about cluster heartbeat networks, see the following Microsoft Knowledge Base articles:
258750, "Recommended Private "Heartbeat" Configuration on a Cluster Server" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=258750)
307962, "Multicast Support Enabled for the Cluster Heartbeat" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=307962)
For additional details, review the document, Exchange Server 2003 Cluster Configuration Checklist (http://go.microsoft.com/fwlink/?linkid=36083).