Question

VRF-lite IPv4 prefix advertisement through VXLAN EVPN

  • 18 March 2020
  • 2 replies
  • 86 views

 

Hello,

 

As per the above simplified network architecture.

I’m trying to understand whether or not, IPv4 prefix advertisement can be supported with VXLAN (Type-5 entry).

Let’s consider the above network design.

DC1 has subnet 10.10.1.0/24

DC2 has subnet 10.10.2.0/24

Host to host communication (between both DC & submet) does work well within VRF spun up in both locations.

Let’s assume, there are external communication requirements for office branches to access those subnet. That traffic goes through an ISP based L3VPN cloud.

This is peering with the DC TOR switch within a VRF.

If one of the CPE fails for whatever reason, is it possible to advertise the opposite network through a Type-5 VXLAN entry network type, so that this subnet could then be reachable again through the remaining ISP CPE device in the other DC.

 

 

PS : This is a cumulus VX environment (Lab)


2 replies

Hmm,

 

Looks like I just fixed my problem.

The VLAN corresponding to the  main VRF (L3VNI,aggregating both location VLAN, L2VNI) wasn’t mapped to the VRF itself…

 

:~$ net show bgp l2vpn evpn vni
Advertise Gateway Macip: Disabled
Advertise SVI Macip: Disabled
Advertise All VNI flag: Enabled
BUM flooding: Head-end replication
Number of L2 VNIs: 2
Number of L3 VNIs: 1
Flags: * - Kernel

  VNI        Type RD                    Import RT                 Export RT                 Tenant VRF
* 900050     L2   10.255.230.3:2        64910:900050              64910:900050             LAB
  904050     L2   10.255.230.3:6        64910:904050              64910:904050             default
* 904050     L3   10.50.222.100:4       64910:904050              64910:904050             LAB ← This was missing….
cumulus@LEAF-GEA:mgmt:~$

 

Route Distinguisher: 10.50.222.100:2
*> [5]:[0]:[24]:[10.40.222.0]
                    10.255.231.4                           0 64900 64950 64960 i
                    RT:64960:904050 ET:8 Rmac:0c:cd:cc:5c:4b:04
*> [5]:[0]:[24]:[10.50.222.0]
                    10.255.231.4                           0 64900 64950 64960 ?
                    RT:64960:904050 ET:8 Rmac:0c:cd:cc:5c:4b:04
*> [5]:[0]:[29]:[10.4.1.0]
                    10.255.231.4                           0 64900 64950 64960 ?
                    RT:64960:904050 ET:8 Rmac:0c:cd:cc:5c:4b:04
Route Distinguisher: 10.50.222.100:4
*> [5]:[0]:[24]:[10.50.222.0]
                    10.255.230.3             0         32768 i
                    ET:8 RT:64910:904050 Rmac:0c:cd:cc:6c:d8:0a
*> [5]:[0]:[29]:[10.5.1.0]
                    10.255.230.3             0         32768 ?
                    ET:8 RT:64910:904050 Rmac:0c:cd:cc:6c:d8:0a
 

This can therefore be resolved ;-)

 

 

Userlevel 4

Great, glad you figured it out and shared how you resolved it, @Seb-ELCA !

Reply