Bug ID 503875: Configure bwc policy category max rate

Last Modified: Sep 13, 2023

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

Opened: Jan 30, 2015

Severity: 3-Major

Related Article: K81433151

Symptoms

When category max rate percentage is configured with a low value, for example, a lower value relative to the policy max user rate, some packets might be dropped.

Impact

The packets in flows using the bwc policy and category may be dropped, the flows mapped to the category might not be able to pass packets.

Conditions

The bwc policy is configured as dynamic, with categories. And the category max rate is configured to low value when the policy is being provisioned and mapped to traffic flows.

Workaround

Configure category rate in absolute value and higher value relative to policy max user rate.

Fix Information

Category max rate percentage is now configured to ensure valid settings.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips