Cisco VxLAN EVPN Route Leaking – 1

Leave a Comment

Overview

Route leaking in Cisco VXLAN EVPN fabrics plays a critical role in enabling communication between workloads residing in different L3 VXLAN Network Segments (VNIs), VRFs. It essentially allows these workloads to seamlessly access resources and services provided by shared services or external networks.

VRF (Virtual Routing and Forwarding) – VRFs are leveraged to establish isolated routing domains. These VRFs act like virtual routers within a physical switch, maintaining separate routing tables and forwarding policies. VRFs can be used to create private network segments for individual tenants within the data center. This isolation ensures that tenant workloads cannot interfere with traffic belonging to other tenants, enhancing security and compliance.

Why do we need route leaking then:

  • Shared Services – A shared services VRF can be established for hosting services like DNS, DHCP, monitoring and management servers, NTP and etc. The shared services VRF could centrally managed and accessed by multiple tenants requiring those services. Route leaking could be used to centrally manage routing for these services and ensure they are accessible to authorized workloads across different L3 domains within the fabric.
  • Shared External Network Connectivity: A VRF can be specifically designated for connecting the VXLAN EVPN fabric to external networks like the internet, a WAN, or another VXLAN EVPN fabric. This VRF provides a controlled pathway for workloads within the fabric in multiple VRFs through route leaking to access resources and services on the external network.
  • Security: Route leaking policies can be used to restrict access to shared services or external networks only for authorized workloads within specific L3 domains.

Route leaking is required to deploy VxLAN EVPN fabric with shared services VRF and shared external network connectivity, so how do we implement route leaking? this blog walk us through the process of configuring route leaking for shared services.

Topology

Centralized route leaking at border leaf (BL) nodes
  • Route leaking configuration only done on the BLs
  • Default routes advertised to leaf switches from the BLs
  • Configuration simplicity
  • Traffic between vrfs needs to cross BL
Distributed route leaking at all leaf switches where the VRF presents
  • Route leaking configuration on all leaf switches where the vrf requiring route leaking presents. This is error prone for cli or script based deployment (using NDFC resolves this issue)
  • Manually managing the configuration and identifying the leaf switches with the vrf increases the complexity as the network size increase (using NDFC avoids the complexity)
  • Traffic doesn’t cross the BL unnecessarily

Goal – Green vrf imports Blue & Orange vrfs and Blue & Orange vrfs import Green vrf using both methods

Assumptions

  • The information in this document was created from the devices in a CML lab environment
  • VxLAN EVPN fabric already configured with VRFs – Green (for shared services), Blue & Orange
  • All hosts are working within their VRF
  • The topology is built on CML
  • CML version used for the lab – Version: 2.6.0+build.5
  • NDFC version used for the lab – 12.1.3b
  • In a live network environment , ensure that you understand the potential impact of any command

Configuration

VXLAN EVPN uses MP-BGP and its route-policy concept to import and export prefixes. Border leaf switches can selectively import advertised routes into their own VRFs based on predefined policies. This allows workloads within those VRFs to learn about the shared services or external network and establish communication paths.

  • Import Policies: These policies define which routes from advertised VRFs a specific VRF will import into its routing table. This allows for granular control over which route prefix can access shared services or external resources.
  • Export Policies: These policies define which routes from a VRF will be advertised to other VRFs within the fabric. This helps control the overall routing information propagation within the VXLAN EVPN fabric.

Route leaking between vrfs ‘Blue’ & ‘Orange’ and vrf ‘Green’ (shared services vrf) at the border leaf nodes is demonstrated.

Route Leaking at the Border Leaf (BL) Nodes only – Configuration

### Current state - no route leaking (blue and/or Orange can't access green,shared services, vrf)

cisco@S-3:~$ ping 10.10.30.10 #(Blue pinging Green)
PING 10.10.30.10 (10.10.30.10): 56 data bytes
^C
--- 10.10.30.10 ping statistics ---
7 packets transmitted, 0 packets received, 100% packet loss

cisco@S-4:~$ ping 10.10.30.10 #(Orange pinging Green)
PING 10.10.30.10 (10.10.30.10): 56 data bytes
^C
--- 10.10.30.10 ping statistics ---
8 packets transmitted, 0 packets received, 100% packet loss

### Route Leaking configuration at the BLs

### BL-1 & BL-2

### static default route to advertise to all leaf switches with the vrf

vrf context Blue
  ip route 0.0.0.0/0 null0
