Table of Contents
Advertisement
Web OS 10.0 Application Guide
7.
Add the defined string IDs to configure the real server(s) to handle the appropriate load
balance string(s).
>> # /cfg/slb/real 2/layer7/addlb <ID>
where ID is the identification number of the defined string.
N
OTE
URL Hashing for Web Cache Redirection
By default, hashing algorithms use the source IP address and/or destination IP address
(depending on the application area) to determine content location. For example, firewall load
balancing uses both source and destination IP addresses, WCR uses only the destination IP
address, and SLB uses only the source IP address.
Hashing is based on the URL, including the HTTP Host header (if present), up to a maximum
of 255 bytes. You can optimize "cache hits" by using the hashing algorithm to redirect client
requests going to the same page of an origin server to a specific cache server.
For example the switch could use the string "nortelnetworks.com/products/180/" for hashing
the following request:
GET http://products/180 / HTTP/1.0
HOST:www.nortelnetworks.com
To configure the switch for WCR based on a hash key, use the following procedure:
1.
Configure basic SLB.
Before you can configure header-based cache redirection, ensure that the switch has already
been configured for basic SLB (see
tasks:
n
Assign an IP address to each of the real servers in the server pool.
n
Define an IP interface on the switch.
n
Define each real server.
n
Assign servers to real server groups.
n
Define virtual servers and services.
n
Configure the load-balancing algorithm to hash or minmiss.
n
406
Chapter 15: Content Intelligent Switching
–
If you don't add a defined string (or add the ID 1), the server will handle any request.
"Server Load Balancing" on page
117) with the following
212777-A, February 2002
Advertisement
Table of Contents
