Bug ID 737344: VE rate shaper warnings might not be issued as expected

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
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.4, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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,,,,,,,, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 14.0.0,,,,, 14.1.0,,,

Opened: Jul 18, 2018
Severity: 3-Major


By default, BIG-IP Virtual Edition (VE) rate shaper warnings can be issued at 75% of the threshold. The rate shaper logic is implemented per-TMM, but the threshold-warning logic is based on all TMMs. Because no warning is issued unless the entire system is over the threshold, it is possible that an individual TMM might be over the threshold but have no warning issued.


No warning is logged, even though it might be expected. This makes it difficult to know when a deployment is close to reaching its licensed capacity if it has bursty traffic or uneven distribution of connections across TMMs.


-- Rate shaper warnings configured to be issued at 75% of the threshold. -- System with N TMMs and licensed for X megabits-per-second (results in a per-tmm threshold of approximately X/N). -- One TMM has more than 0.75*X/N of traffic, but the entire system is processing less than 0.75*N.



Fix Information


Behavior Change