vrf context Orange
  ip route 0.0.0.0/0 Null0
vrf context Green
  ip route 0.0.0.0/0 Null0

### advertise the default route to all leaf switches with the vrf

router bgp 65125
  vrf Blue
    address-family ipv4 unicast
      network 0.0.0.0/0
  vrf Orange
    address-family ipv4 unicast
      network 0.0.0.0/0
  vrf Green
    address-family ipv4 unicast
      network 0.0.0.0/0

### Route leaking using the route target import - route target use ASN:vni format

vrf context Blue
 address-family ipv4 unicast
   import vrf advertise-vpn
   route-target import 65125:30002          # importing vrf Green - vni for Green is 30002
   route-target import 65125:30002 evpn
vrf context Orange
 address-family ipv4 unicast
   import vrf advertise-vpn
   route-target import 65125:30002          # importing vrf Green - vni for Green is 30002
   route-target import 65125:30002 evpn
vrf context Green
 address-family ipv4 unicast
   import vrf advertise-vpn
   route-target import 65125:30000          # importing vrf Blue - vni for Blue is 30000
   route-target import 65125:30000 evpn
   route-target import 65125:30001          #  importing vrf Orange - vni for orange is 30001
   route-target import 65125:30001 evpn

### This will leak all routes between the vrfs, route-map can be used if filtering is needed

Route Leaking at the Border Leaf (BL) Nodes only – Verification

### BLs

### show ip route vrf <vrf name>

BL-1# sh ip route vrf blue 
<snipped output... to only show that the Green vrf networks are imported into Blue vrf  - 10.10.20.0/24 & 10.10.30.0/24>

10.10.20.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN
    *via 10.10.100.116%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN 
10.10.20.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN 
10.10.30.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN
    *via 10.10.100.116%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN 
10.10.30.10/32, ubest/mbest: 1/0
    *via 10.10.100.121%default, [200/0], 00:04:36, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6479 encap: VXLAN
    
BL-1# sh ip route vrf orange
<snipped output... to only show that the Green vrf networks are imported into Orange  vrf  - 10.10.20.0/24 & 10.10.30.0/24>

10.10.20.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN
    *via 10.10.100.116%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN
10.10.20.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN
10.10.30.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN
    *via 10.10.100.116%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN 
10.10.30.10/32, ubest/mbest: 1/0
    *via 10.10.100.121%default, [200/0], 00:04:55, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a6479 encap: VXLAN

BL-1# sh ip route vrf Green
<snipped output... to only show that the Blue & Orange vrf networks are imported into Green vrf  - 10.10.40.0/24 & 10.10.50.0/24>

10.10.40.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30000 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN
    *via 10.10.100.116%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30000 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN
10.10.40.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30000 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN
10.10.50.0/24, ubest/mbest: 2/0
    *via 10.10.100.113%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30001 (Asymmetric) tunnelid: 0xa0a6471 encap: VXLAN 
    *via 10.10.100.116%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30001 (Asymmetric) tunnelid: 0xa0a6474 encap: VXLAN 
10.10.50.10/32, ubest/mbest: 1/0
    *via 10.10.100.121%default, [200/0], 00:05:03, bgp-65125, internal, tag 6512
5, segid: 30001 (Asymmetric) tunnelid: 0xa0a6479 encap: VXLAN
 

### Leaf nodes

### show ip route vrf <vrf name>

<snipped output... to only show that Blue, Orange and Green vrfs are getting the default route pointing to the BLs where the route leaking is done>

L-1# sh ip route vrf Blue 

0.0.0.0/0, ubest/mbest: 2/0
    *via 10.10.100.111%default, [200/0], 00:28:27, bgp-65125, internal, tag 6512
5, segid: 30000 tunnelid: 0xa0a646f encap: VXLAN
    *via 10.10.100.112%default, [200/0], 00:21:35, bgp-65125, internal, tag 6512
5, segid: 30000 tunnelid: 0xa0a6470 encap: VXLAN
 
L-1# sh ip route vrf Orange 

0.0.0.0/0, ubest/mbest: 2/0
    *via 10.10.100.111%default, [200/0], 00:31:53, bgp-65125, internal, tag 6512
5, segid: 30001 tunnelid: 0xa0a646f encap: VXLAN 
    *via 10.10.100.112%default, [200/0], 00:21:46, bgp-65125, internal, tag 6512
5, segid: 30001 tunnelid: 0xa0a6470 encap: VXLAN
 
L-1# sh ip route vrf Green

