Microsoft KB Archive/315517

= How to manage Internet Information Services Web IP bindings by using third-party load balancing devices =

Article ID: 315517

Article Last Modified on 2/14/2007

-

APPLIES TO


 * Microsoft Application Center 2000 Standard Edition

-



This article was previously published under Q315517



SUMMARY
This step-by-step article explains how to manage IP address bindings of Web sites within an Application Center 2000 cluster by using any third-party load balancing device.



Prerequisites

 * An Application Center 2000 cluster already exists, which you created with the Other load balancing load balancing option selected.
 * Hardware and software network requirements for your load balancing device have been met.
 * TCP/IP traffic is successfully load-balanced between the servers.

Concept
When you configure Application Center for Other load balancing, Application Center replicates all of the Web site bindings from the cluster controller to the cluster members. This configuration can cause all of the servers except for the cluster controller to respond to HTTP requests in a manner similar to Figure 1.

Note If you configure the cluster for no load balancing, Application Center does not replicate the Web site bindings from the cluster controller to the cluster members, and the techniques that are discussed in this article are not required. However, if you configure the cluster for no load balancing, you cannot use the Load Balancing Tool (ACExt.exe) from the Application Center 2000 Resource Kit to manage the servers. For more information about the Load Balancing Tool and supported load balancers, click the following article number to view the article in the Microsoft Knowledge Base:

320041 Supported third-party load balancers for Application Center 2000

Figure 1:

[WebServer1]             (cluster controller) [NetworkAdapter1] 192.168.0.1

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80

[WebServer2]             (cluster member) [NetworkAdapter1] 192.168.0.2

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80

[WebServer3]             (cluster member) [NetworkAdapter1] 192.168.0.3

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80

Application Center is designed so that you can administer changes on a single server (cluster controller), and then the cluster members reflect the changes. To set up all of your servers to respond to HTTP requests, you must add the Web site bindings to the cluster controller that you typically would add to the cluster members. This procedure replicates the bindings to the cluster members.

NOTE: Internet Information Services (IIS) will ignore Web site bindings of IP addresses that do not exist on the respective server.

In the sample scenario in this article, we manually added two IP addresses, 192.168.0.2 and 192.168.0.3, to WebSite1 on the cluster controller (refer to Figure 2). To add Web bindings manually, click Advanced on the Web site Properties page. In this example, the Web bindings are set up correctly for third-party load balancing.

Figure 2:

[WebServer1]             (cluster controller) [NetworkAdapter1] 192.168.0.1

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

[WebServer2]             (cluster member) [NetworkAdapter1] 192.168.0.2

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

[WebServer3]             (cluster member) [NetworkAdapter1] 192.168.0.3

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

To add another Web site to the cluster (Figure 3), follow these steps:
 * 1) Add a new unique IP address to each of the servers.
 * 2) Create the new Web site on the cluster controller.
 * 3) Add the new IP address for each of the servers to the Web site bindings of the new Web site.

Figure 3:

[WebServer1]             (cluster controller) [NetworkAdapter1] 192.168.0.1  192.168.0.11

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

[WebSite2] [IP]             [Port]    [Host Header] 192.168.0.11     80     192.168.0.22      80     192.168.0.33      80

[WebServer2]             (cluster member) [NetworkAdapter1] 192.168.0.2  192.168.0.22

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

[WebSite2] [IP]             [Port]    [Host Header] 192.168.0.11     80     192.168.0.22      80     192.168.0.33      80

[WebServer3]             (cluster member) [NetworkAdapter1] 192.168.0.3  192.168.0.33

[WebSite1] [IP]             [Port]    [Host Header] 192.168.0.1      80     192.168.0.2       80     192.168.0.3       80

[WebSite2] [IP]             [Port]    [Host Header] 192.168.0.11     80     192.168.0.22      80     192.168.0.33      80

