Cisco Bug: CSCtc33679 - PIRO: prefixes donot go into INPOLICY due to exit mismatch
Feb 03, 2017
- Cisco ASR 1000 Series Aggregation Services Routers
Known Affected Releases
12.2XN 12.4(24)T3 15.0(1)M2 15.1(1)T1
Symptoms: Routes are not being controlled properly when PIRO is used. Conditions: If more than one exit per BR is configured and PIRO is used to control the routes, the nexthop is not being calculated correctly. As a result, traffic for these traffic classes is not taking the correct route.
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