Bug ID 499150: OneConnect does not reuse existing connections in VIP targeting VIP configuration

Last Modified: Apr 10, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
10.2.4, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4

Fixed In:
12.0.0, 11.6.0 HF5, 11.5.3

Opened: Jan 01, 2015
Severity: 3-Major
Related AskF5 Article:


Significant increase in Active Connections and Connections per Second for virtual servers that receive connections from another virtual server with the Policy action 'virtual' or iRule command 'virtual' and the client virtual server has a OneConnect profile. The connections per second will match the rate of HTTP requests sent to the server virtual server. A packet capture would reveal that OneConnect is not reusing previously opened connections, and previously opened connections remain idle until timeout.


An increase in CPU and memory resources occurs due to the increase in connections established and connections that remain in memory.


This occurs when either of the following conditions are met: -- Virtual-to-virtual configuration with OneConnect profile. -- iRule contains the following command: node <ip> <port>.


If not required, remove the OneConnect profile from the client virtual server.

Fix Information

Connections are correctly reused even with VIP on VIP configuration.

Behavior Change