Bug ID 676982: Active connection count increases over time, long after connections expire

Last Modified: Dec 11, 2018

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, 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 AskF5 Article:
K21958352

Symptoms

- Number of active connections is increasing over time. - Memory used by TMM increases over time. - Potential TMM restart is possible.

Impact

- Service may be impacted after a period. - TMM instances may restart.

Conditions

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.

Workaround

None.

Fix Information

SessionDB-related accesses initiated via iRules are now properly cleaned up and no longer hang.

Behavior Change