| Configuring the WSM using Device Manager |
|
The HTTP redirect function uses the best response and least load for the requested content to redirect requests to an alternate site. However, if the client requests a non-HTTP application, such as FTP, POP3, or SMTP, and resources are unavailable at the first site, then you can configure a proxy IP address on the client port to redirect requests.
Note:
This feature should be a last resort in topologies where remote servers are usually virtual server IP addresses in other WSMs.
The following figure illustrates the packet-flow of HTTP and non-HTTP redirects in a GSLB environment.
The following table describes the redirects shown in the figure above.
HTTP
1a. Client DNS request reaches Site 2, where resources are unavailable. Site 2 sends response to client with Site 1's virtual server IP address.
1b. Client re-sends request to site 1, where resources are available. Site 1 completes TCP three-way handshake with client.
Non-HTTP
2a. Client DNS request reaches Site 2, where resources are unavailable. Site 2 sends a request to Site 1 with Site 2's proxy IP address as the source IP address and the virtual server IP address of Site 1 as the destination IP address.
2b. Site 1 processes the client proxy IP request. Resources are available at Site 1. Site 1 returns request to proxy IP port on Site 2. Site 2 completes the three-way handshake with the client.
See also:
|
|