Forum Discussion
Michael_Yates
Mar 02, 2012Nimbostratus
Hi NGT IT,
If I am reading your question correctly you are wanting to know if multiple requests within the same TCP Connection can be evenly distributed.
The answer to your question is yes, but the behavior that you get is depends upon the context that you are using it.
If you have multiple request from the same client within a TCP Connection, they should all be pinned to the same server through the normal server affinity persistence behavior of the LTM. If you have multiple clients within the same TCP Connection, then the deeper inspection of each request that is performed by the OneConnect Profile will load balance them to different pool members.
I would suggest reviewing the DevCentral Wiki Post for the ">OneConnect Profile. The behavior that I am describing is listed in this Wiki Entry.
Without OneConnect enabled, persistence data is examined only in the first request of a Keep-Alive connection, so if multiple requests are sent on the same clientside Keep-Alive connection, LTM will persist them all to the same destination as the first unless a OneConnect profile is applied (even if logic contained in an iRule dictates otherwise).
When using services like Akamai, where all of your connections appear to be coming from a single TCP Connection is where the OneConnect Profile really shines.
Hope this helps.