Cisco Bug: CSCvu55422 - QoS not working with BGP/QPPB
Jun 10, 2020
- Cisco 1900 Series Integrated Services Routers
Known Affected Releases
Symptom: The BGP feature is marking the QOS group only after the CCE is done with its classifications since the CCE feature is called before the BGP feature in input feature path. From #sh cef int g0/1 we see 'Input features: CCE Input Classification, Ingress-NetFlow, BGP Policy Map, QoS Marking' then ' IP_FEATURE_IN_CCE_FIRST_CLASSIFY,' then ' IP_FEATURE_IN_BGP_POLICY_MAP,' so that shows the process of how marking is done. Conditions: Latest versions on ISRG2 : Version 15.7(3)M5, RELEASE SOFTWARE (fc1) The reason why the packets are not being matched against qos-group 10 is the below : CGB-BG-BUR-IP-DIA-01-R-1#show ip route 10.145.0.0 Routing entry for 10.145.0.0/16 Known via "bgp 64535", distance 20, metric 0 Tag 65001, qos-group 10, type external <<<< from routing perspective qos-group 10 already matched here / sit Last update from 10.91.66.8 12:49:14 ago Routing Descriptor Blocks: * 10.91.66.8, from 10.91.66.253, 12:49:14 ago Route metric is 0, traffic share count is 1 AS Hops 2 Route tag 65001 MPLS label: none Router(config-if)# bgp-policy destination ip-qos-map Router(config-if)#do sh cef int gig0/2 Input features: CCE Input Classification, BGP Policy Map, QoS Marking <<< CCE classification still happening before the bgp policy map and The BGP feature is marking the QOS group only after the CCE is done with its classifications since the CCE feature is called before the BGP feature in input feature path This is considered a type of limitation in ISRG2 platforms ( 1900 , 2900 , 3900 , .. ) running 15.x releases. Now, on the 12 train issue is not the same because the marking is done differently as the architecture of the train differs than the 15 therefore since marking is different it is doing its job as needed. it's a limitation with CCE DP and BGP policy in input direction.
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