Alteon Application Switch Operating System Application Guide
Persistence
594
Document
ID:
RDWR-ALOS-V2900_AG1302
B
Look for the Cookie in the URI
The last "Look for cookie in URI?" parameter is set to enable. As a result, Alteon uses
UID=12345678
as the cookie.
Example
2: Parsing the Cookie
This example shows three configurations which use the hashing key or wildcards to identify which
part of the cookie value should be used for determining the real server. For example, the value of
the cookie is defined as follows:
>> Cookie: sid=0123456789abcdef; name1=value1;...
A
Select the entire value of the sid cookie as a hashing key for selecting the real server
This command directs Alteon to use the sid cookie, starting with the first byte in the value, and
using the full 28 bytes.
B
Select a specific portion of the sid cookie as a hashing key for selecting the real server
This command directs Alteon to use the sid cookie, starting with the eighth byte in the value,
and using only four bytes. This uses 789a as a hashing key.
C
Using wildcards for selecting cookie names
With this configuration, Alteon looks for a cookie name that starts with ASPSESSIONID
.
ASPSESSIONID123
,
ASPSESSIONID456, and ASPSESSIONID789 are seen as the same
cookie name. If more than one cookie matches, only the first one is used.
Example
3: Using Passive Cookie Mode
If you are using passive cookie mode, Alteon examines the server's
Set-Cookie
: value and directs
all subsequent connections to the server that assigned the cookie.
For example, if Server 1 sets the cookie as "
Set-Cookie
:
sid=12345678
", then all traffic from a
particular client with cookie
sid=12345678
is directed to Server 1.
>> # /cfg/slb/virt 1/service 80/pbind cookie passive UID 1 8 ena
>> # /cfg/slb/virt 1/service 80/pbind cookie passive sid 1 16 dis
>> # /cfg/slb/virt 1/service 80/pbind cookie passive sid 8 4 dis
>> # /cfg/slb/virt 1/service 80/pbind cookie passive ASPSESSIONED* 1 16 dis
>> # /cfg/slb/virt 1/service 80/pbind cookie passive sid 1 8 dis
