zNetLaB › Guided labs › Data Center
VXLAN EVPN fabric with a spine route reflector
Data Center Advanced 5 devices 4 checked tasks 100 points Plan lab
Two leaves and a spine. OSPF carries the loopbacks, the spine reflects the L2VPN EVPN routes, and VLAN 10 is stretched over VNI 10010 so the two hosts share one subnet. 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
Two leaves and a spine. OSPF carries the loopbacks, the spine reflects the L2VPN EVPN routes, and VLAN 10 is stretched over VNI 10010 so the two hosts share one subnet.
Your role: a network engineer. Level: Advanced Done when: all 4 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, SP, L2, H1, H2 start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
The spine holds an EVPN session to each leaf (25 pts) Leaf 1 sees leaf 2 as an NVE peer (25 pts) Host 1 reaches host 2 through the fabric (30 pts) After that ping, leaf 1 holds the far host MAC learned over BGP (20 pts)
The activity, in order
The spine holds an EVPN session to each leaf On the spine: OSPF on the links and loopback, feature bgp and nv overlay evpn, and a peer template with route-reflector-client and send-community extended for both leaves.Why: Each goal is a state the lab can check on the running device. Verify with: show bgp l2vpn evpn summary Leaf 1 sees leaf 2 as an NVE peer On each leaf map VLAN 10 to vn-segment 10010, build nve1 from loopback0 with host-reachability protocol bgp, and add the VNI under evpn with automatic RD and RTs.Why: Each goal is a state the lab can check on the running device. Verify with: show nve peers Host 1 reaches host 2 through the fabric Address the hosts in 192.168.10.0/24 and ping across.Why: Each goal is a state the lab can check on the running device. Verify with: ping 192.168.10.2 After that ping, leaf 1 holds the far host MAC learned over BGP The ping made both hosts send, their MACs travel as EVPN route type 2.Why: Each goal is a state the lab can check on the running device. Verify with: show l2route evpn mac all
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
Two leaves and a spine. OSPF carries the loopbacks, the spine reflects the L2VPN EVPN routes, and VLAN 10 is stretched over VNI 10010 so the two hosts share one subnet.
What you will be able to do
The spine holds an EVPN session to each leaf
Leaf 1 sees leaf 2 as an NVE peer
Host 1 reaches host 2 through the fabric
After that ping, leaf 1 holds the far host MAC learned over BGP
The network
Nexus 9300, Catalyst 8000V — 5 devices in all, already cabled.
Eth1/1 Eth1/1 Eth1/1 Eth1/2 Gi1 Eth1/5 Gi1 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
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
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 holds an EVPN session to each leaf 25 On SP: show bgp l2vpn evpn summary output matches 1\.1\.1\.1\s+4\s+65000. and On SP: show bgp l2vpn evpn summary output matches 2\.2\.2\.2\s+4\s+65000.
2 Leaf 1 sees leaf 2 as an NVE peer 25 On L1: show nve peers output matches 2\.2\.2\.2.
3 Host 1 reaches host 2 through the fabric 30 On H1: ping 192.168.10.2 must succeed.
4 After that ping, leaf 1 holds the far host MAC learned over BGP 20 On L1: show l2route evpn mac all output matches BGP.
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 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
inherit peer L
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
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