Forum Discussion
Hi Fasahat,
Are you using these servers in multiple pools? Are you using any fallback persistence method?
Perhaps consider using a load balancing method that takes into account the performance of your back end servers (observed,fastest,predictive), or even least connections based on node (if node is used multiple pools).
If OneConnect was enabled, I wouldn't expect it to affect your load balancing, just the communication LTM->Backend.
Also check to true up the results your server teams are telling you with the persistence statistics... Statistics > Module Statistics > Local Traffic > Persistent Records.
Do you see 100 versus 500 persistence records for the nodes affected?
Do the pool(s) statistics reflect the results or information from the server teams, in respect of current connections?
Just some suggestions of what I'd look at initially.
I suppose you could be unlucky in that one server had a lot of users who've closed their browser and others continued usage (if cookie persistence isn't set to expire until session end).