cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
575
Views
0
Helpful
4
Replies
Highlighted
Beginner

NX-OS route leaking from VRF to Global routing table

I would like to leak routes from the VRF called production into the global routing table and leak routes from the global routing table to the vrf on NX-OS.

 

I was able to accomplish the route leaking but I can't ping from the NX-OS device itself to the leaked routes or from an upstream router. 

 

This is a VIRL lab and the setup is pretty easy.

I have an IOSV router running EIGRP and its interface is 192.168.1.2/24

The NX-OS switch is running EIGRP on 192.168.1.1/24 and BGP for the route leaking.

The config for this is applied on the NX-OS and here are the details.

The production routes make it to the IOSV router no problem via the redistribution but I can't communicate to them. 

Is there something I'm missing?

Thank you!

 

<------------------------------------------------->
vrf context Production_VRF
  address-family ipv4 unicast
   route-target both 99:1
    import vrf default map any
    export vrf default map any
<------------------------------------------------->   

!

<------------------------------------------------->    
router eigrp Site-A
  autonomous-system 14
  address-family ipv4 unicast
    router-id 10.3.255.1
    passive-interface default
    metric version 64bit
    redistribute bgp 99 route-map any
<------------------------------------------------->   

!

<------------------------------------------------->    
router bgp 99
  address-family ipv4 unicast
    network 10.3.12.0/23
    network 192.168.1.0/24
  vrf Production_VRF
    address-family ipv4 unicast
      network 10.1.9.0/24
<------------------------------------------------->   

Show commands on the NX-OS to show the leaked routes

 

 

STA-Spine-201# sh ip route bgp
IP Route Table for VRF "default"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

10.1.9.0/24, ubest/mbest: 1/0, attached
    *via 10.1.9.2%Production_VRF, Vlan9, [20/0], 00:10:38, bgp-99, external, tag
 99,
 !
 !
 STA-Spine-201# show ip route vrf production_VRF bgp
IP Route Table for VRF "Production_VRF"
'*' denotes best ucast next-hop
'**' denotes best mcast next-hop
'[x/y]' denotes [preference/metric]
'%<string>' in via output denotes VRF <string>

10.3.12.0/23, ubest/mbest: 1/0, attached
    *via 10.3.12.2%default, Vlan1012, [20/0], 00:15:18, bgp-99, external, tag 99
,
192.168.1.0/24, ubest/mbest: 1/0, attached
    *via 192.168.1.1%default, Eth2/1, [20/0], 00:07:43, bgp-99, external, tag 99

4 REPLIES 4
Highlighted
VIP Mentor

Hi

 

Can you share your virl file?

 


Thanks
Francesco
PS: Please don't forget to rate and select as validated answer if this answered your question
Highlighted

I used dcloud virl lab and I do not have it sorry and thank you for replying

Highlighted
VIP Expert

Hello,

 

I have recreated your setup in GNS3 using the VIRL images, it appears to work as designed, I can ping the leaked routes locally. Can you post the config of the upstream device (the one that cannot ping the leaked routes externally) as well ?

Highlighted

Thank you for your efforts. The upstream router has a very simple config.  I do not have the power to recreate this in my lab so I use dcloud for my testing NX-OSV.

 

int g0/0
no shut
!
ip address 192.168.1.2 255.255.255.0
!
!
router eigrp 14
no auto-summary
network 192.168.1.2 0.0.0.0
!
!