unbalanced pool , persistence problem

This is my theory at the moment - is this plausible?

 

 

Currently, there are two persistence methods configured. The default is cookie and the fallback is source-ip. The theory is that when a client connects and doesn’t have a cookie, the F5 looks at the client source ip (in this case, all our call center users share the same source ip) and sends the client to the pool member that ip last connected to. When the session is established, the client receives a cookie that persists the session with that web server. Thus, all our call center traffic is persisted to the same server. This would also explain why the hardest hit server changes when a code rollout is done and the servers are disabled in the pool one at a time. When a server is disabled in the pool, new connections are not allowed and so they go to a different web server and the cycle repeats.

 

 

My thought, was to remove the fall back persistence method of source-ip.