Forum Discussion
Sven_89244
Feb 10, 2011Nimbostratus
Persistence Behavior
Hello,
I've recognized a unusual behavior in the persistence handling.
I have a pool with two servers
Balancing is RoundRobin
Persistence is "Cookie insert". Cookies are limited to the session.
Now i've decoded the cookie in the packet (with http://devcentral.f5.com/wiki/defau...ogger.html) and compared it with the [LB::server addr]:[LB::server port] entry and found that they are not matching.
i.e.
Feb 10 07:09:54 tmm tmm[1797]: Rule persistence_cookie_logger : Request from client: 132.186.121.59:3603 contains persistence cookie referencing pool member 139.25.236.150:80 destination 139.25.236.151:80
Feb 10 07:09:55 tmm tmm[1797]: Rule persistence_cookie_logger : Request from client: 157.163.197.75:1896 contains persistence cookie referencing pool member 139.25.236.151:80 destination 139.25.236.150:80
This happens very often.
Does anyone have a hint for me
Thanks
3 Replies
Sort By
- O.k. in the Askf5-database i've found
Persistence may fail for subsequent requests on Keep-Alive connections - Any chance you could try OneConnect to see if that's the bug you're hitting?
- As Chris suggests, a OneConnect profile is definitely the way to correct this behavior. It's not really a bug per se. It's due to the default connection based load balancing.
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