Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1
Opened: Mar 26, 2018 Severity: 2-Critical
Under certain conditions BIG-IP systems may leak memory. Over time, the memory lost might affect performance/scalability as the unit approaches an out-of-memory condition. tmm crash
Over time, this issue might lead to a BIG-IP system out-of-memory condition, which results in a TMM crash and failover event. Traffic disrupted while tmm restarts.
-- UDP profile configured. -- CLIENT_ACCEPTED iRule in use.
You can use either of the following workarounds: -- Run the following command: tmsh modify sys db tmm.sessiondb.table_cmd_timeout_override value true -- Enable 'resassemble-fragments' in the FastL4 profile.
None