Experts configure the cluster for windows2003 coup

I believe many system users are not familiar with the concept of clustering, but cluster technology plays an important role in the organization of key business, e-commerce and business process applications. Therefore, this article will lead everyone to participate in the cluster configuration based on Windows2003 operating system, from the following configuration process, I hope readers can really understand the powerful features of Windows2003 cluster technology in Windows2003.

What is a configuration cluster?

A so-called cluster is to run the same software on a group of computers and virtualize it into a host system to serve clients and applications; the computer is physically connected by cable And through the cluster software to achieve the connection on the program, the computer can achieve fault tolerance and load balancing that cannot be achieved by a single machine.

First, let's talk about the required environment:

Each machine has only one network card, operating system windows2003 sp2,

Prepare three IP addresses, such as: Server A: 192.168. 0.2 Server B: 192.168.0.3 and for cluster IP: 192.168.0.5

The next steps are as follows:

Create a new cluster on A (Control Panel -> Management Tools -> ;There are cluster management tools below), the IP address of the cluster is 192.168.0.5

The mode should be selected as "multicast" Please note that here you want to select “multicast”, unicast mode I tried The second host cannot be added in one day.

The filtering mode of the port rule is: multiple hosts: no need to choose a single here, because when it is single, when one of the servers hangs, then Requests that were previously connected to this server are not automatically forwarded to another server, which is obviously not what we want to see.

He will show that it is being aggregated. In general, it will be aggregated.

Next, go to Server B: Also open the Cluster Manager "Network Load Balancing Manager"., connect to the new cluster. Enter the IP address of A. This time it is very likely to prompt “ The host can't access ” or “ can't locate the situation”, or ask for the login user name and password, etc., but it is not correct. At this time, you can refer to Microsoft's documentation to modify the registry, disable authentication or other methods.

When there is no problem, you will see that the server has been aggregated.

Add B to Server A and choose to add the host to the cluster. If the problem in the previous step is solved, there is usually no problem here.

Then switch to B, select Add Host to Cluster, and add its own IP to the cluster.

After a while, the display will be aggregated.

At this point, we can receive the cluster ip: 192.168.0.5 on IIS to test whether our configuration is valid. The IIS of both servers receives the cluster IP instead of the original IP.

Create two pages with the same address and different page contents. Put them on two servers, turn off one to see what's displayed, turn off the one, and start that one to see the changes.

We are generally done.

Note:

The account and password of the two servers must remain the same.

<;Network Load Balancing Manager> After configuration, please save the host list. Otherwise, you will not see the list the next time you open it. Both servers must be saved.

The log can be turned on so that the problem can be analyzed.

Cluster technology plays an important role in the enterprise. Although most of our users don't understand the concept of configuring clusters in Win2003 system, we still introduce this powerful feature to everyone. Functional friends should remember to share.