Cisco Bug: CSCtf19115 - IBGP next hop self on RRs for IPv4/IPv6
Feb 02, 2017
- Cisco IOS
Known Affected Releases
12.2(32.0.8)SRE 12.2REC 15.1(1)S
Symptom:Currently configuring next-hop-self at RR only updates the nexthop of eBGP routes. This enhancement updates the behavior so that next-hop of iBGP routes can be updated as well via new keyword "all" [no] neighbor <address> next-hop-self [all] Conditions:Two scenarios this feature is helpful and asked by customers: 1) To provide a mechanism to scale large MPLS networks: If you are reflecting 3107 prefixes across area to core boundary, you may want to set next-hop-self on the ABR (which is enabled with RR functionality) so that local label allocated and LSPs are terminated at that point. Otherwise, you will have to propagate a lot of state edge to edge all over the network. 2) 6PE case: Today only eBGP to iBGP 6PE case supported. This feature has been request for iBGP to iBGP 6PE case. If you are connecting the areas supporting v6 but core does not support v6, you tunnel v6 through the core which is ipv4 only. In this case, 6PE is ABR doing iBGP route reflection, i.e. RR.
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