Bug ID 503343: TMM crashes when cloned packet incorrectly marked for TSO

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.2, 11.5.3, 11.6.0, 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.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6, 11.5.4, 11.4.1 HF9

Opened: Jan 28, 2015

Severity: 2-Critical

Symptoms

TMM cores

Impact

Traffic disrupted while tmm restarts.

Conditions

1. Clone pool configured 2. Clone MTU > Client or Server MTU 3. tm.tcpsegmentationoffload db var in "disable" state 4. TSO enabled in client or server side interface 5. TSO disabled in clone interface

Workaround

Remove the configured clone pool

Fix Information

Prevent TMM crash due to cloned packet incorrectly marked for TSO.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips