Forum Discussion
Frank_69873
Nimbostratus
NimbostratusF5 Load Balancer using Cookies to route traffic.
We have many F5 Load balancers. I am investigating using Cookies to ensure that my traffic gets routed to servers behind a load balancer. The cookies that we are planning to use are for devices that ...
Kevin_Davies_40
Nacreous
NacreousLooks like you want manual persistence based on what values you supply. Easy enough.
when HTTP_REQUEST {
persist uie [HTTP::header select-server]
}
That will choose a server based on load balancing then when it sees the same data in the select-server header next time it will send the request back to the same server.
Frank_69873Nimbostratus
NimbostratusI have been reading about Universal persistence using cookies...It always assumes the pooled server will supply the cookie.
Here is what we need...
1) An initial HTTP request arrives with a cookie (IP address of a downstream destination device being served by the pool member)
2 ) The BIG-IP LTM UIE parses the request and sees the cookie. If now looks in the persistence table of the association. There is none so it sets one up using Load balancing.
3) The response comes back. There is no cookie in the response but we do no care as the clients manually set and send the cookie.
The next HTTP request arrives from a different client trying to get the the same downstream destination device.
1) The BIG-IP LTM UIE parses the client request for the Cookie header, finds the destination server IP cookie, and matches the cookie to the entry in the persistence table.
2) The BIG-IP LTM persists the client request to the same pool member as was set up in the last request.
Is this possible?
