Bug ID 784549: Heavy CPU usage by TMM in configurations with traffic-matching-criteria

Last Modified: Jul 23, 2021

Bug Tracker

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

Known Affected Versions:
14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 16.0.0, 16.0.0.1, 16.0.1, 16.0.1.1, 16.0.1.2, 16.1.0

Opened: May 21, 2019
Severity: 3-Major

Symptoms

The Traffic Management Microkernel (TMM) processes appears very busy, imposing a heavy load on the even-numbered CPUs, in the absence of heavy network traffic or other obvious sources of workload.

Impact

CPU load is unreasonably high, which limits the amount of traffic the BIG-IP system can handle. The heavy CPU load may slow other processing, with a variety of impacts, ranging from slow user-interface response to constant restarts of processes by the sod daemon.

Conditions

-- At least one virtual server is configured using the 'traffic-matching-criteria' feature, with lists of either addresses or ports.

Workaround

None.

Fix Information

None

Behavior Change