Bug ID 565810: OneConnect profile with an idle or strict limit-type might lead to tmm core.

Last Modified: Feb 13, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
11.2.1, 11.4.1, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 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, 12.0.0, 12.0.0 HF1, 12.0.0 HF2

Fixed In:
12.1.0, 12.0.0 HF3, 11.6.1, 11.5.4 HF2

Opened: Jan 06, 2016
Severity: 2-Critical
Related AskF5 Article:
K93065637

Symptoms

OneConnect profile with an idle or strict limit-type might lead to tmm core.

Impact

Traffic disrupted while tmm restarts.

Conditions

OneConnect profile with a limit-type value of idle or strict.

Workaround

Use a limit-type of 'none'.

Fix Information

A OneConnect profile using an idle or strict limit-type no longer causes the tmm to core when attempting to shutdown idle connections.

Behavior Change