when & how does secondary or backup persistence method gets applied. Is it only when primary method fails, if so how does ltm determine to apply seconday method.
When F5 detects the primary persistence is not working, fall back would be applied. e.g. cookies are blocked/not supported in client browsers if primary is cookie, SSL session I'd changes frequently and primary persistence method is SSL.
When F5 detects the primary persistence is not working, fall back would be applied. e.g. cookies are blocked/not supported in client browsers if primary is cookie, SSL session I'd changes frequently and primary persistence method is SSL.
Thanks. when the user accesses an application, does the f5 apply persistence information only once for that connection or per request?
It is quite confusing as the user may access an application page but then continue to use many of other functions within the same page, will it use persistence again in this case.
Persistence record is maintained for the session. BIGIP sends request from the same client to the same member throughout the session if persistence is enabled.
By default, the BIG-IP system performs load balancing once for each TCP connection. When you configure a persistence profile on a BIG-IP virtual server, the BIG-IP system tracks a pointer to the pool member that serviced a client request.
If you want to apply load balancing and persistenc per "HTTP request" you can enable oneconnect and cookie persistence. I would suggest have a good read on below articles
Thanks. So does it mean, if a user opens an application first time via f5 would that be the start of tcp connection & a one time load balancing decission will be made?
& as long as the application is being used by user will it be considered one tcp connection having multiple http requests?
