Hi Brad,
As it can be seen your VPNV4 peering is like this R1Core (PE) <– >CoreCentral 
<– >R2Core (PE).
Therefore R1 has a peering to Core with iBGP and VPNV4 is activated. Good R1 
has a knowledge of VRF and it can import and export the respective VPNV4 
addresses to vrf but that is not true for Rcore.
 
The other thing is the core has a iBGP peerings with both routers so it will 
not pass the route that it got from one to another. Even if you can solve this 
issue with route reflector or confederation, you have to work around to get the 
VPNV4 traffic around. May be you have to configure the Core with vrf ....
 
The best way is to peer the two PE routers directly.
The other thing is it is not a must to peer with loopbacks
 
Best Regards,
 
Solomon




________________________________
From: Brad Edgeworth <[email protected]>
To: "[email protected]" <[email protected]>
Sent: Sat, November 21, 2009 8:48:52 AM
Subject: [OSL | CCIE_RS] Need help with L3 MPLS


So I’m trying to practice MPLS L3 VPN with routing OSPF across it.   I’m having 
difficulties with my connectivity from one CE device to the other CE device.   
Before I started I had plain MPLS working on a flat network end to end.   I’m 
successful with getting my OSPF routes across the cloud but need help figuring 
out why packets won’t travel.   Can someone find what I’m missing?
 
-brad
 
 
 
Setup is straightforward:    R1 (CE) – R1Core (PE) – CoreCentral – R2Core (PE) 
– R2 (CE)
                                                                10.x.x.x 
subnets are data networks for the CE
                                                                192.168.x.x 
subnets are the provider network
 
Routing portion of the configs listed below:
 
**R1Core
router ospf 100 vrf BRAD
 domain-id 0.0.0.1
 log-adjacency-changes
 redistribute bgp 100 subnets
 network 10.32.0.0 0.0.255.255 area 1
router ospf 1
 log-adjacency-changes
 network 172.0.0.0 0.255.255.255 area 1
 network 192.168.0.0 0.0.255.255 area 0
router bgp 100
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 192.168.1.254 remote-as 100
 !
 address-family vpnv4
  neighbor 192.168.1.254 activate
  neighbor 192.168.1.254 send-community both
 exit-address-family
 !
 address-family ipv4 vrf BRAD
  redistribute connected
  redistribute ospf 100 vrf BRAD
  no synchronization
 exit-address-family
 
 
**** CoreCentral
router ospf 1
 mpls ldp autoconfig
 log-adjacency-changes
 network 0.0.0.0 255.255.255.255 area 0
router bgp 100
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 192.168.1.1 remote-as 100
 neighbor 192.168.2.1 remote-as 100
!
 address-family vpnv4
  neighbor 192.168.1.1 activate
  neighbor 192.168.1.1 send-community extended
  neighbor 192.168.1.1 route-reflector-client
  neighbor 192.168.2.1 activate
  neighbor 192.168.2.1 send-community extended
  neighbor 192.168.2.1 route-reflector-client
exit-address-family
 
 
**R2Core
router ospf 100 vrf BRAD
 domain-id 0.0.0.2
 log-adjacency-changes
 redistribute bgp 100 subnets
 network 10.64.0.0 0.0.255.255 area 2
router ospf 1
 log-adjacency-changes
 network 172.0.0.0 0.255.255.255 area 2
 network 192.168.0.0 0.0.255.255 area 0
router bgp 100
 no bgp default ipv4-unicast
 bgp log-neighbor-changes
 neighbor 192.168.2.254 remote-as 100
 !
 address-family vpnv4
  neighbor 192.168.2.254 activate
  neighbor 192.168.2.254 send-community both
 exit-address-family
 !
 address-family ipv4 vrf BRAD
  redistribute connected
  redistribute ospf 100 vrf BRAD
  no synchronization
 exit-address-family



      
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Reply via email to