Bug ID 553830: Use of OneConnect may result in stalled flows

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.2.1, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 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

Fixed In:
12.1.0, 11.2.1 HF16

Opened: Oct 22, 2015

Severity: 3-Major

Symptoms

Stuck serverside flows that do not expire

Impact

Excessive memory usage, tmm can crash.

Conditions

Serverside flow expires while clientside is closing while OneConnect is being used.

Workaround

Disable OneConnect. This can also be mitigated by ensuring the server-side idle timeout is not set lower than the client profile's fin-wait timeout while using OneConnect.

Fix Information

Connections utilizing OneConnect will be forcibly shutdown upon expiration

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips