Wednesday, September 23, 2009

Lab 18... issues... twice.

I did lab 18, twice and ended up with the same problem. The first time I did it, I did it on my own. The second time, I followed the Proctor Guide.

Task 18.9 - I'm supposed to configure MP-eBGP between two ASes and then use BGP to send-labels. I configured it, just the same as the proctor guide but I can't get my the eBGP peer routers to see the VPNV4 bgp prefixes advertised in their respective ASes.

So if R2, R1 and R5 are in AS 125 and R5 eBGP peers with R6 in AS 689 (with routers R8 and R9 in AS689), and R2 is peering with a CE, receiving VPNV4 routes after redistribution and R1 is seeing it and advertising to R5, why isn't R5 able to see the VPNV4 routes in its own AS? Plus why can't I configure BGP soft-reconfiguration inbound in address-family vpnv4... I want to see what routes are being received by R5's VPNV4...


For those interested here's R5's config:

!
router ospf 1
log-adjacency-changes
network 150.50.15.5 0.0.0.0 area 0
network 200.0.0.5 0.0.0.0 area 0
!
router bgp 125
no bgp default ipv4-unicast
bgp log-neighbor-changes
neighbor 150.50.56.2 remote-as 689
neighbor 200.0.0.1 remote-as 125
neighbor 200.0.0.1 update-source Loopback0
!
address-family ipv4
neighbor 150.50.56.2 activate
neighbor 150.50.56.2 send-label
neighbor 200.0.0.1 activate
neighbor 200.0.0.1 next-hop-self
neighbor 200.0.0.1 send-label
no auto-summary
no synchronization
exit-address-family
!
address-family vpnv4
neighbor 200.0.0.1 activate
neighbor 200.0.0.1 send-community extended
exit-address-family
!


R5#sh ip bgp vpnv4 all s
BGP router identifier 200.0.0.5, local AS number 125
BGP table version is 1, main routing table version 1

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
200.0.0.1 4 125 261 224 1 0 0 00:39:35 0
R5#


******************R1*****************************
R1#sh ip bgp vpnv4 all neighbors 200.0.0.5 advertised-routes
BGP table version is 29, local router ID is 200.0.0.1
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 125:100
*>i150.50.24.0/30 200.0.0.2 0 100 0 ?
*>i200.0.0.4/32 200.0.0.2 1 100 0 ?

Total number of prefixes 2

R1#sh ip bgp vpnv4 all s
BGP router identifier 200.0.0.1, local AS number 125
BGP table version is 29, main routing table version 29
2 network entries using 312 bytes of memory
2 path entries using 136 bytes of memory
6/2 BGP path/bestpath attribute entries using 888 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
1 BGP extended community entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
Bitfield cache entries: current 1 (at peak 4) using 32 bytes of memory
BGP using 1416 total bytes of memory
BGP activity 12/6 prefixes, 26/20 paths, scan interval 15 secs

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
200.0.0.2 4 125 233 257 29 0 0 00:53:21 2
200.0.0.5 4 125 229 266 29 0 0 00:44:51 0
200.0.0.9 4 689 17 17 0 0 0 00:50:58 Active
R1#

**********************************************************
R1 showing it received VPNV4 routes from R2 and advertising it to R5 (R1 is a RR).