Bug ID 2224749: The db key dos.blleaklimit doesnt have any impact

Last Modified: Feb 19, 2026

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

Known Affected Versions:
17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.1.2.2, 17.1.3, 17.1.3.1

Opened: Feb 16, 2026

Severity: 3-Major

Symptoms

For more information see https://community.f5.com/kb/technicalarticles/ip-intelligence-and-ip-shunning/286783 By default, every 256th packet goes into software when logging is set to “limited”. This is controlled by the sys db variable “dos.blleaklimit”. You can modify it to values like 1, 3, 7, 15, 31, 63, 127, 255, 511, 1023, and so on. The default value is 255. Currently, only the default value of 255 is working.

Impact

No functional impact but you are unable to control the hardware drop rate using "dos.blleaklimit"

Conditions

-- AFM Provisioned -- IPI licensed -- IPI policy created -- Set the logging to “Limited” -- Hardware appliances support.

Workaround

None

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips