Detailed explanation of IIS Server Load balancer-application request route Article 2: Create and configure Server Farm

Since the release of this series, I have received replies from many friends! Thank you very much. At the same time, many friends have asked some questions, some of which are basic questions. Due to the time, they will not reply to them one by one. If they do not understand, I hope you will learn by yourself! Although this series is not difficult, many of the knowledge is required by default, such as the concept, principle, and Web farm of Server Load balancer.

This topic is as follows:

Create server farm

Configure server farm

The application request route module is used together with the server farm module. You can use application request route for HTTP Request Routing only after the server farm is created. Server farm is simply a logical grouping of one or more servers for ease of management and HTTP Request Routing.

In the previous articleArticle, We have introduced how to install and configure arr. Next, we started to create and configure the server farm.

Create server farm

1. Start the control panel of IIS 7 and see the following interface (taking win Server 2008 as an example ):

2. Select "server farms", right-click, and select "create server farm ".

3. Name the new server farm.

4. Add a server to the new server farm and enter the server address.

5. After Entering the address of the server to be added to the server farm, you can click "add" to add it. In addition, you can click "Advanced Settings" to perform advanced settings, as shown below.

In "Advanced Settings", you can set the port of the newly added server. For example, in the added server 192.168.0.1, the site is not placed on port 80, but on another port, we can set it here to tell arr to forward requests to other ports of 192.168.0.1 in the future, instead of 80.

In addition, you can also set the weight of the server (weight). Later, we can choose weight-based load balancing for arr.Algorithm.

6. After adding, you can see the result as follows:

7.If necessary, we can add more servers to the newly created mynewserverfarm. Just right-click "mynewserverfarm" or "servers.

Configure server farm

1.Select "mynewserverfarm". The following page is displayed on the right:

Through this interface, we can visually configure and monitor arr.

2. Server Load balancer algorithm selection:Double-click the "load balance" icon. Select the ARR load balancing algorithm. The interface is as follows:

Here we provide different routing algorithms for Server Load balancer in 7. Through the method name, we can understand each algorithm very well. For details about algorithms, refer to this article: Common Load Balancing algorithms. The types and numbers of algorithms provided here are different, but the principles are the same:Partial Pressure!

3. Server Health Monitoring: Arr can be configured to send a GET request to check whether the server in the server farm is in good state. This principle is the same as we ping a computer from time to determine whether it can be connected.

We can place a file in each site (any files allowed by IIS, such as txt, HTML, and aspx pages, cannot be. for example, http: // localhost/MyApp/test.html, put a piece of text on this page: Good. Start configuration, as shown in:

Arr sends a request every 30 seconds, and then compares the Request Response to determine whether the server is in good state. Of course, we can write more complex statements to determine whether the server is in good state.CodeBecause health test implements the provider mode, we can replace the algorithm. This advanced feature will be discussed later.

This article is here! Next, we will actually start to use arr for request forwarding.

Link: http://www.agilesharp.com/u/yanyangtian/Blog.aspx/t-199