Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 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.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 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
Fixed In:
13.1.0
Opened: Feb 05, 2016
Severity: 5-Cosmetic
The default values for a drop policy's elements max-threshold and min-threshold may show as '0' under certain circumstances, and their actual values under other circumstances. This can actually lead to the values being displayed differently between configsync devices despite the traffic group showing in-sync (internally, the actual non-zero default value is always used, and so no config mismatch is detected). This leads to confusion.
Confusion when you see the change in value from zero to something else when you change one value and see other value automatically changed.
This occurs when using rate-shaping drop policies.
No work around is needed.
Ignore the parameter values when rate shaper drop policy changes automatically to the default value.
