Hello all
i am running into an issue where even though i'm able to successfully leak routes from a VRF to the global routing table and vice versa, devices inside the VRF (4.149.253.0/24) and devices from the global routing table (13.38.0.0/28) are still unable to ping each other. Traceroutes sourcing from either of the networks will die as soon as they get to core 4 where the route leaking is happening. below is pertitent info concerning the network.
TOPOLOGY
CORE 4 INFO WHERE ROUTE LEAKING IS HAPPENING
RUNNING CONFIG
vrf definition ENTERPRISE-A
rd 23444:4
route-target export 22:23444
route-target import 22:23444
address-family ipv4
import ipv4 unicast map GLOBAL_TO_ENTA
export ipv4 unicast map ENTA_TO_GLOBAL
exit-address-family
!
interface GigabitEthernet2.40
encapsulation dot1Q 40
vrf forwarding ENTERPRISE-A
ip address 3.222.44.4 255.255.255.0
!
route-map GLOBAL_TO_ENTA permit 10
match ip address prefix-list DEFAULT
!
route-map ENTA_TO_GLOBAL permit 10
match ip address prefix-list ENTA-PUBLICS
!
ip prefix-list DEFAULT seq 5 permit 0.0.0.0/0
ip prefix-list ENTA-PUBLICS seq 5 permit 4.149.253.0/24
!
router bgp 300
!
address-family ipv4
network 0.0.0.0
!
address-family ipv4 vrf ENTERPRISE-A
redistribute connected
neighbor 3.222.44.44 remote-as 300
neighbor 3.222.44.44 activate
neighbor 3.222.44.44 route-reflector-client
exit-address-family
GLOBAL BGP TABLE
BGP routing table entry for 4.149.253.0/24, version 103
Paths: (1 available, best #1, table default)
Advertised to update-groups:
4 6
Refresh Epoch 3
23444, (Received from a RR-client), imported path from 23444:4:4.149.253.0/24 (ENTERPRISE-A)
3.222.44.44 from 3.222.44.44 (3.0.0.44)
Origin IGP, metric 0, localpref 100, valid, internal, best
Extended Community: RT:22:23444
rx pathid: 0, tx pathid: 0x0
Updated on Apr 29 2024 01:17:09 UTC
!
BGP routing table entry for 0.0.0.0/0, version 2
Paths: (1 available, best #1, table default)
Advertised to update-groups:
4 6
Refresh Epoch 1
Local
0.0.0.0 from 0.0.0.0 (3.0.0.4)
Origin IGP, metric 0, localpref 100, weight 32768, valid, sourced, local, af-export(1), best
rx pathid: 0, tx pathid: 0x0
Updated on Apr 29 2024 01:12:56 UTC
GLOBAL ROUTING TABLE
Routing entry for 4.149.253.0/24
Known via "bgp 300", distance 200, metric 0
Tag 23444, type internal
Last update from 3.222.44.44 01:06:12 ago
Routing Descriptor Blocks:
* 3.222.44.44 (ENTERPRISE-A), from 3.222.44.44, 01:06:12 ago
opaque_ptr 0x7F19CAEFC608
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 23444
MPLS label: none
!
Routing entry for 13.38.0.0/28
Known via "ospf 300", distance 110, metric 2, type intra area
Last update from 3.20.34.3 on GigabitEthernet1, 01:18:21 ago
Routing Descriptor Blocks:
* 3.20.34.3, from 255.255.255.3, 01:18:21 ago, via GigabitEthernet1
Route metric is 2, traffic share count is 1
!
Routing entry for 0.0.0.0/0, supernet
Known via "static", distance 1, metric 0 (connected), candidate default path
Advertised by bgp 300
Routing Descriptor Blocks:
* directly connected, via Null0
Route metric is 0, traffic share count is 1
VRF BGP TABLE
BGP routing table entry for 23444:4:4.149.253.0/24, version 23
Paths: (2 available, best #1, table ENTERPRISE-A)
Advertised to update-groups:
1
Refresh Epoch 3
23444, (Received from a RR-client)
3.222.44.44 (via vrf ENTERPRISE-A) from 3.222.44.44 (3.0.0.44)
Origin IGP, metric 0, localpref 100, valid, internal, best
Extended Community: RT:22:23444
rx pathid: 0, tx pathid: 0x0
Updated on Apr 29 2024 01:17:09 UTC
Refresh Epoch 3
VRF ROUTING TABLE
Routing Table: ENTERPRISE-A
Routing entry for 4.149.253.0/24
Known via "bgp 300", distance 200, metric 0
Tag 23444, type internal
Last update from 3.222.44.44 01:16:05 ago
Routing Descriptor Blocks:
* 3.222.44.44, from 3.222.44.44, 01:16:05 ago
opaque_ptr 0x7F1956340438
Route metric is 0, traffic share count is 1
AS Hops 1
Route tag 23444
MPLS label: none
Hi @adamehill87
sorry for late reply I was need one day off to run lab to check this case
the lab
I was not 100% sure that I am correct and there is no limitation of route import/export via BGP leaking so I wait to run lab and check.
and I was correct there is no limitation,
I run EIGRP and BGP and config R1 as leaking router and you can see that the R2 is get default route leak from R1 (R1 learn it from R3)
the issue I think in your case is some missing command it not vrf leak limitation
if you want to complete your lab and check the default route leaking please confirm that
MHM
