zNetLaB › Guided labs › Data Center
Troubleshoot: VXLAN EVPN, one leaf left out
Data Center Advanced 5 devices 2 checked tasks 100 points Plan lab
The underlay is up on every switch, but host 1 cannot reach host 2 and leaf 1 has no NVE peer. Read the spine and fix the overlay. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
The underlay is up on every switch, but host 1 cannot reach host 2 and leaf 1 has no NVE peer. Read the spine and fix the overlay.
Your role: a network engineer. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 3 switchs, 2 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. L1 starts with and VLAN 10, OSPF 1, BGP 65000 already configured. SP starts with and OSPF 1, BGP 65000 already configured. L2 starts with and VLAN 10, OSPF 1, BGP 65000 already configured. H1 starts with addresses (G1 192.168.10.1/24). H2 starts with addresses (G1 192.168.10.2/24).
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
The spine has an EVPN session to leaf 2 (40 pts) Host 1 reaches host 2 (60 pts)
The activity, in order
The spine has an EVPN session to leaf 2 show running-config bgp on the spine: neighbor 2.2.2.2 has no inherit peer L. Add it.Why: Each goal is a state the lab can check on the running device. Verify with: show bgp l2vpn evpn summary Host 1 reaches host 2 Once leaf 2 routes are reflected, leaf 1 builds the NVE peer.Why: Each goal is a state the lab can check on the running device. Verify with: show nve peers
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
The underlay is up on every switch, but host 1 cannot reach host 2 and leaf 1 has no NVE peer. Read the spine and fix the overlay.
What you will be able to do
The spine has an EVPN session to leaf 2
Host 1 reaches host 2
The network
Nexus 9300, Catalyst 8000V — 5 devices in all, already cabled.
Eth1/1 Eth1/1 Eth1/1 Eth1/2 Gi1 192.168.10.1/24 Eth1/5 Gi1 192.168.10.2/24 Eth1/5 L1 SP L2 H1 H2 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
L1 Nexus 9300 configure it
SP Nexus 9300 configure it
L2 Nexus 9300 configure it
H1 Catalyst 8000V configure it
H2 Catalyst 8000V configure it
Cabling
L1 Ethernet1/1 ↔ SP Ethernet1/1
L2 Ethernet1/1 ↔ SP Ethernet1/2
H1 Gi1 ↔ L1 Ethernet1/5
H2 Gi1 ↔ L2 Ethernet1/5
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
SP feature ospf
feature bgp
feature nv overlay
nv overlay evpn
router ospf 1
router-id 9.9.9.9
exit
interface loopback0
ip address 9.9.9.9/32
ip router ospf 1 area 0.0.0.0
exit
interface Ethernet1/1
no switchport
ip address 10.1.0.9/24
ip router ospf 1 area 0.0.0.0
no shutdown
exit
interface Ethernet1/2
no switchport
ip address 10.2.0.9/24
ip router ospf 1 area 0.0.0.0
no shutdown
exit
router bgp 65000
router-id 9.9.9.9
address-family l2vpn evpn
retain route-target all
exit
template peer L
remote-as 65000
update-source loopback0
address-family l2vpn evpn
send-community extended
route-reflector-client
exit
exit
neighbor 1.1.1.1
inherit peer L
exit
neighbor 2.2.2.2
exit
exit
L1 feature ospf
feature bgp
feature nv overlay
feature vn-segment-vlan-based
nv overlay evpn
vlan 10
vn-segment 10010
exit
router ospf 1
router-id 1.1.1.1
exit
interface loopback0
ip address 1.1.1.1/32
ip router ospf 1 area 0.0.0.0
exit
interface Ethernet1/1
no switchport
ip address 10.1.0.1/24
ip router ospf 1 area 0.0.0.0
no shutdown
exit
interface Ethernet1/5
switchport
switchport access vlan 10
no shutdown
exit
interface nve1
no shutdown
host-reachability protocol bgp
source-interface loopback0
member vni 10010
ingress-replication protocol bgp
exit
exit
evpn
vni 10010 l2
rd auto
route-target import auto
route-target export auto
exit
exit
router bgp 65000
router-id 1.1.1.1
neighbor 9.9.9.9
remote-as 65000
update-source loopback0
address-family l2vpn evpn
send-community extended
exit
exit
exit
L2 feature ospf
feature bgp
feature nv overlay
feature vn-segment-vlan-based
nv overlay evpn
vlan 10
vn-segment 10010
exit
router ospf 1
router-id 2.2.2.2
exit
interface loopback0
ip address 2.2.2.2/32
ip router ospf 1 area 0.0.0.0
exit
interface Ethernet1/1
no switchport
ip address 10.2.0.2/24
ip router ospf 1 area 0.0.0.0
no shutdown
exit
interface Ethernet1/5
switchport
switchport access vlan 10
no shutdown
exit
interface nve1
no shutdown
host-reachability protocol bgp
source-interface loopback0
member vni 10010
ingress-replication protocol bgp
exit
exit
evpn
vni 10010 l2
rd auto
route-target import auto
route-target export auto
exit
exit
router bgp 65000
router-id 2.2.2.2
neighbor 9.9.9.9
remote-as 65000
update-source loopback0
address-family l2vpn evpn
send-community extended
exit
exit
exit
H1 interface GigabitEthernet1
ip address 192.168.10.1 255.255.255.0
no shutdown
exit
H2 interface GigabitEthernet1
ip address 192.168.10.2 255.255.255.0
no shutdown
exit
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 The spine has an EVPN session to leaf 2 40 On SP: show bgp l2vpn evpn summary output matches 2\.2\.2\.2\s+4\s+65000.
2 Host 1 reaches host 2 60 On H1: ping 192.168.10.2 must succeed. and On L1: show nve peers output matches 2\.2\.2\.2.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
SP router bgp 65000
neighbor 2.2.2.2
inherit peer L
exit
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up