Forum Discussion
Andy_Herrman_22
Nimbostratus
Jun 21, 2006Problem with persistence
I have a setup with a BIG-IP load balancer with 2 servers in a pool being load balanced. The URI that the user is connecting with contains a query parameter that is used for the persistence value. A...
unRuleY_95363
Jun 23, 2006Historic F5 Account
Sheesh, I go on vacation one day and no one can seem to answer this for you...
The problem is that the persist command does not change the already connected back-end server on a subsequent request over the same connection. In order for that to happen, you could either enable OneConnect (add the oneconnect profile to your virtual) or modify the rule to call LB::detach if the uid value changes. Then the subsequent request would utilize the new persist setting to (re)connect to the appropriate server.
Also, just to be clear about the "persist add" command. In this case it is certainly not needed. That is because the "persist uie" command will add a record if it does not exist. Normally, the "persist add" command is only necessary if the first server response contains the information necessary to persist on (EG, as is the case with JSESSION type persistence).
Anyway, hope this helps and it's not too late.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects