Two or more network interfaces are recommended in a cluster
[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: 2006-06-05
Microsoft® Exchange Server 2007 setup displays this warning because the current Microsoft Windows cluster environment has only one network interface that is defined.
It is a recommended best practice to implement at least one network interface for the public network (client connection) and one network interface for the private network (administrative/heartbeat) to avoid a single point of failure.
To address this warning, implement at least one additional network interface for the Microsoft Windows cluster.
For more information about the optimal network configuration for Windows server clusters, see "Server Clusters: Network Configuration Best Practices for Windows 2000 and Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=34304).