Bug ID 632386: EdgeClient cannot establish iClient control connection to BIG-IP if another control connection exists

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP APM(all modules)

Fixed In:
13.0.0, 12.1.2 HF1

Opened: Dec 07, 2016

Severity: 3-Major


When a iClient control connection, between Edge Client and BIG-IP, exists for a given session id, a new iClient control connection for the same session id cannot be established until the existing connection is torn down. When the client interface is down or the client changes networks, it takes time for the BIG-IP to detect that the existing control connection is down. During this time, if the client attempts to establish a new control connection (interface up or different network), BIG-IP rejects the new connection request.


Edge Client cannot establish a iClient control connection and hence a tunnel to the BIG-IP.


EdgeClient attempts to open a new iClient control connection with the same session id as that of an existing control connection and without explicitly closing the current connection. This could happen when the client interface is down or clients changes the network it is on.



Fix Information

When BIG-IP sees a new iClient control connection request for a session id for which another iClient control connection exists, the existing connection is closed and the new connection request is attempted to be accepted.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips