Installation and Troubleshooting Guide

22 Preparing Your Systems for Clustering
NOTE: Do not configure Default Gateway, NetBIOS, WINS, and DNS on the private
network. If you are running Windows Server 2003, disable NetBIOS on the
private network.
If multiple cluster interconnect network adapters are connected to a network
switch, ensure that all of the private network’s network adapters have a
unique address. You can continue the IP address scheme in Table 2-2 with
10.0.0.3, 10.0.0.4, and so on for the private network’s network adapters or
network adapter teams of the other clusters connected to the same switch.
You can improve fault tolerance by using network adapters that support
adapter teaming or by having multiple LAN segments. To avoid
communication problems, do not use dual-port network adapters for the
cluster interconnect.
NOTE: NIC teaming is supported only on a public network, not on a private network.
Creating Separate Subnets for the Public and Private Networks
The public and private network’s network adapters installed in the same
cluster node must reside on separate IP subnetworks. Therefore, the private
network used to exchange heartbeat information between the nodes must
have a separate IP subnet or a different network ID than the public network,
which is used for client connections.
Private network static IP address
cluster interconnect (for node-to-node
communications)
10.0.0.1 10.0.0.2
Private network subnet mask 255.255.255.0 255.255.255.0
Table 2-2. Examples of IP Address Assignments (continued)
Usage Cluster Node 1 Cluster Node 2