Table of Contents
Advertisement
Example:
n
Real Server 1: "Gold" handles gold requests.
n
Real Server 2: "Silver" handles silver request.
n
Real Server 3: "Bronze" handles bronze request.
n
Real Server 4: "any" handles any request that does not have a cookie or matching
cookie.
With servers defined to handle the requests listed above, here is what happens:
n
Request 1 comes in with no cookie; it is forwarded to Real Server 4 to get cookie assigned.
n
Request 2 comes in with "Gold" cookie; it will be forwarded to Real Server 1.
n
Request 3 comes in with "Silver" cookie; it will be forwarded to Real Server 2.
n
Request 4 comes in with "Bronze" cookie; it will be forwarded to Real Server 3.
n
Request 5 comes in with "Titanium" cookie; it will be forwarded to Real Server 4, since it
does not have an exact cookie match (matches with "any" configured at Real Server 4).
4.
Configure the real server(s) to handle the appropriate load balance string(s).
To add a defined string:
>> # /cfg/slb/real 2/layer7/addlb <ID>
where ID is the identification number of the defined string.
N
OTE
dle any request.
5.
Enable DAM on the switch or configure a proxy IP address on the client port.
To use cookie-based preferential load balancing without DAM, you must configure a proxy IP
address on the client port.
N
OTE
disabled, you need only one proxy IP address.
Enable proxy load balancing on the port used for cookie-based preferential load balancing. If
Virtual Matrix Architecture (VMA) is enabled on the switch, you can choose to configure the
remaining ports with proxy IP disabled.
212777-A, February 2002
–
If you don't add a defined string (or add the defined string "any"), the server will han-
–
If VMA is enabled, you need to configure a proxy IP address on ports 1-8. If VMA is
Web OS 10.0 Application Guide
Chapter 15: Content Intelligent Switching
n
385
Advertisement
Table of Contents
