HP Integrity rx5670 Windows Integrity Cluster Installation and Configuration G - Page 26

Setup, configuration, validation, and maintenance of the cluster Creating and configuring the cluster NOTE NOTE Creating and configuring the cluster The following sections describe the main steps needed to create and configure your cluster. Configuring the public and private networks Your private and public NICs must be configured in different subnets, otherwise the Cluster Service and Cluster Administrator utility will not be able to 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, see http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/8 7f23f24-474b-4dea-bfb5-cfecb3dc5f1d.mspx. When configuring your networks, remember the following general guidelines: • Set your private network IP address to a unique, non-routable value on each cluster, as discussed in Microsoft Knowledge Base Article Number 142863, "Valid IP Addressing for a Private Network," at http://support.microsoft.com/default.aspx?scid=kb;EN-US;142863. For example, a valid private IP address of 10.1.1.1 with subnet mask of 255.0.0.0 could be used for node A, while an IP address of 10.1.1.2 with subnet mask of 255.0.0.0 could be used for node B, and so on. • It is good practice (if possible) to install your private/public NICs in the same slots of each node in the cluster (private NICs in same slot, public NICs in same slot, etc.) • It is good practice to use NIC Teaming to provide redundancy of your public network (see "NIC teaming" on page 28) 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, non-routable 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 26 Chapter 2