Configure Cookie Stickiness

[Live2 Bicycle]

Needing to setup cookie based stickiness for the oracle guys. We have two 6513’s with CSM software version 3.1(4). I read a few of the Cisco docs to try and figure this out myself but what I configured is not working.

Here is what the oracle guys want. If user is on Server 10.10.103.14 and Server 10.10.103.14 goes down the load balancers currently switches to Server 10.10.103.15. If server A comes back up the user is currently switched back to Server 10.10.103.14 and the session is lost. The Oracle guys want the user to stick on Server 10.10.103.15 until the session is completed.

What is the best way to accomplish this using cookies and can you provide some config examples. Below is what my current config looks like.

serverfarm ORACLEAPPFARM3

nat server

no nat client

predictor hash address source

failaction purge

real 10.10.103.14

inservice

real 10.10.103.15

inservice

health retries 2 failed 2

probe ORACLEICMPPROBE

sticky 3 cookie CookieAPPFARM3 insert

!

policy POLICYAPPFARM3

sticky-group 3

serverfarm ORACLEAPPFARM3

vserver ORACLEVIRTUAL3

virtual 10.0.103.22 any

serverfarm ORACLEAPPFARM3

replicate csrp connection

persistent rebalance

slb-policy POLICYAPPFARM3

inservice

[Gilles Dufour]

cookie insert was introduced in version 4.1.

So it is most probably not doing much with your 3.1 version.

http://www.cisco.com/en/US/products/hw/modules/ps2706/prod_bulletin09186a00802072b0.html

If you do not want to upgrade, you can do sticky based on source ip.

Replace your sticky 3 cookie command with a 'sticky 3 netmask /32 timeout 600'

Also, if you do stickyness you should change your predictor command to 'predictor leastconn' or 'predicot roundrobin'.

Regards,

Gilles.