cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4882
Views
0
Helpful
7
Replies

Unable to advertise static routes via MP BGP to PE routers

Dennis Topo Jr
Level 1
Level 1

Hello all. I'm having an issue advertising the transit networks between the P and PE routers via this labbed MPLS\MP BGP network. My attempt was to achieve end to end connectivity via BGP-using an different EBGP AS for each site- and IBGP among the P and PE routers- no other redistributed IGPs between the CE and PE routers such as in this example (a lab I posted a while back):

http://techjuice.blogspot.com/2014/10/mpls3-with-getvpn.html

 

Anyway, I'm able to exchange routes advertised by the CE's just fine. But those 2 transit routes- I can't seem to get into the BGP table.

I added a VRF called SHARED- and redistributed the static routes on each PE into that VRFs ipv4 address family, and imported the route target values into the TGI VRF- but still won't show up. Not sure what I am missing now. I realize this isn't the optimal config, such as not using loopbacks for my neighbors etc...but just trying to prove out a concept here. Below the diagram is the relevant part of my config- and below that is the BGP table of PE-R8

Appreciate any insight ! Thanks....Dennis

 

 

 

PE-R8  (PE-R9 is a similar "mirrored" config)

 

*note- there is no interface is "in" the SHARE vrf, if that matters. I simply wanted to use it as a "container" to import from. I tried redistributing the static routes directly into the TGI vrf too...but same result- no routes in BGP 

 

ip vrf SHARE                   

rd 130:130

route-target export 30:30

route-target import 30:30

!

ip vrf TGI

rd 120:120

route-target export 20:20

route-target import 20:20

route-target import 30:30

 

 

address-family ipv4 vrf SHARE

redistribute static

default-information originate

exit-address-family

 

 

router bgp 65000

bgp router-id 152.177.58.142

bgp log-neighbor-changes

neighbor 152.177.58.145 remote-as 65000

!

address-family ipv4

neighbor 152.177.58.145 activate

exit-address-family

!

address-family vpnv4

neighbor 152.177.58.145 activate

neighbor 152.177.58.145 send-community both

exit-address-family

 

 

ip route 152.177.58.144 255.255.255.252 152.177.58.141  

 

BGP Address family on PE-R8    (no 152.177.58.144 network!)

 

PE-R8#show ip bgp all
For address family: IPv4 Unicast

For address family: VPNv4 Unicast

     Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 120:120 (default for vrf TGI)
 *>  10.7.1.0/24         152.177.58.138           0             0 65002 i
 *>i 10.24.20.0/22     152.177.58.145           0    100      0 65001 i
 *>i 51.64.56.252/30  152.177.58.145           0    100      0 65001 i
 *>i 130.148.200.126/32
                                   152.177.58.145           0    100      0 65001 i
 *>i 152.177.58.132/30
                                   152.177.58.145           0    100      0 65001 i
 r>  152.177.58.136/30
                                     152.177.58.138           0             0 65002 i

 

1 Accepted Solution

Accepted Solutions

Hi Dennis,

 

To make your global route visible in any vrf, you have to have this route in your BGPv4 table.

 

View solution in original post

7 Replies 7

Ugur Ersoy
Level 1
Level 1

you static route is located in global routing table but you do redistribution under vrf Share route table. 

 

do redistribution under address family ipv4 or write your static route as ip route vrf share ....

Thanks for the reply Ugur....

Ahh-- tried adding the static to the vrf share - but same results-the routes don;t show up in the vpnv4 TGI table (I kept the global one also since it's needed for my neighborships) I thought for certain that was it! :(

 

ip route 152.177.58.144 255.255.255.252 152.177.58.141

ip route vrf SHARE 152.177.58.144 255.255.255.252 152.177.58.141

 

 And Redistributing under ipv4 address family won't help me either, right?-- as I want these routes to ultimately end up in the vpnv4 TGI vrf table.....  

Ok...shooting from the hip now.......I added the static route to both vrfs and redistribute static- I would think something should give some results here- but no! Still not getting those routes in the table. What am I missing? 

ip route 152.177.58.144 255.255.255.252 152.177.58.141
ip route vrf SHARE 152.177.58.144 255.255.255.252 152.177.58.141
ip route vrf TGI 152.177.58.144 255.255.255.252 152.177.58.141

 

address-family ipv4 vrf SHARE
  redistribute static
  default-information originate
 exit-address-family
 !
 address-family ipv4 vrf TGI
  redistribute static
  neighbor 152.177.58.138 remote-as 65002
  neighbor 152.177.58.138 activate
  default-information originate
 exit-address-family

 

 

 

update:

I scrapped the redistribute static....used loopbacks for my PE neighborships.....8.8.8.8 and 9.9.9.9 for PE-R8 and 9 respectively

 

and tried this:

 

ip route 9.9.9.9 255.255.255.255 152.177.58.141
ip route 152.177.58.144 255.255.255.252 152.177.58.141
!
!
ip prefix-list IMPORT_STATIC seq 5 permit 152.177.58.144/30
!
route-map IMPORT_STATIC_MAP permit 10
 match ip address prefix-list IMPORT_STATIC

 

ip vrf TGI
 rd 120:120
 import ipv4 unicast map IMPORT_STATIC_MAP
 route-target export 20:20
 route-target import 20:20

For address family: VPNv4 Unicast

     Network          Next Hop            Metric LocPrf Weight Path
Route Distinguisher: 120:120 (default for vrf TGI)
Import Map: IMPORT_STATIC_MAP, Address-Family: IPv4 Unicast, Pfx Count/Limit: 0/1000
 *>  10.7.1.0/24         152.177.58.138     0             0 65002 i
 *>i 10.24.20.0/22      9.9.9.9                  0    100      0 65001 i
 *>i 51.64.56.252/30  9.9.9.9                  0    100      0 65001 i
 *>i 130.148.200.126/32
                       9.9.9.9                             0    100      0 65001 i
 *>i 152.177.58.132/30
                       9.9.9.9                             0    100      0 65001 i
 r>  152.177.58.136/30
                       152.177.58.138               0             0 65002 i

 

Still cannot get a static route into the VPNv4 unicast table for vrf TGI as shown above

 

Hi Dennis,

 

To make your global route visible in any vrf, you have to have this route in your BGPv4 table.

 

Ugur- thanks for looking more into this. Yes- I realized this too...lesson learned! That's exactly right- you can't just import the route directly into the vrf like I was trying to do.

 

In addition to the above... I redistributed the global static routes into the ipv4 address family of BGP- THEN they import in the vpnv4 vrf table...as shown below.

 

PE-R8#show ip bgp

  Network          Next Hop            Metric LocPrf Weight Path
 r>i 8.8.8.8/32       152.177.58.146           0    100      0 ?
 *>  9.9.9.9/32       152.177.58.141           0         32768 ?
 r>i 152.177.58.140/30
                             152.177.58.146           0    100      0 ?
 *>  152.177.58.144/30
                             152.177.58.141          
0         32768 ?
show ip bgp all

For address family: VPNv4 Unicast

Route Distinguisher: 120:120 (default for vrf TGI)
Import Map: IMPORT_STATIC_MAP, Address-Family: IPv4 Unicast, Pfx Count/Limit: 1/1000
 *>  10.7.1.0/24          152.177.58.138    0             0 65002 i
 *>i 10.24.20.0/22      9.9.9.9                  0    100      0 65001 i
 *>i 51.64.56.252/30  9.9.9.9                  0    100      0 65001 i
 *>i 130.148.200.126/32
                                  9.9.9.9                  0    100      0 65001 i
 *>i 152.177.58.132/30
                                 9.9.9.9                  0    100      0 65001 i
 r>  152.177.58.136/30
                                152.177.58.138           0             0 65002 i
 *>  152.177.58.144/30
                       152.177.58.141          
0         32768 ?
 

 

So..to sum up...here's the config that worked: (for PE-R8....R9 config'd similarly)

ip vrf TGI

rd 120:120

import ipv4 unicast map IMPORT_STATIC_MAP

route-target export 20:20

route-target import 20:20

 

router bgp 65000

bgp router-id 8.8.8.8

bgp log-neighbor-changes

neighbor 9.9.9.9 remote-as 65000

neighbor 9.9.9.9 update-source Loopback8

!

address-family ipv4

redistribute static

neighbor 9.9.9.9 activate

exit-address-family

!

address-family vpnv4

neighbor 9.9.9.9 activate

neighbor 9.9.9.9 send-community both

exit-address-family

!

address-family ipv4 vrf TGI

neighbor 152.177.58.138 remote-as 65002

neighbor 152.177.58.138 activate

exit-address-family

 

ip route 9.9.9.9 255.255.255.255 152.177.58.141

ip route 152.177.58.144 255.255.255.252 152.177.58.141

!

!

ip prefix-list IMPORT_STATIC seq 5 permit 152.177.58.144/30

!

route-map IMPORT_STATIC_MAP permit 10

match ip address prefix-list IMPORT_STATIC

 

 

 

 

your bgp config seems correct. instead of static routes, you better run ospf and ldp over ospf.

I labbed what you are trying here and can't see anything wrong (both redistributing static and importing route from global to vrf). R1-R2-R3-R4

Review Cisco Networking for a $25 gift card