OneConnect

What is OneConnect and its benefit?

“OneConnect” is trademark feature of F5 LTM (Local Traffic Manager) which uses the concept of
Connection Reuse Pool i.e. after LTM has sent request and received full response through the
connection, these connections are not torn down, rather put in the Connection reuse Pool. When a
new Client creates TCP connection with LTM, LTM reuses existing TCP connection from Connection
Reuse Pool instead of creating new LTM-Server TCP connection. This approach saves the system
resources like memory, CPU processes etc. of LTM and Server.

When using the OneConnect feature, you should consider the following factors:

When using OneConnect to optimize HTTP traffic, F5 recommends that you apply an HTTP profile to the virtual server. This allows the BIG-IP system to efficiently manage connection reuse without additional configuration. Failure to apply an HTTP profile may result in unexpected behavior such as backend server traffic being sent to the wrong client.

Avoid using a OneConnect profile for non-HTTP virtual servers that process more complex transactions, such as FTP or RTSP. Doing so may result in traffic disruption and session failure. Even for simple non-HTTP protocols, an iRule may be required to manage connection reuse.

When a virtual server is configured with a OneConnect profile the virtual server must also be configured with a L7 profile (including iRules) to avoid unexpected traffic processing behavior.

Avoid using a OneConnect profile for encrypted traffic that is passed through the virtual server to the destination resources in the encrypted state and is not terminated at the BIG-IP system.