Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Fixed In:
13.1.0, 12.1.3.2, 11.6.3.2
Opened: Aug 03, 2017 Severity: 2-Critical Related Article:
K21958352
- Number of active connections is increasing over time. - Memory used by TMM increases over time. - Potential TMM restart is possible.
- Service may be impacted after a period. - TMM instances may restart.
This issue arises only when all the following conditions occur: - Hardware is chassis type. - There is more than one blade in service. - A fastL4 profile is configured (e.g., using bigproto). - SessionDB is used either by iRules or by native profile functionality.
None.
SessionDB-related accesses initiated via iRules are now properly cleaned up and no longer hang.