Bug ID 527016: CLASSIFICATION_DETECTED irule event results in tmm core

Last Modified: May 29, 2024

Affected Product(s):
BIG-IP All(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, 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

Opened: Jun 08, 2015

Severity: 2-Critical

Symptoms

If an irule script which uses the CLASSIFICATION_DETECTED is used, then it may result in a tmm core.

Impact

Traffic disrupted while tmm restarts.

Conditions

Configure an ltm irule with CLASSIFICATION_DETECTED event, and the body of the script contains atleast one irule command that runs asynchronously.

Workaround

None

Fix Information

Using the CLASSIFICATION_DETECTED irule event does not cause tmm to core.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips