10-10-2014 02:13 PM
I have another concept question. I have an MPLS network with 2 customers labbed up in GNS3. (see attached diagram) GETVPN encryption services set up for one- everything is running perfect. My question, how would I be able to distribute a default route on a PE, to say an ISP router, to the 2 configured customer vrfs. Here's what I tried so far.
I created a vrf called isp on PE-R7- put the interface connecting to the ISP router in the isp vrf- ips are 137.137.137.x.
Created default route in the isp vrf. Created route target export value of 137:137 for the ipv4 af (address family) of the isp vrf
Imported that route target on the pizza vrf ipv4 af (just the one customer for now)
Added redistribute static and default-information originate to the BGP ipv4 af for vrf isp
Did not touch the other PEs since I'm getting nowhere with the one.
I do not even see the default route when I issue PE-R7#show ip route vrf isp just the connected network
And as expected, it's certainly not found in the vpnv4 af of the BGP tables PE-R7#show ip bgp all
So, there's no way it can be can be distributed if doesn't even make the local router BGP tables to begin with
Am I on the right track with this? Below is the config for PE-R7 Thanks in advance everybody....Dennis
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
!
hostname PE-R7
!
boot-start-marker
boot-end-marker
!
!
vrf definition dtech
rd 120:120
!
address-family ipv4
route-target export 30:30
route-target import 20:20
route-target import 40:40
exit-address-family
!
vrf definition isp
rd 137:137
!
address-family ipv4
route-target export 137:137
exit-address-family
!
vrf definition pizza
rd 121:121
!
address-family ipv4
route-target export 31:31
route-target import 21:21
route-target import 137:137
exit-address-family
!
!
no aaa new-model
!
no ip domain lookup
ip domain name lab.local
ip cef
no ipv6 cef
!
!
multilink bundle-name authenticated
!
interface Loopback0
ip address 7.7.7.7 255.255.255.255
!
interface FastEthernet0/0
ip address 10.0.57.7 255.255.255.0
speed auto
duplex auto
mpls ip
!
interface FastEthernet0/1
ip address 10.0.67.7 255.255.255.0
speed auto
duplex auto
mpls ip
!
interface FastEthernet1/0
vrf forwarding dtech
ip address 192.168.78.7 255.255.255.0
speed auto
duplex auto
!
interface FastEthernet1/1
vrf forwarding pizza
ip address 192.168.71.7 255.255.255.0
speed auto
duplex auto
!
interface FastEthernet2/0
vrf forwarding isp
ip address 137.137.137.7 255.255.255.0
speed auto
duplex auto
!
interface FastEthernet2/1
no ip address
shutdown
speed auto
duplex auto
!
!
router eigrp 7
!
address-family ipv4 vrf dtech
redistribute bgp 27 metric 1 1 1 1 1
network 0.0.0.0
autonomous-system 8
exit-address-family
!
address-family ipv4 vrf pizza
redistribute bgp 27 metric 1 1 1 1 1
network 0.0.0.0
autonomous-system 10
exit-address-family
!
router ospf 1
network 7.7.7.7 0.0.0.0 area 0
network 10.0.0.0 0.0.255.255 area 0
!
router bgp 27
bgp log-neighbor-changes
neighbor 2.2.2.2 remote-as 27
neighbor 2.2.2.2 update-source Loopback0
neighbor 11.11.11.11 remote-as 27
neighbor 11.11.11.11 update-source Loopback0
!
address-family ipv4
neighbor 2.2.2.2 activate
neighbor 11.11.11.11 activate
exit-address-family
!
address-family vpnv4
neighbor 2.2.2.2 activate
neighbor 2.2.2.2 send-community extended
neighbor 11.11.11.11 activate
neighbor 11.11.11.11 send-community extended
exit-address-family
!
address-family ipv4 vrf dtech
redistribute eigrp 8
exit-address-family
!
address-family ipv4 vrf isp
redistribute static
default-information originate
exit-address-family
!
address-family ipv4 vrf pizza
redistribute eigrp 10
exit-address-family
!
ip forward-protocol nd
!
!
no ip http server
no ip http secure-server
ip route vrf isp 0.0.0.0 0.0.0.0 137.13.137.13
!
control-plane
!
!
line con 0
exec-timeout 0 0
privilege level 15
logging synchronous
stopbits 1
line aux 0
exec-timeout 0 0
privilege level 15
logging synchronous
stopbits 1
line vty 0 4
login
!
!
end
Solved! Go to Solution.
10-13-2014 02:32 AM
The problem for the lokal router (PE7) is that the next hop is not known. And therefor not showing up in the routing table.
It seems that it can be just a typo, next hop is set to 137.13.137.13,maybe it should be 137.137.137.13.
For the other PE to install the route ( when PE7 starts to distribute it) they also have to know about the next hop network 137.137.137.0. Or You can set next-hop-self in the bgp
/Mikael
10-13-2014 02:32 AM
The problem for the lokal router (PE7) is that the next hop is not known. And therefor not showing up in the routing table.
It seems that it can be just a typo, next hop is set to 137.13.137.13,maybe it should be 137.137.137.13.
For the other PE to install the route ( when PE7 starts to distribute it) they also have to know about the next hop network 137.137.137.0. Or You can set next-hop-self in the bgp
/Mikael
10-19-2014 06:51 AM
Geez! Tired eyes! Thanks for the response on my oversight- here's my lab set up should anyone be interested.....thanks again!
http://techjuice.blogspot.com/2014/10/mpls3-with-getvpn.html
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