Cisco Bug: CSCus74979 - lower-ip-precedence not working when data packet exceeds CIR
May 22, 2017
- Cisco ASR 5000 Series
Known Affected Releases
This was the behaviour change for non-gbr bearer for commited data rate policy application. Symptom: When "committed-data-rate" cli is configured in charging action for non-gbr bearer with exceed-action lower-ip-precedence, ToS value for packet was not getting modified. flow limit-for-bandwidth direction uplink peak-data-rate 75000000 peak-burst-size 14062500 violate-action discard committed-data-rate 88000 committed-burst-size 16500 exceed-action lower-ip-precedence Conditions: packets coming to non-gbr bearer and matching to charging action having "committed-data-rate" cli configured , In this case exceed action configured for "committed-data-rate" wont get applied.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases