05-03-2016 02:10 AM
Hi,
The following topology:
R6 <---eBGP ---> R4 <---iBGP---> R5 <---iBGP---> R8
R6:
R4:
R5:
R8:
The issue is, that the prefix 6.6.6.6/32 isn't advertised on R5 towards R8, although it is best. The 10.5.5.5/32 is advertised.
R5 configuration:
router bgp 458
bgp cluster-id 5
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 150.1.8.8 remote-as 458
neighbor 150.1.8.8 update-source Loopback0
!
address-family ipv4
exit-address-family
!
address-family vpnv4
neighbor 150.1.8.8 activate
neighbor 150.1.8.8 send-community extended
exit-address-family
!
address-family ipv4 vrf a
network 10.5.5.5 mask 255.255.255.255
neighbor 155.1.45.4 remote-as 458
neighbor 155.1.45.4 activate
neighbor 155.1.45.4 route-reflector-client
exit-address-family
R8 Configuration:
router bgp 458
bgp cluster-id 458
bgp log-neighbor-changes
neighbor 150.1.5.5 remote-as 458
neighbor 150.1.5.5 update-source Loopback0
!
address-family vpnv4
neighbor 150.1.5.5 activate
neighbor 150.1.5.5 send-community extended
neighbor 150.1.5.5 route-reflector-client
exit-address-family
R5#sh bgp vpnv4 u all 6.6.6.6/32
BGP routing table entry for 5.5.5.5:10:6.6.6.6/32, version 2
Paths: (1 available, best #1, table a)
Not advertised to any peer
Refresh Epoch 1
6, (Received from a RR-client)
155.1.45.4 (via vrf a) from 155.1.45.4 (150.1.4.4)
Origin IGP, metric 0, localpref 100, valid, internal, best
Extended Community: RT:458:10
mpls labels in/out 18/nolabel
rx pathid: 0, tx pathid: 0x0
R5#
I did find out however that if I create a route-map on R5 and set ip next-hop to R5s update-source (not self), the prefix does get advertised.
route-map rm2r8 permit 10
set ip next-hop 150.1.5.5
router bgp 458
add vpnv4
neighbor 150.1.8.8 route-map rm2r8 out
R5#sh bgp vpnv4 u all 6.6.6.6/32
BGP routing table entry for 5.5.5.5:10:6.6.6.6/32, version 2
Paths: (1 available, best #1, table a)
Advertised to update-groups:
20
Refresh Epoch 1
6, (Received from a RR-client)
155.1.45.4 (via vrf a) from 155.1.45.4 (150.1.4.4)
Origin IGP, metric 0, localpref 100, valid, internal, best
Extended Community: RT:458:10
mpls labels in/out 18/nolabel
rx pathid: 0, tx pathid: 0x0
R5#
R5#sh bgp vpnv4 u all nei 150.1.8.8 adv
BGP table version is 4, local router ID is 150.1.5.5
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 5.5.5.5:10 (default for vrf a)
*>i 6.6.6.6/32 155.1.45.4 0 100 0 6 i
*> 10.5.5.5/32 0.0.0.0 0 32768 i
Total number of prefixes 2
R5#
I wasn't able to find any information on this scenario in Cisco Docs.
Thanks.
/JZ
Solved! Go to Solution.
05-03-2016 06:34 AM
Hi,
iBGP may not be supported as PE-CE protocol. Please see below doc. You may try to "configure neighbor ip-address internal-vpn-client"
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-l3vpn-ibgp-pe-ce.html
Regards,
Akash
05-03-2016 06:34 AM
Hi,
iBGP may not be supported as PE-CE protocol. Please see below doc. You may try to "configure neighbor ip-address internal-vpn-client"
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/15-s/irg-15-s-book/irg-l3vpn-ibgp-pe-ce.html
Regards,
Akash
05-03-2016 10:40 AM
Hi Akash,
This was exactly what I was looking for.
Thanks a lot.
Regards,
/JZ
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide