Forum Discussion
LTM TCP Connection management
traffic was measured from both the F5 pool member statistics as well as the server side session table.. The server will always reflect the most accurate number of sockets that are in EST or TIME_WAIT state for example.
None of the things mentioned in that article apply here. Since I have seen this with Round robin that eliminates it being just with least connnections. This is one of those issues that I would need to get at the internals which I cant do without support. For example with some other vendor devices I can turn on specific types of debugging and observer the decision logic on where a request is sent based on the current configuration which is very helpful in these cases. It would at least provide some logic as to why more traffic is getting sent to same set of servers.
- What_Lies_Bene1Sep 04, 2013
Cirrostratus
I doubt very much if we'll get to the root cause of this, particularly with such an old version of code. However (Nitass gave me this idea in response to another post) perhaps it can be overcome using a more 'intelligent' load balancing method. Candidates would be Weighted Least Connections, Dynamic Ratio, Observed or Predictive.
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
