Bug ID 508100: Bandwidth not limited by max category rate when sum of category rates lesser than max user rate in traffic priority groups

Last Modified: Oct 24, 2019

Bug Tracker

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

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1

Opened: Feb 20, 2015
Severity: 4-Minor

Symptoms

Categories in BWC policy with traffic priority groups can be configured with sum of maximum category rates lesser than the maximum user rate. The goal for per-subscriber traffic prioritization is to provide weighted bandwidth allocation when a subscriber limit is reached. The prioritization of traffic is applied when the network congestion is detected.

Impact

An invalid configuration is added without warning or error.

Conditions

Occurs when categories in BWC policy with traffic priority groups are configured with sum of maximum category rates lesser than the maximum user rate.

Workaround

Configure categories in BWC policy with traffic priority groups such that the sum of maximum category rates is greater than or equal to maximum user rate.

Fix Information

None

Behavior Change