How to Configure Cluster Networking Components and Priority

Artikel
01/23/2017

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, Exchange Server 2007 SP1, Exchange Server 2007 SP2, Exchange Server 2007 SP3

This topic explains how to use Cluster Administrator or Cluster.exe to configure the cluster networking components and priority for a clustered mailbox server (CMS) in a single copy cluster (SCC) on Windows Server 2003.

There are two procedures that you need to perform:

Enable networks for cluster use This procedure allows the cluster to make use of the networks to which it is attached.
Configure network priority order This procedure ensures that client connections to the cluster occur in a timely manner.

If you are using Internet SCSI (iSCSI) storage in an SCC, the iSCSI networks may be detected by the Cluster service during cluster formation and listed as available networks in the cluster. The Cluster service should not manage iSCSI networks, and any detected iSCSI networks should be disabled for cluster use.

Before You Begin

These procedures assume that only two networks, a public network and a private network, are in use. If your cluster has two networks, we recommend that you configure these networks as one public network and one private network, which is a common configuration.We also recommend that you have two or more networks connected to your cluster server. For additional information about public and private networks, see How to Configure Network Connections for a Single Copy Cluster.

Configuring cluster network priority is different from configuring the network binding order in Microsoft Windows. For detailed steps that explain how to configure the network binding order in Windows, see How to Configure Network Connections for a Single Copy Cluster.

To perform the following procedures on a computer that is being configured for a CMS, the account you use must be delegated membership in the local Administrator group. For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.

Procedure

To use Cluster Administrator to enable networks for cluster use

Open Cluster Administrator.
In the console tree, expand Cluster Configuration, and then expand Networks.
Right-click the private network that you want to enable, and select Properties.
Verify that the Enable this network for cluster use check box is selected.
In the This network performs the following role in the cluster field, select Internal cluster communications only (private network), and then click OK.
Right-click the public network that you want to enable, and then click Properties.
Verify that the Enable this network for cluster use check box is selected.
In the This network performs the following role in the cluster field, select All communications (mixed network), and then click OK.

Note

If you have any networks, including iSCSI networks, that you do not want to be managed or used by the cluster, clear the Enable this network for cluster use check box for the network.

To use Cluster Administrator to configure cluster network priority

Open Cluster Administrator.
In the console tree, right-click the cluster name, and then select Properties.
Click the Network Priority tab.
In Networks used for internal cluster communications, select the private network. Increase its priority by clicking Move Up until the private network is listed at the top of the priority list. Repeat this step for each additional private network until all private networks have a higher priority than all mixed or client-only networks.
When you have finished, click OK.

To use Cluster.exe to enable networks for cluster use

Open a Command Prompt window on the active node, and then run the following command for each private network in the failover cluste.
```
Cluster <ClusterName> network "NameofPrivateNetwork" /prop Role=1
```
Note

If you have any networks, including iSCSI networks, that you do not want to be managed or used by the cluster, set the value for Role to 0.
Verify that all private networks are configured for internal cluster communications only (private), and that all public networks are configured for all communications (mixed) by running the following commands and verifying that the role for private networks is set to 1 (0x1) and the role for public (mixed) networks is set to 3 (0x3):.
```
Cluster <ClusterName> network "NameofPrivateNetwork" /prop
Cluster <ClusterName> network "NameofPublicNetwork" /prop
```
Repeat the preceding commands for each additional private and public network in the failover cluster.

To use Cluster.exe to configure cluster network priority

Open a Command Prompt window on the active node and run the following command.
```
Cluster <ClusterName> /setnetpri:NameofPrivateNetwork,NameofPublicNetwork
```
Note

The /setnetpri option is order-dependent. If you have multiple public or private networks, ensure that all private networks are at the top of the network priority by listing them first in the command (for example, Priv1,Priv2,Pub1,Pub2).

Dela via