For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Netgus_312724's avatar
Netgus_312724
Icon for Nimbostratus rankNimbostratus
Mar 06, 2017

My load balancer don't balance...!

Hello all, I'm beginner with F5 LTM, but I know well other solution... I decided to discover this solution by following the tutorials of F5. For the moment nothing complicated since the configura...
application delivery
LTM
gsharri's avatar
gsharri
Icon for Altostratus rankAltostratus
Mar 07, 2017

You are seeing expected behavior. With your configuration BIG-IP is making one load balancing decision for the TCP connection not for every HTTP request. If you wish to load balance each http request to different pool members you must implement a OneConnect profile as explained here:

 

K7208: Overview of the OneConnect profile.

 

The relevant portion of the article is this:

 

Content Switching

When a OneConnect profile is enabled for an HTTP virtual server, and an HTTP client sends multiple requests within a single connection, the BIG-IP system is able to process each HTTP request individually. The BIG-IP system sends the HTTP requests to different destination servers as determined by the load balancing method. Without a OneConnect profile enabled for the virtual server, the BIG-IP system performs load-balancing only once for each TCP connection.