Export (0) Print
Expand All
6 out of 9 rated this helpful - Rate this topic

How to Configure Network Connections for Cluster Continuous Replication

 

Applies to: Exchange Server 2007 SP3, Exchange Server 2007 SP2, Exchange Server 2007 SP1, Exchange Server 2007

Topic Last Modified: 2008-07-15

This topic explains how to configure network connections to support a Microsoft Exchange Server 2007 clustered mailbox server in a cluster continuous replication (CCR) environment. Proper configuration of the network connections is necessary to ensure that client connections to the cluster server are possible and happen in a timely fashion. There are three procedures that must be performed prior to forming the clusters:

  • Configure the network connection order
  • Configure the public network connections
  • Configure the private network connections
    importantImportant:
    If you have a network adapter that can be manually configured to specify speed and duplex mode, and you are using a crossover cable, you should manually specify a speed and duplex mode. With network adapters that can manually specify a speed and duplex mode, make sure that you hard set them with the same configuration on all nodes and according to the manufacturers' specifications. For network adapters that do not support manual settings, follow the card manufacturer's specifications. The amount of information that is traveling across the private network is small, but latency is critical for communication. If you have the same speed and duplex settings, this helps to support reliable communication. If you are not sure of the supported speed of your card and connecting devices, or your manufacturer's recommended settings, we recommend that you set all the devices on that path to 10 megabytes (MB) per second and half duplex. This configuration provides sufficient bandwidth and reliable communication. For more information about the effects of using the Autodetect setting on network interface cards in cluster deployments, see Microsoft Knowledge Base article 174812, The effects of using Autodetect setting on cluster network interface card.

To perform the following procedures on a computer that is being configured for a clustered mailbox server, the account you use must be delegated the following:

  • Membership in the local Administrators group

For more information about permissions, delegating roles, and the rights that are required to administer Exchange Server 2007, see Permission Considerations.

You must have at least one network that has file-sharing capabilities for the Majority Node Set (MNS) quorum with file share witness to function. We recommend that you enable file sharing on multiple networks in the cluster to avoid a single point of failure for the quorum resource.

  1. In Control Panel, double-click Network Connections.

  2. On the Advanced menu, click Advanced Settings.

  3. In Advanced Settings, on the Adapters and Bindings tab, under Connections, make sure that your connections appear in the following order:

    • <Public network name> (where Public network name is the name of your public network connection)
    • <Private network name> (where Private network name is the name of your private network connection)
    • Remote access connections
  4. Click OK to save the changes.

noteNote:
If your clustered mailbox server has more than two networks, it is important to ensure that all public networks are at the top of the connection order list and all private networks are at the bottom of the connection order list.
  1. In Control Panel, double-click Network Connections.

  2. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your public network connection), and then click Rename.

  3. In the Name field, enter a meaningful name, such as Public.

  4. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your public network connection), and then click Properties.

  5. In <Network connection name> Properties, on the General tab, under This connection uses the following items, make sure that the Client for Microsoft Networks, Internet Protocol (TCP/IP) and File and Printer Sharing for Microsoft Networks check boxes are checked.

  6. Select Internet Protocol (TCP/IP), and then click Properties.

  7. In Internet Protocol (TCP/IP) Properties, click Advanced.

  8. In Advanced TCP/IP Settings, on the DNS tab, verify the following information:

    • Under DNS server addresses, in order of use, ensure that all of the required addresses are listed.
    • Under Append these DNS suffixes (in order), ensure that the correct suffixes are listed.
  9. On the WINS tab, ensure that Disable NetBIOS over TCP/IP is not selected.

  10. Click OK twice to save the changes, and then click Close to exit Properties.

  1. In Control Panel, double-click Network Connections.

  2. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your private network connection), and then click Rename.

  3. In the Name field, enter a meaningful name, such as Private.

  4. In Network Connections, right-click <Network connection name> (where <Network connection name> is the name of your private network connection), and then click Properties.

  5. On the General tab of the private network connection, under This connection uses the following items, select the Internet Protocol (TCP/IP) check box. Make sure that check boxes for Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks are checked.

  6. Select Internet Protocol (TCP/IP), and then click Properties.

  7. On the Internet Protocol (TCP/IP) Properties page, on the General tab, select Use the following IP address, and then configure a static IP address and subnet mask for the connection. Also select Use the following DNS server addresses, and leave blank the IP address fields for Preferred DNS server and Alternate DNS server, and then click Advanced.

    noteNote:
    The default gateway and Domain Name System (DNS) entries are left blank. It is not necessary to configure the default gateway or DNS settings because private cluster networks are used only for internal cluster communications.
  8. In Advanced TCP/IP Settings, on the DNS tab, verify the following information:

    • Under DNS server addresses, in order of use, make sure that no addresses are listed.
    • Make sure that the Register this connection's addresses in DNS check box is cleared.
  9. On the WINS tab, ensure that Disable NetBIOS over TCP/IP is selected.

  10. Click OK twice to save the changes, and then click Close to exit Properties.

To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.