Bug ID 475701: FastL4 with FIX late-bind enabled may not honor client-timeout

Last Modified: Apr 10, 2019

Bug Tracker

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

Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8

Fixed In:
12.0.0, 11.6.1

Opened: Aug 15, 2014
Severity: 3-Major


When insufficient initial data is received, the FastL4 fix late-bind timeout recovery action is not taken (no RST sent with disconnection and no default pool use with fallback).


The client-timeout feature does not work. Client connections seem to hang, and RST is not sent (when timeout-recovery disconnect) or the connection does not continue with standard FastL4 behavior (when timeout-recovery fallback) if enough initial data does not arrive within the client-timeout.


FastL4 profile with FIX late-bind enabled and insufficient data is received.


Setting tcp-handshake-timeout to a value that is greater than client-timeout might allow this to work.

Fix Information

FastL4 with FIX late-bind enabled now honors client-timeout.

Behavior Change