The common problems are:
1. Not turning off keep alives
2. Inserting cookies into cacheable content (this causes other clients behind the same
cache to get the wrong cookie). Solution: write a rule to send all requests for cacheable
content (.jpg, .gif, etc) to a non-cookie persistence vip and set all other content to non-cacheable.
p.s. You can change the pool name to ignore all prior cookies.
From: Chris Kirby [mailto:ckirbyIZZATstreetviews.com]
Sent: Tuesday, April 24, 2001 8:22 AM
Subject: [load balancing] F5 BigIP Persistence Checking
I'm trying to configure persistence checking on our F5 Bigip
box so a user is always returned to the same node. The pool
has been set with insert cookie persistence with a 30 minute
timeout. We have one virtual server that uses this pool as a
However, our logon sessions are still getting bounced around
different nodes when clicking through the site. Does the
persistence mode take awhile to take effect or is it immediate?
Do all pre-existing cookies have to be deleted on the web browser
clients first? Just throwing out some questions. :)
Any input would be greatly appreciated.
This archive was generated by hypermail 2b30 : Tue Apr 24 2001 - 14:26:40 EDT