Forum Discussion
Source address Persistance & OneConnect profile
Hi folks,
I have a customer who needs a 30min source address persistence, this is causing issue with overloading random pool members, the issue is with number of requests in a single tcp connection coming from some sources being very high because sources are terminal servers, one of the solutions I am looking at is OneConnect profile but I don't know what is the behavior/affect of OneConnect to source address persistence, any idea?
Thanks.
1 Reply
- Vijay_E
Cirrus
OneConnect forces load balancing decision for every HTTP request. However, with source IP persistence in place, the requests will still be sent to the already selected pool member based on the persistence key.
If you need better distribution, you can lower the source IP persistence netmask to /32 instead of the default /24. Cookie persistence is better than changing the source IP persistence netmask.
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