Appendix G -- Managing IIS IP Bindings

When hosting multiple Web sites on a single cluster that uses an external load-balancing device, the cluster members are typically configured with multiple IP addresses, each of which is mapped to a Web site. Table G.1 illustrates such a case.

Table G.1 Binding Configuration for Members Hosting Multiple Web Sites

MemberSite ASite B
Server 11.1.1.12.2.2.1
Server 21.1.1.2 2.2.2.2
Server 31.1.1.3 2.2.2.3

Upgrading the member grouping illustrated in Table G.1 to a Microsoft Application Center 2000 (Application Center) cluster is not a problem, provided that it is handled correctly.

Because all cluster members are synchronized with the cluster controller, you should ensure that all content and configuration exists on the controller before adding any members. Unpredictable behavior can result if content or configuration information on the members is different from the controller. This includes IP address bindings for Web sites.

For example, if a cluster contains three members and the Default Web Site has three IP addresses bound to it (one for each member), you should bind all three IP addresses to the Default Web Site. Do not add these IP addresses to any network adapter on the controller. Use Internet Services Manager to bind IP addresses to Web sites. Adding IP addresses from other members to any network adapter on the controller might result in IP address conflicts on your network.

NOTE


Adding unused IP address bindings to Web sites in Internet Information Services 5.0 (IIS) will not impact performance. Because IIS only detects IP addresses that are bound to network adapters, adding additional IP address bindings to Web sites will not result in any performance degradation.

The next section shows the changeover process that you should use when moving servers that host multiple Web sites into the Application Center cluster environment.

Changeover Process

For the sake of this example, we'll assume that the cluster is created on Server 1, which will be the cluster controller.

  1. Create an Application Center cluster on Server 1.
  2. Configure the controller on this new cluster with all the bindings from the other servers, as shown in Table G.2.

    Table G.2 New Binding Configuration for the Cluster Controller

    MemberSite ASite B
    Server 11.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3
    Server 2 1.1.1.2 2.2.2.2
    Server 3 1.1.1.3 2.2.2.3

    NOTE


    There are no problems providing IIS bindings for IP addresses that do not exist on a server; IIS simply ignores any that are provided, which are not mapped to a server's TCP/IP settings.

  3. Add the two remaining servers to the Application Center cluster.

    Application Center automatically copies the IIS configuration settings from the controller to each member after the member joins the cluster.

    Table G.3 shows the binding configuration for all the members after the two new members are added.

    Table G.3 Member Binding Configuration After Adding Cluster Members

    MemberSite ASite B
    Server 11.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3
    Server 21.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3
    Server 3 1.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3

    Let's assume that you want to add another server to the cluster. This server will host Site A on 1.1.1.4 and Site B on 2.2.2.4.

  4. Add the IP bindings for the new server to the cluster controller.

    The new bindings for the cluster will look like those shown in Table G.4.

    Table G.4 New Binding Configuration for the Cluster Controller

    MemberSite ASite B
    Server 11.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.42.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4
    Server 21.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3
    Server 3 1.1.1.1, 1.1.1.2, 1.1.1.32.2.2.1, 2.2.2.2, 2.2.2.3
  5. Add the new member to the cluster.

    The IP bindings for the cluster will look like those shown in Table G.5.

    Table G.5 Member Binding Configuration After Adding a Member

    MemberSite ASite B
    Server 11.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.42.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4
    Server 21.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.42.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4
    Server 31.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.42.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4
    Server 41.1.1.1, 1.1.1.2, 1.1.1.3, 1.1.1.42.2.2.1, 2.2.2.2, 2.2.2.3, 2.2.2.4


Microsoft Application Center 2000 Resource Kit 2001
Microsoft Application Center 2000 Resource Kit 2001
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 183

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net