CloudLabBox
Try the free demo

VXLAN EVPN lab 12 of 14

Troubleshooting the overlay

Four tickets, four overlay faults: a route target, a VNI and an ESI that do not match, and a silent host with no route to it.

Run this lab

It needs Standard: its 9 nodes are set to 9 vCPU and 10,752 MB in total.

In your workspace: Shared, then VXLAN EVPN fabrics guided labs, then 12 - Troubleshooting the overlay

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 9 vCPU and 10,752 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
9 vCPU, 10,752 MB
Smallest plan
Standard

The scenario

The underlay at Calder Freight is healthy now: every session is up and every VTEP is reachable. But four tickets came in after last week's change, and all of them are in the overlay.

TicketComplaint
1h1 (VLAN 10) and h3 (VLAN 10) can't reach each other
2h2 and h5 (VLAN 30) can't reach each other
3h1's bond is only using one of its two links
4h4, a licence server in VLAN 20, can't be reached from h3
ItemCorrect design
VLAN 10VNI 10010, RT 65000:10010, anycast gateway 10.10.10.1
VLAN 20 (leaf2 only)Not stretched, gateway 10.20.20.1
VLAN 30VNI 10030, RT 65000:10030, bridged only
VRF REDL3 VNI 50001, RT 65000:50001
h1's segmentlocal-id 1, MAC 44:38:39:be:ef:aa on both leaves

Hosts: h1 10.10.10.11 (bond to leaf1 and leaf2), h2 10.30.30.12 (leaf2 swp4), h3 10.10.10.13 (leaf3 Ethernet3), h4 10.20.20.14 (leaf2 swp5), h5 10.30.30.15 (leaf3 Ethernet4).

What you’ll practise

  • Find a route target mismatch
  • Find a VNI mismatch
  • Find an ESI mismatch from the host side and the leaf side
  • Explain how type 5 routes reach a silent host

The tasks

  1. Start the lab
  2. Ticket 1, routes that never get imported
  3. Ticket 2, the wrong VNI
  4. Ticket 3, an ESI that doesn't match
  5. Ticket 4, the silent host

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Troubleshooting the overlay9 nodes, 9 links. Every link is listed as text below the diagram.spine1leaf1leaf2leaf3h1h2h4h3h5swp4eth0Ethernet2swp1Ethernet3eth0swp3eth0Ethernet4eth0swp5eth0swp3eth1Ethernet1swp1Ethernet3Ethernet1
9 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • spine1 Ethernet1 to leaf1 swp1
  • spine1 Ethernet2 to leaf2 swp1
  • spine1 Ethernet3 to leaf3 Ethernet1
  • leaf1 swp3 to h1 eth0
  • leaf2 swp3 to h1 eth1
  • leaf2 swp4 to h2 eth0
  • leaf2 swp5 to h4 eth0
  • leaf3 Ethernet3 to h3 eth0
  • leaf3 Ethernet4 to h5 eth0
Nodes in Troubleshooting the overlay, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
spine1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
leaf1NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 MB
leaf2NVIDIA Cumulus VXcumulus-vx-5.9.11 vCPU, 2,048 MB
leaf3Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
h1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h4Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h3Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
h5Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder VXLAN EVPN fabrics guided labs.

  3. Open 12 - Troubleshooting the overlay and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More VXLAN EVPN labs

All VXLAN EVPN labs

CloudLabBox is independent of Arista Networks, Cisco, HPE, Juniper Networks and NVIDIA. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.