Export routes from VRF to global routing table, Cisco Nexus 3048

[theamberlion]

Hello everyone.

I have a couple of Cisco Nexus 3048  paired in a vPC domain and HSRP.

n3000-uk9-kickstart.6.0.2.U2.2

system:    version 6.0(2)U2(2)

I'm trying to perform route leaking between VRF and GRT

vrf context CT_net
  address-family ipv4 unicast
    route-target import 1:1
    route-target import 2:2
    route-target import 3:3
    route-target export 2:2
    export map ROUTE_LEAK
    import map ROUTE_LEAK
    import vrf default map ROUTE_LEAK
vrf context MF_interconn
  address-family ipv4 unicast
    route-target import 2:2
    route-target import 3:3
    route-target export 3:3
    export map ROUTE_LEAK
    import map ROUTE_LEAK
router bgp 150
  address-family ipv4 unicast
    redistribute static route-map ROUTE_LEAK
  vrf CTIF_net
    address-family ipv4 unicast
      redistribute direct route-map ROUTE_LEAK
      redistribute static route-map ROUTE_LEAK
  vrf MinFin_interconn
    address-family ipv4 unicast
      redistribute direct route-map ROUTE_LEAK
      redistribute static route-map ROUTE_LEAK

ip prefix-list ROUTE_LEAK seq 10 permit 0.0.0.0/0 le 32 
route-map ROUTE_LEAK permit 10
  match ip address prefix-list ROUTE_LEAK 

Using this config, i have GRT routes imported in context CT_net, using

import vrf default map ROUTE_LEAK

more than that, both VRFs share routes between them.

Now i want to export the routes from CT_net into the GRT. In the Cisco Nexus 9000 documentation and examples, there is a command which does that:

export vrf default map

But when i try to apply this command in my vrf context CT_net, the command is unknown.

The question: Can i, and if yes, how do i export directly connected and static routes from VRF CT_net to GRT on a Nexus 3k.

[Georg Pauwen · Accepted solution]

Hello,

Route leaking to the default VRF is not allowed because it is the global VRF. That is one of the limitations for VRF on the Nexus 3K. Which means you can only import/leak FROM the default VRF

https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3000/sw/unicast/602_u1_1/l3_nx-os/l3_virtual.html#Guidelines%20and%20Limitations%20for%20VRF%20Route-Leak

[theamberlion]

Thank you for pointing me at limitations.

Any ideas on how to make connection between default vrf and custom one?

[Georg Pauwen]

Unfortunately, I think it is a platform limitation on the N3K...

[paul driver]

Hello

First apologies if I have your topology wrong, Bu to to confirm that you wish to export the routes currently in the CT_net vrf rib into GRT ?  I don't see any related config for GRT ? Is this another vrf on another PE router or it is a acronym for general route table?

[theamberlion]

GRT here stands for Global Routing Table.
aka the 'default' vrf:

show ip route vrf default

versus custom vrf CT_net

show ip route vrf CT_net

[paul driver]

hello

---

@theamberlion wrote:

GRT here stands for Global Routing Table.
aka the 'default' vrf:

show ip route vrf default

versus custom vrf CT_net

show ip route vrf CT_net

---

I have just tested this and it is indeed the GRT ---- Well I never!

switch# sh ip route | in V
IP Route Table for VRF "default"
'%<string>' in via output denotes VRF <string>

switch# sh ip adjacency | in V
IP Adjacency Table for VRF default

@Georg Pauwen wrote:

Hello,

Route leaking to the default VRF is not allowed because it is the global VRF. That is one of the limitations for VRF on the Nexus 3K. Which means you can only import/leak FROM the default VRF

This looks ONLY applicable for vrf-lite.