Last Modified: May 14, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 12.1.4, 22.214.171.124
Opened: Mar 20, 2017
Related AskF5 Article: K50325308
When category is set at lower rate than 100% of the user rate, and traffic going through the category is non-TCP, and the amount of data is 150% of the instance rate, then that can create policy to be active, lowering the overall bandwidth.
BWC dynamic policy cannot achieve 100% of max-rate.
This occurs when all of the following conditions are met: -- Category rate is less than max-user-rate -- Traffic is non-TCP data. -- Amount of data passing is 150% of max-user-rate.
Increase the max-rate of any dynamic policy, and add an additional static policy set to the max-rate expected from the dynamic policy. Note: There is no actual fix for this issue except for not using UDP traffic in categories, if the amount of traffic on that UDP category is expected to exceed 150%, or over to the maximum fair rate provided by the BWC instance. Note that the PEM subscriber and BWC instance have 1-1 relationship.