How to Configure Cluster Networks for a Failover Cluster
Microsoft Exchange Server 2007 will reach end of support on April 11, 2017. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
Applies to: Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3
This topic explains how to use the Failover Cluster Management tool and Cluster.exe to configure the cluster networks for the failover cluster. After both nodes have been added to the cluster, the cluster networking components must be configured. Specifically, you must configure networks for cluster and client access, and you must configure tolerance settings for missed cluster heartbeats. While configuring the cluster and client access settings, we also recommend renaming the networks with more meaningful names.
Before You Begin
To perform this procedure, the account you use must be delegated membership in the local Administrators group. For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
To use the Failover Cluster Management tool to configure networks for cluster and client access
Open the Failover Cluster Management tool.
Expand the cluster node, and then select Networks.
Modify the properties for each network by configuring the name of the network, as well as cluster and client access settings. For details about the available settings, see Installing Cluster Continuous Replication on Windows Server 2008, as well as the Failover Cluster Management tool Help.
Only cluster networks that are configured for both cluster and client use (referred to as mixed networks) can be enabled for log shipping. Cluster networks designated as private can be used for seeding and reseeding.
Optionally, rename each network with a more meaningful name (for example, Public, Private, LogShip1, LogShip2).
To use Cluster.exe to configure tolerance for missed cluster heartbeats
Verify that both nodes in the cluster are online. To do this, run the following command:
cluster ClusterName Node
Examine the output of the command in Step 1, and verify that the Status for each node is Up.
Configure the number of missed heartbeats for all private and mixed interfaces on all nodes. To do this, run the following command based on your environment.
Single subnet failover clusters:
cluster ClusterName /prop SameSubnetThreshold=10
Multi-subnet failover clusters:
cluster ClusterName /prop CrossSubnetThreshold=10
After the cluster networks have been configured, the next step is to configure the cluster quorum. For detailed steps about how to configure the cluster quorum, see How to Configure the Node and File Share Majority Quorum.
For More Information
For more information about cluster continuous replication (CCR), see Cluster Continuous Replication and Installing Cluster Continuous Replication on Windows Server 2008.