Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Mar 12, 2016 Severity: 3-Major Related Article:
K21538416
Using OneConnect with forwarded flows might cause resets. The first connection attempt from the client works properly and sets up the OneConnect flow pool on one tmm, and a forwarding flow on another tmm. Then, when the client attempts a second connection, the system tries to reuse the forwarding flow, which returns failure and resets the connection. The system might report a reset cause such as 'Unable to obtain local port' or 'Out of ports', or in some versions, there might not be a specific reset cause reported.
Client connections are reset.
Using OneConnect and forwarding flows. The system uses forwarding flows when source-port preserve-strict is configured, when a virtual server is configured for 'cmp-enabled no', and in certain other circumstances. For example, this issue can be seen on 2000- and 4000-series platforms, when 'source-port preserve strict' is used with OneConnect.
Do not use preserve-strict and OneConnect together.
None