0.0.0.0/0, ubest/mbest: 2/0
    *via 10.10.100.111%default, [200/0], 00:32:02, bgp-65125, internal, tag 6512
5, segid: 30002 tunnelid: 0xa0a646f encap: VXLAN 
    *via 10.10.100.112%default, [200/0], 00:21:55, bgp-65125, internal, tag 6512
5, segid: 30002 tunnelid: 0xa0a6470 encap: VXLAN
 
### Ping from Green (10.10.20.10) to Blue (10.10.40.10) & Orange (10.10.50.10)

cisco@inserthostname-here:/home$ ping 10.10.40.10
PING 10.10.40.10 (10.10.40.10) 56(84) bytes of data.
64 bytes from 10.10.40.10: icmp_seq=1 ttl=61 time=87.1 ms
64 bytes from 10.10.40.10: icmp_seq=2 ttl=61 time=71.8 ms
64 bytes from 10.10.40.10: icmp_seq=3 ttl=61 time=62.0 ms
64 bytes from 10.10.40.10: icmp_seq=4 ttl=61 time=42.2 ms
64 bytes from 10.10.40.10: icmp_seq=5 ttl=61 time=92.4 ms
^C
--- 10.10.40.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4007ms
rtt min/avg/max/mdev = 42.230/71.088/92.418/18.033 ms
cisco@inserthostname-here:/home$ ping 10.10.50.10
PING 10.10.50.10 (10.10.50.10) 56(84) bytes of data.
64 bytes from 10.10.50.10: icmp_seq=1 ttl=61 time=42.5 ms
64 bytes from 10.10.50.10: icmp_seq=2 ttl=61 time=82.1 ms
64 bytes from 10.10.50.10: icmp_seq=3 ttl=61 time=61.2 ms
64 bytes from 10.10.50.10: icmp_seq=4 ttl=61 time=76.2 ms
64 bytes from 10.10.50.10: icmp_seq=5 ttl=61 time=67.9 ms
^C
--- 10.10.50.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4009ms
rtt min/avg/max/mdev = 42.521/66.007/82.132/13.727 ms

### Ping from Blue (10.10.40.10) to Green (10.10.20.10 & 10.10.30.10) & Orange (10.10.50.10)
### Ping to Orange failed since no leaking between Blue and Orange

cisco@S-3:~$ ping 10.10.20.10
PING 10.10.20.10 (10.10.20.10): 56 data bytes
64 bytes from 10.10.20.10: seq=0 ttl=61 time=106.894 ms
64 bytes from 10.10.20.10: seq=1 ttl=61 time=125.771 ms
64 bytes from 10.10.20.10: seq=2 ttl=61 time=102.512 ms
64 bytes from 10.10.20.10: seq=3 ttl=61 time=109.303 ms
64 bytes from 10.10.20.10: seq=4 ttl=61 time=219.053 ms
^C
--- 10.10.20.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 102.512/132.706/219.053 ms
cisco@S-3:~$ ping 10.10.30.10
PING 10.10.30.10 (10.10.30.10): 56 data bytes
64 bytes from 10.10.30.10: seq=0 ttl=61 time=192.478 ms
64 bytes from 10.10.30.10: seq=1 ttl=61 time=257.145 ms
64 bytes from 10.10.30.10: seq=2 ttl=61 time=291.892 ms
64 bytes from 10.10.30.10: seq=3 ttl=61 time=132.459 ms
64 bytes from 10.10.30.10: seq=4 ttl=61 time=121.943 ms
^C
--- 10.10.30.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 121.943/199.183/291.892 ms
cisco@S-3:~$ ping 10.10.50.10
PING 10.10.50.10 (10.10.50.10): 56 data bytes
^C
--- 10.10.50.10 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
cisco@S-3:~$

### Ping from Orange (10.10.50.10) to Green (10.10.20.10 & 10.10.30.10) & Blue (10.10.40.10)
### Ping to Blue failed since no leaking between Blue and Orange

cisco@S-4:~$ ping 10.10.20.10
PING 10.10.20.10 (10.10.20.10): 56 data bytes
64 bytes from 10.10.20.10: seq=0 ttl=61 time=73.934 ms
64 bytes from 10.10.20.10: seq=1 ttl=61 time=100.217 ms
64 bytes from 10.10.20.10: seq=2 ttl=61 time=152.819 ms
64 bytes from 10.10.20.10: seq=3 ttl=61 time=61.999 ms
64 bytes from 10.10.20.10: seq=4 ttl=61 time=280.135 ms
--- 10.10.20.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss^C
round-trip min/avg/max = 61.999/133.820/280.135 ms

