Configuring the Public and Private Networks
NOTE:
Private and public NICs must be configured in different subnets, otherwise the cluster
service and Cluster Administrator utility cannot detect the second NIC.
In clustered systems, node-to-node communication occurs across a private network, while
client-to-cluster communication occurs across one or more public networks. To review the
Microsoft recommendations and best practices for securing your private and public networks,
go to:
http://technet2.microsoft.com/windowsserver/en/library/
f64e46ba-2d09-4f1a-ba9c-f2b1f71821eb1033.mspx?mfr=true
When configuring your networks, observe the following guidelines:
•
Set your private network IP address to a unique, nonroutable value on each cluster, as
discussed in Microsoft Knowledge Base Article Number 142863, "Valid IP Addressing for
a Private Network":
http://support.microsoft.com/default.aspx?scid=kb;EN-US;142863
For example, use a valid private IP address of 10.1.1.1 with a subnet mask of 255.0.0.0 for
node A, and an IP address of 10.1.1.2 with a subnet mask of 255.0.0.0 for node B, and so on.
•
If possible, install your private and public NICs in the same slots of each node in the cluster
(private NICs in same slot, public NICs in same slot, and so on).
•
Use NIC Teaming to provide redundancy of your public network (see
(page
27)).
NOTE:
You cannot use NIC Teaming to provide redundancy for your private network. However,
you can provide redundancy for your private network without having it fail over to the public
network by configuring an additional NIC on each cluster member in a different, nonroutable
subnet, and setting it for "Internal Cluster communication only". This method is described in
the Microsoft Knowledge Base Article Number 258750, "Recommended private "Heartbeat"
configuration on a cluster server," at:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;258750
Private Network
Before configuring the private network for your cluster, see the following Microsoft Knowledge
Base articles for Microsoft recommendations and best practices:
•
Article number 258750, "Recommended Private "Heartbeat" Configuration on a Cluster
Server," at:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;258750
•
Article Number 193890, "Recommended WINS Configuration for Microsoft Cluster Server,"
at:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;193890
•
Article Number 142863, "Valid IP Addressing for a Private Network," at:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;142863
To configure your private network, complete the following steps:
1.
Right-click the My Network Places icon on your desktop, and select Properties.
2.
Determine which Local Area Connection icon in the Network Connections window
represents your private network. Right-click that icon, select Rename, and change its name
to Private.
3.
Right-click the Private icon and select Properties.
"NIC Teaming"
Creating and Configuring the Cluster
25