Cisco Bug: CSCum65037 - UMMT - Route-map cmd [set ip next-hop peer-address] not seen in configs
Jan 29, 2017
- Cisco ASR 900 Series Aggregation Services Routers
Known Affected Releases
Symptom: [set ip next-hop peer-address] CLI configured within a route-map won't appear in running-configs. Hence the configuration is lost across reload. Note that the intended functionality of the command works fine as per the expectation, but the functionality would be lost after reboot until the user reconfigures it again. Conditions: In Unified MPLS for Mobile transport model with IGP-LDP Access, IGP routes (mainly CSG loopbacks) from Access ring would be redistributed into BGP in the Pre-Aggregation device (ASR903). When this happens, IGP nexthops that are directly connected to the Pre-Aggregation devices are treated as BGP nexthops in the local BGP database of the pre-aggregation device. Hence when the corresponding link goes down, there might be unnecessary BGP nexthop scan for AF IPv4 taking place. To avoid this, user need to configure [set ip next-hop peer-address] in the route-map used to redistribute IGP routes into BGP.. With this configuration, NH for the redistributed IGP routes (CSG loopbacks) would be stored as 0.0.0.0 in local database and hence if the directly connected interface goes down, BGP nexthop scan for AF IPv4 won't be triggered. Note: This command is used to make sure BGP NH's would be 0.0.0.0 for the redistributed IGP routes (CSG loopbacks) into BGP. For the same IGP routes reflected to ABR's in BGP, Pre-Aggregation devices would anyway change the NH to it's own loopback IP address as required in UMMT design and this command has no role to play for those reflected BGP routes.
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