Bug ID 489153: TMM may incorrectly log compression limit has been exceeded

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
10.2.4, 11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4

Fixed In:
12.0.0

Opened: Nov 06, 2014
Severity: 5-Cosmetic

Symptoms

The log entry similar to the following appears in /var/log/ltm: Nov 6 13:33:26 6900s-2 err tmm1[15040]: 01240011:3: Compression license limit of 50 Mbit/s exceeded today.

Impact

Unexpected log entry

Conditions

This can occur once the following conditions have been met: 1. Compression limit has been exceeded in past 24 hours 2. Add-on license for unlimited compression limit has been installed

Workaround

None

Fix Information

The TMM will reset its compression limit exceeded state upon increasing the licensed compression limit.

Behavior Change