Forum Discussion
Using Encrypted persistence cookies with multiple LTMS
Hi All, I am using F5 default cookie for persistence defined on virtual server which is the same name for both datacenter. I use irule to route the traffic to the original data center in case traffic goes to another data center. But it looks like the persistence cookie is getting reset when it goes to opposite data center since the persistence cookie identifying the server is invalid for this new data center. Now when traffic is routed back to original data center again the cookie is invalid, so the session goes to a different server. Now how can i stop the persistence cookie being reset when it goes to opposite data center and kick off routing to original data center before any cookie is reset?
- Mark_CloutierMar 06, 2015
Nimbostratus
The persistence cookie contains the pool name, so you need to use the same pool name in both datacenters, or in the irule that does the redirection back to the "correct" datacenter, make sure you are redirecting before a load balancing decision is made, with the associated persistence application.... BTW, I have to revisit my setup, when I encrypted mine, sites stopped working, need to do more investigation as to why....
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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