Windows 2003 cluster Installation configuration full Introduction (III)

Configuring the second node

&http://www.aliyun.com/zixun/aggregation/37954.html ">nbsp; Installing the Cluster service on another node takes less time than spending on the first node. The Setup program configures the Cluster service network settings on the second node based on the configuration of the first node. At the same time, you can add multiple nodes to the cluster through remote operations.

Note: For this section, open node 1 and all shared disks, and then open all other nodes. At this point, the Cluster service Controls access to the shared disk in order to eliminate any chance of damaging the volume.

1. Open Cluster Administrator on Node 1.

2. Click File, click New, and then click Nodes.

3. The Add Cluster Computer Wizard will start and click Next.

4. If you do not log on with the correct credentials, you will be asked to specify a domain account that has administrative rights to all nodes in the cluster.

5. Enter the machine name of the node you want to add to the cluster, and click Add. Repeat this step, as shown in Figure 21 below, to add the other nodes you want. When you have finished adding all the nodes, click Next.

Figure 21. Add nodes to the cluster.

6. The Setup Wizard performs an analysis on all nodes to confirm that they are properly configured.

7. Type the account password used to start the Cluster service.

8. Check the summary information displayed for confirmation. Summary information will be used to configure other nodes when they join the cluster.

9. Check all warnings or errors encountered during cluster creation, and then click Next.

10. Click Finish to end the installation.



Configuration after installation: Heartbeat configuration

Now that the network on each node is properly configured and the Cluster service is configured, you need to configure the network roles to define the capabilities of each network in the cluster. Here is a list of network configuration options in Cluster Administrator:

· Enabled for cluster application: If this check box is selected, the Cluster service will use the network. By default, this check box is selected for all networks.

· For client access only (public network): Select this option if you want the Cluster service to use only this network adapter for external communication with other clients. The network adapter will not communicate node to node.

· For internal cluster communications only (private network): Select this option if you want the cluster to communicate with nodes only using that network.

· All communications (mixed networks): Select this option if you want the Cluster service to use this network adapter for node communication and external client communication. By default, this check box is selected for all networks.

This white paper assumes that only two networks are used and explains how to configure the two networks as mixed and private networks, respectively. This is the most common configuration. If you have available resources, it is recommended that you use two dedicated redundant networks for internal cluster communications.

Configure Heartbeat

1. Start Cluster Administrator.

2. In the left pane, click Cluster Configuration, click Network, right-click Private, and then click Properties.

3. Click for internal cluster communications only (private network), as shown in Figure 22 below.

Figure 22. Use Cluster Administrator to configure your heartbeat.

4. Click OK.

5. Right-click Public, then "Properties" (as shown in Figure 23 below).

6. Click to select the Enable this network for cluster application check box.

7. Click All communications (mixed network), and then click OK.

Figure 23. Public Properties dialog box.

Heartbeat Adapter Priority

After you configure how the Cluster service applies the role of the network adapter, the next step is to prioritize internal cluster communications applications. This applies only to two or more networks configured as nodes to communicate with nodes. The priority arrow to the right of the screen specifies the order in which the Cluster service uses each network adapter to communicate between nodes. The Cluster service always attempts to use the first-listed network adapter for Remote Procedure Call (RPC) communication between nodes. The next network adapter on the list is used only if the Cluster service cannot communicate with the first network adapter.