Last Modified: Feb 28, 2025
Affected Product(s):
BIG-IP TMOS
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4
Fixed In:
17.5.0, 17.1.2
Opened: Apr 05, 2024
Severity: 4-Minor
Currently existing tm.egressdscp db variable does not provide enough flexibility in configuring Quality of Service (QoS), as it applies to all egress TMM connections (including monitor traffic and other protocols). Add an option to QoS mark egress BGP packets, to apply a QoS marking to BGP packets as they leave a router.
No impact
- Configuring QoS.
None
Added a new db variable TM.BGPEgressDscp controlling DSCP value of egress BGP packets. Default is 0 (zero). A BGP session restart is required. Following is an example: root@(bigip1)(cfg-sync Standalone)(Active)(/Common)(tmos)# list sys db tm.bgpegressdscp sys db tm.bgpegressdscp { value "42" }