Alteon Application Switch Operating System Application Guide
Global Server Load Balancing
Document ID: RDWR-ALOS-V2900_AG1302 735
Configuring Static Client Proximity
This section details the client proximity workflow and procedures to configure the sites for Figure
125 - GSLB Client Proximity Site with HTTPS Service, page 735.
Figure 125: GSLB Client Proximity Site with HTTPS Service
In this example, the order of preference for Client X is Site C followed by Site B and Site A. When
Client X loads the browser and enters the URL www.radware.com/products/index.html, the system
sends a DNS getHostByname query to the client's local DNS server for the www,radware.com IP
address.
Workflow for GSLB Client Proximity Site with HTTPS Service
The following is the workflow for the example as shown Figure 125 - GSLB Client Proximity Site with
HTTPS Service, page 735:
1. The Client X DNS requests the local DNS server to send the www.radware.com IP address.
2. The local DNS server queries the upstream DNS server on Alteon.
3. The Site A Alteon receives a DNS request and acts as the authoritative DNS. Site A responds to
the DNS request with a Site A VIP address according to the DNS GSLB configured metric.
4. Client X opens an HTTP application session with an Alteon at Site A.
5. On receiving the request, Site A checks its client proximity table and finds a static entry. It
identifies Site C to be the closest site and sends an HTTP 302 redirection with Site C IP address/
domain name.
6. On receiving the request, Site C checks its client proximity table and serves the HTTP request.
To Next Page
Loading...
Need help?
General