Forum Discussion
switching pools in irule without using oneconnect profile
Inside your HTTP_REQUEST event use the command LB::detach. This will remove the stickyness and allow your iRule to select a destination per HTTP request. The reason it is sticky is the pool selection is normally only performed once at the start of the TCP connection. Subsequent pool commands will have no effect unless you tell the F5 to detach the connection from the server side using the command given. When you are using oneconnect the server side is always detached.
See the following solution ID's which describe this behaviour
sol9800
sol7964
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