cisco@S-4:~$ ping 10.10.30.10
PING 10.10.30.10 (10.10.30.10): 56 data bytes
64 bytes from 10.10.30.10: seq=0 ttl=61 time=72.506 ms
64 bytes from 10.10.30.10: seq=1 ttl=61 time=101.739 ms
64 bytes from 10.10.30.10: seq=2 ttl=61 time=79.043 ms
64 bytes from 10.10.30.10: seq=3 ttl=61 time=73.303 ms
64 bytes from 10.10.30.10: seq=4 ttl=61 time=63.342 ms
^C
--- 10.10.30.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 63.342/77.986/101.739 ms
cisco@S-4:~$ ping 10.10.40.10
PING 10.10.40.10 (10.10.40.10): 56 data bytes
^C
--- 10.10.40.10 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss

Route Leaking at All Leaf Nodes with VRF Configured – Configuration

### All switches with the vrf are configured with route target import command with ASN:vni format

vrf context Blue
 address-family ipv4 unicast
   route-target import 65125:30002          
   route-target import 65125:30002 evpn
vrf context Orange
 address-family ipv4 unicast
   route-target import 65125:30002          
   route-target import 65125:30002 evpn
vrf context Green
 address-family ipv4 unicast
   route-target import 65125:30000          
   route-target import 65125:30000 evpn
   route-target import 65125:30001         
   route-target import 65125:30001 evpn

### This will leak all routes between the vrfs, route-map can be used if filtering is needed

Route Leaking at All Leaf Nodes with VRF Configured – Verification 

### Leaf Switches - Sample leaf switch is used all have the same policy and route

### show ip route vrf <vrf name>

L-1# sh ip route vrf Blue
<snipped output... to only show that the Green vrf networks are imported into Blue vrf  - 10.10.20.0/24 & 10.10.30.0/24>

10.10.20.0/24, ubest/mbest: 1/0, attached
    *via 10.10.20.1%green, Vlan20, [20/0], 00:05:20, bgp-65125, external, tag 65
125
10.10.20.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:05:20, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN
 
10.10.30.0/24, ubest/mbest: 1/0, attached
    *via 10.10.30.1%green, Vlan30, [20/0], 00:05:20, bgp-65125, external, tag 65
125

L-1# sh ip route vrf Orange 
<snipped output... to only show that the Green vrf networks are imported into Orange vrf  - 10.10.20.0/24 & 10.10.30.0/24>

10.10.20.0/24, ubest/mbest: 1/0, attached
    *via 10.10.20.1%green, Vlan20, [20/0], 00:08:27, bgp-65125, external, tag 65
125
10.10.20.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:08:27, bgp-65125, internal, tag 6512
5, segid: 30002 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN
 
10.10.30.0/24, ubest/mbest: 1/0, attached
    *via 10.10.30.1%green, Vlan30, [20/0], 00:08:27, bgp-65125, external, tag 65
125

L-1# sh ip route vrf Green 
<snipped output... to only show that the Blue and Orange vrf networks are imported into Green vrf  - 10.10.40.0/24 & 10.10.50.0/24>

10.10.40.0/24, ubest/mbest: 1/0, attached
    *via 10.10.40.1%blue, Vlan40, [20/0], 00:10:04, bgp-65125, external, tag 651
25
10.10.40.10/32, ubest/mbest: 1/0
    *via 10.10.100.143%default, [200/0], 00:10:03, bgp-65125, internal, tag 6512
5, segid: 30000 (Asymmetric) tunnelid: 0xa0a648f encap: VXLAN
 
10.10.50.0/24, ubest/mbest: 1/0, attached
    *via 10.10.50.1%orange, Vlan50, [20/0], 00:10:04, bgp-65125, external, tag 6
5125

