zNetLaB › Guided labs › Data Center
Troubleshoot: Junos EVPN routes that are thrown away
Data Center Advanced 4 devices 2 checked tasks 100 points Plan lab
The iBGP EVPN session between the two vQFX leaves is established, but the hosts cannot talk and neither leaf lists the other as a VTEP. 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 iBGP EVPN session between the two vQFX leaves is established, but the hosts cannot talk and neither leaf lists the other as a VTEP.
Your role: a network engineer. Level: Advanced Done when: all 2 goals show as passed (100 points).
Network status
Devices: 2 routers, 2 PCs, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. H1 is a host with 192.168.10.11/24. H2 is a host with 192.168.10.12/24. L1, L2 start with an empty configuration.
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
Leaf 1 lists leaf 2 as a remote VTEP (40 pts) Host 1 reaches host 2 (60 pts)
The activity, in order
Leaf 1 lists leaf 2 as a remote VTEP L2 exports and imports target:65000:99, L1 uses target:65000:10. Set the same vrf-target on L2.Why: Each goal is a state the lab can check on the running device. Verify with: show ethernet-switching vxlan-tunnel-end-point remote Host 1 reaches host 2 Once the routes are imported the MACs are learned across the fabric.Why: Each goal is a state the lab can check on the running device. Verify with: show evpn database
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 iBGP EVPN session between the two vQFX leaves is established, but the hosts cannot talk and neither leaf lists the other as a VTEP.
What you will be able to do
Leaf 1 lists leaf 2 as a remote VTEP
Host 1 reaches host 2
The network
vQFX, PC — 4 devices in all, already cabled.
xe-0/0/0 xe-0/0/0 Fa0 xe-0/0/1 Fa0 xe-0/0/1 L1 L2 H1 192.168.10.11/24 H2 192.168.10.12/24 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
L1 vQFX configure it
L2 vQFX configure it
H1 PC 192.168.10.11 / 255.255.255.0
H2 PC 192.168.10.12 / 255.255.255.0
Cabling
L1 xe-0/0/0 ↔ L2 xe-0/0/0
H1 Fa0 ↔ L1 xe-0/0/1
H2 Fa0 ↔ L2 xe-0/0/1
What is configured at the start
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
L1 configure
set interfaces xe-0/0/0 unit 0 family inet address 10.0.0.1/30
set interfaces lo0 unit 0 family inet address 10.255.0.1/32
set interfaces xe-0/0/1 unit 0 family ethernet-switching interface-mode access
set interfaces xe-0/0/1 unit 0 family ethernet-switching vlan members V10
set routing-options autonomous-system 65000
set routing-options router-id 10.255.0.1
set protocols ospf area 0.0.0.0 interface xe-0/0/0.0
set protocols ospf area 0.0.0.0 interface lo0.0 passive
set protocols bgp group OVL type internal
set protocols bgp group OVL local-address 10.255.0.1
set protocols bgp group OVL family evpn signaling
set protocols bgp group OVL neighbor 10.255.0.2
set switch-options vtep-source-interface lo0.0
set switch-options route-distinguisher 10.255.0.1:1
set switch-options vrf-target target:65000:10
set protocols evpn encapsulation vxlan
set protocols evpn extended-vni-list all
set vlans V10 vlan-id 10
set vlans V10 vxlan vni 10010
commit
exit
L2 configure
set interfaces xe-0/0/0 unit 0 family inet address 10.0.0.2/30
set interfaces lo0 unit 0 family inet address 10.255.0.2/32
set interfaces xe-0/0/1 unit 0 family ethernet-switching interface-mode access
set interfaces xe-0/0/1 unit 0 family ethernet-switching vlan members V10
set routing-options autonomous-system 65000
set routing-options router-id 10.255.0.2
set protocols ospf area 0.0.0.0 interface xe-0/0/0.0
set protocols ospf area 0.0.0.0 interface lo0.0 passive
set protocols bgp group OVL type internal
set protocols bgp group OVL local-address 10.255.0.2
set protocols bgp group OVL family evpn signaling
set protocols bgp group OVL neighbor 10.255.0.1
set switch-options vtep-source-interface lo0.0
set switch-options route-distinguisher 10.255.0.2:1
set switch-options vrf-target target:65000:99
set protocols evpn encapsulation vxlan
set protocols evpn extended-vni-list all
set vlans V10 vlan-id 10
set vlans V10 vxlan vni 10010
commit
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 Leaf 1 lists leaf 2 as a remote VTEP 40 On L1: show ethernet-switching vxlan-tunnel-end-point remote output matches 10\.255\.0\.2.
2 Host 1 reaches host 2 60 On H1: ping 192.168.10.12 must succeed. and On L1: show evpn database output matches 10\.255\.0\.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:
L2 configure
set switch-options vrf-target target:65000:10
commit
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