Foundry Switch and Router Installation and Configuration Guide
26 - 4
December 2000
When the web browser sends its TCP SYN request (to initiate the HTTP session with the web host), the gateway
router used by the client’s computer looks in its routing table for the route to the requested IP address. The router
may receive multiple paths, in which case the router typically chooses the path with the lowest cost (usually the
number of router hops to the host) to place in the routing table. The paths can all go to the same host or to
different hosts. In the case of globally-distributed SLB, the paths go to different hosts. The shortest path takes the
client to the gateway router attached to the ServerIron, third-party SLB, or directly-attached server that is closest
to the client. Thus, when a client on the West coast requests the web site, the client’s gateway sends the request
to the ServerIron in Los Angeles. A client in London would instead be directed to the directly-attached server in
Paris.
The router’s behavior works well when all the real servers are available. However, suppose the real servers
attached to the ServerIron in Los Angeles become unavailable. This results in the VIP on that ServerIron
becoming unavailable.
NOTE:
You can associate “remote” servers with a VIP configured on a ServerIron, in which case the ServerIron
fails over to the remote servers if all local servers are unavailable. Remote servers are a less robust alternative to
the ServerIron’s globally-distributed SLB feature. There is no restriction against using remote servers in a
globally-distributed SLB configuration, but globally-distributed SLB makes the use of remote servers unnecessary.
In a globally-distributed SLB configuration, a client can still reach the desired VIP (web site) if the client's gateway
router receives a path to another site that contains the VIP the client is trying to reach. However, gateway routers
typically advertise network routes rather than host routes. As a result, even if the VIP (web site) is unavailable, the
gateway router still advertises the network to which the VIP belongs. Consequently, a client's gateway router can
still have a path to the unavailable server, in which case the client does not receive the requested web page.
By configuring the Foundry Layer 3 Switches attached to the ServerIrons, third-party SLBs, or real servers that
contain the web site to check the health of the web site (HTTP application), you can ensure that the Foundry Layer
3 Switches advertise paths only to for web site locations that are available:
•
If the web site passes the health check, the Foundry Layer 3 Switch advertises a host route to the web site’s
IP address.
•
If the web site fails the health check, the Foundry Layer 3 Switch removes the host route. The route is no
longer advertised and ages out of the routing tables in clients’ gateway routers.
As a result, those paths to the web site’s IP address that are no longer available age out of the routing tables on
gateway routers while the paths that are still available remain in the routing tables. When a client uses its gateway
router to reach the web site, the gateway's path to the site’s IP address is usually the one with the lowest cost. In
Figure 26.1, when the site at Los Angeles is available, the client's gateway uses the path to Los Angeles as the
route to IP address 209.157.22.249. However, if the IP address at the Los Angeles site becomes unavailable and
thus fails its health check, the NetIron at the Los Angeles site removes the static host route for 209.157.22.249
from its route table. The path on the client's gateway ages out and is replaced by the next valid path with the
lowest cost, in this case the path to 209.157.22.249 at the New York site.
HTTP Health Check Algorithm
When you configure a Layer 3 Switch to periodically check the health of the HTTP port on a web server, the router
does one of the following based on the result of the health check. The health check algorithm applies regardless
of whether the web server is directly attached to the Layer 3 Switch (or attached through Layer 2 Switches) or is
attached to a ServerIron or third-party SLB that is load balancing the IP address among multiple servers.
•
If the health check is successful, the router places a static host route in its route table for the web site’s IP
address. When the router sends a routing advertisement, the host route is included. The client's gateway
router will receive this host route as one of the paths to the IP address.
•
If the health check is not successful, the router removes the static host route (if present) for the IP address.
As a result, the route ages out of the routing tables on other routers. After the removed route ages out of the
routing table on the client's gateway router, the router accepts another path to the IP address.
You can configure a separate HTTP health check for each web site IP address. The health check consists of a
standard TCP connection followed by a standard request for an HTTP page on the IP address. If the HTTP page
responds with an acceptable HTTP status code, the IP address passes the health check, at which point the
Summary of Contents for Switch and Router
Page 2: ...December 2000 Copyright 2000 by Foundry Networks Inc ...
Page 26: ...Foundry Switch and Router Installation and Configuration Guide xxvi December 2000 ...
Page 64: ...Foundry Switch and Router Installation and Configuration Guide 2 34 December 2000 ...
Page 162: ...Foundry Switch and Router Installation and Configuration Guide 5 38 December 2000 ...
Page 196: ...Foundry Switch and Router Installation and Configuration Guide 6 34 December 2000 ...
Page 208: ...Foundry Switch and Router Installation and Configuration Guide 7 12 December 2000 ...
Page 236: ...Foundry Switch and Router Installation and Configuration Guide 8 28 December 2000 ...
Page 258: ...Foundry Switch and Router Installation and Configuration Guide 9 22 December 2000 ...
Page 420: ...Foundry Switch and Router Installation and Configuration Guide 13 32 December 2000 ...
Page 442: ...Foundry Switch and Router Installation and Configuration Guide 14 22 December 2000 ...
Page 554: ...Foundry Switch and Router Installation and Configuration Guide 15 112 December 2000 ...
Page 574: ...Foundry Switch and Router Installation and Configuration Guide 16 20 December 2000 ...
Page 626: ...Foundry Switch and Router Installation and Configuration Guide 17 52 December 2000 ...
Page 682: ...Foundry Switch and Router Installation and Configuration Guide 18 56 December 2000 ...
Page 826: ...Foundry Switch and Router Installation and Configuration Guide 20 20 December 2000 ...
Page 994: ...Foundry Switch and Router Installation and Configuration Guide 26 10 December 2000 ...
Page 1004: ...Foundry Switch and Router Installation and Configuration Guide B 6 December 2000 ...
Page 1044: ...Foundry Switch and Router Installation and Configuration Guide C 40 December 2000 ...
Page 1048: ...Foundry Switch and Router Installation and Configuration Guide D 4 December 2000 ...
Page 1070: ...Foundry Switch and Router Installation and Configuration Guide Index 18 December 2000 ...