### Ping from Green (10.10.20.10) to Blue (10.10.40.10) & Orange (10.10.50.10)
cisco@inserthostname-here:/home$ ping 10.10.40.10
PING 10.10.40.10 (10.10.40.10) 56(84) bytes of data.
64 bytes from 10.10.40.10: icmp_seq=1 ttl=63 time=22.9 ms
64 bytes from 10.10.40.10: icmp_seq=2 ttl=63 time=11.5 ms
64 bytes from 10.10.40.10: icmp_seq=3 ttl=63 time=34.6 ms
64 bytes from 10.10.40.10: icmp_seq=4 ttl=63 time=13.7 ms
64 bytes from 10.10.40.10: icmp_seq=5 ttl=63 time=8.22 ms
^C
--- 10.10.40.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4009ms
rtt min/avg/max/mdev = 8.219/18.198/34.649/9.570 ms
cisco@inserthostname-here:/home$ ping 10.10.50.10
PING 10.10.50.10 (10.10.50.10) 56(84) bytes of data.
64 bytes from 10.10.50.10: icmp_seq=1 ttl=62 time=80.8 ms
64 bytes from 10.10.50.10: icmp_seq=2 ttl=62 time=31.6 ms
64 bytes from 10.10.50.10: icmp_seq=3 ttl=62 time=89.8 ms
64 bytes from 10.10.50.10: icmp_seq=4 ttl=62 time=91.4 ms
64 bytes from 10.10.50.10: icmp_seq=5 ttl=62 time=45.9 ms
^C
--- 10.10.50.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 31.578/67.883/91.378/24.508 ms

### Ping from Blue (10.10.40.10) to Green (10.10.20.10 & 10.10.30.10) & Orange (10.10.50.10)
### Ping to Orange failed since no leaking between Blue and Orange
cisco@S-3:~$ ping 10.10.20.10
PING 10.10.20.10 (10.10.20.10): 56 data bytes
64 bytes from 10.10.20.10: seq=0 ttl=63 time=12.672 ms
64 bytes from 10.10.20.10: seq=1 ttl=63 time=12.607 ms
64 bytes from 10.10.20.10: seq=2 ttl=63 time=24.609 ms
64 bytes from 10.10.20.10: seq=3 ttl=63 time=9.412 ms
64 bytes from 10.10.20.10: seq=4 ttl=63 time=12.450 ms
^C
--- 10.10.20.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 9.412/14.350/24.609 ms
cisco@S-3:~$ ping 10.10.30.10
PING 10.10.30.10 (10.10.30.10): 56 data bytes
64 bytes from 10.10.30.10: seq=0 ttl=62 time=45.365 ms
64 bytes from 10.10.30.10: seq=1 ttl=62 time=70.611 ms
64 bytes from 10.10.30.10: seq=2 ttl=62 time=27.379 ms
64 bytes from 10.10.30.10: seq=3 ttl=62 time=26.139 ms
64 bytes from 10.10.30.10: seq=4 ttl=62 time=38.306 ms
^C
--- 10.10.30.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 26.139/41.560/70.611 ms
cisco@S-3:~$ ping 10.10.50.10
PING 10.10.50.10 (10.10.50.10): 56 data bytes
^C
--- 10.10.50.10 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
cisco@S-3:~$ 

### Ping from Orange (10.10.50.10) to Green (10.10.20.10 & 10.10.30.10) & Blue (10.10.40.10)
### Ping to Blue failed since no leaking between Blue and Orange
cisco@S-4:~$ ping 10.10.20.10
PING 10.10.20.10 (10.10.20.10): 56 data bytes
64 bytes from 10.10.20.10: seq=0 ttl=62 time=39.020 ms
64 bytes from 10.10.20.10: seq=1 ttl=62 time=40.836 ms
64 bytes from 10.10.20.10: seq=2 ttl=62 time=62.246 ms
64 bytes from 10.10.20.10: seq=3 ttl=62 time=44.173 ms
64 bytes from 10.10.20.10: seq=4 ttl=62 time=31.494 ms
^C
--- 10.10.20.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 31.494/43.553/62.246 ms
cisco@S-4:~$ ping 10.10.30.10
PING 10.10.30.10 (10.10.30.10): 56 data bytes
64 bytes from 10.10.30.10: seq=0 ttl=63 time=13.773 ms
64 bytes from 10.10.30.10: seq=1 ttl=63 time=16.576 ms
64 bytes from 10.10.30.10: seq=2 ttl=63 time=23.394 ms
64 bytes from 10.10.30.10: seq=3 ttl=63 time=15.047 ms
64 bytes from 10.10.30.10: seq=4 ttl=63 time=28.026 ms
^C
--- 10.10.30.10 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 13.773/19.363/28.026 ms
cisco@S-4:~$ ping 10.10.40.10
PING 10.10.40.10 (10.10.40.10): 56 data bytes
^C
--- 10.10.40.10 ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

https://deliabtech.com/data-center/vxlan-evpn-fabric/

About

Leave a Comment

Your email address will not be published. Required fields are marked *