Forum Discussion
Robert_77728
Jun 15, 2011Nimbostratus
session persistence issue
- natheCirrocumulusRobert,
- hooleylistCirrostratusDestination address persistence uses the client's destination IP address, so it's only really useful for network virtuals. As Nathan said, try source address persistence.
- Robert_77728NimbostratusThanks. What do you need to know about our setup to know if source address persistence is what I should be using?
The mask is "None" because I'm using the default profile.
- hooleylistCirrostratusIs this HTTPS traffic? Do your clients support cookies? If yes to both of those I'd suggest using cookie insert persistence with a OneConnect profile. This should give more granular load balancing across pool members compared with source address persistence.
- Robert_77728NimbostratusThe traffic is HTTPS to the Big-IP LTM and then the SLL if offloaded by the Big-IP LTM and the traffic is then HTTP to the servers. Cookies... no because they aren't required but we do use cookie-less sessions though.
- Robert_77728Nimbostratusnathan, if I use source address persistence can I use the default source address profile or do I need to change anything? Thanks.
- natheCirrocumulusRobert,
- Robert_77728NimbostratusResolved! I changed it to source address and had to really bump the timeout up! Thanks!!!
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