Bug ID 484013: tmm might crash under load when logging profile is used with packet classification

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
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.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

Fixed In:
12.0.0, 11.6.1 HF1, 11.5.1 HF6

Opened: Oct 11, 2014
Severity: 2-Critical
Related Article:
K12435402

Symptoms

When tmm is under heavy load it may run out of memory and crash under certain conditions.

Impact

Traffic disrupted while tmm restarts.

Conditions

This occurs when the following conditions are met: 1. Packet classification is enabled 2. Security logging profile is used with 'log translation fields' option enabled. 3. Fast flow forwarding is enabled on forwarding virtual server.

Workaround

To work around this, do one of the following: -- Disable 'log translation fields' in the security logging profile. -- Disable fast flow forwarding.

Fix Information

This fixes a memory leak when TMM is overloaded and forwards flows to the peer, and packet classification is enabled with 'log translation fields' in the logging profile.

Behavior Change