Brad, Peer VPNv4 between loopbacks of the PEs. If you don't peer between loopbacks, the next-hop (igp) label gets popped of too early and you have a VPN label exposed to a P router.
Also, the Core central router doesn't need BGP...that's part of the beauty of it :) On Fri, Nov 20, 2009 at 10:48 PM, Brad Edgeworth <[email protected]>wrote: > 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 > > -- Bryan Bartik CCIE #23707 (R&S, SP), CCNP Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
