zNetLaB › Guided labs › Data Center
Junos EVPN: symmetric IRB and type-5 between two subnets
Data Center Advanced 4 devices 3 checked tasks 100 points Plan lab
Two vQFX leaves with a different VLAN and subnet behind each. Put each IRB in VRF T and carry the VRF over L3VNI 50001 so the hosts route to each other across the fabric. 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 vQFX leaves with a different VLAN and subnet behind each. Put each IRB in VRF T and carry the VRF over L3VNI 50001 so the hosts route to each other across the fabric.
Your role: a network engineer. Level: Advanced Done when: all 3 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, gateway 192.168.10.1. H2 is a host with 192.168.20.12/24, gateway 192.168.20.1. L1, L2 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
L1 exports its subnet as a type-5 route (25 pts) L1 holds the far subnet in T.inet.0 from EVPN (30 pts) H1 reaches H2 in the other subnet (45 pts)
The activity, in order
L1 exports its subnet as a type-5 route Build the EVPN underlay and overlay as in the L2 lab, add irb.10 (L1) or irb.20 (L2) as the l3-interface of the VLAN, and a routing-instance T of type vrf holding the irb, with an RD, vrf-target target:65000:5001 and protocols evpn ip-prefix-routes advertise direct-nexthop, encapsulation vxlan, vni 50001.Why: Each goal is a state the lab can check on the running device. Verify with: show evpn ip-prefix-database L1 holds the far subnet in T.inet.0 from EVPN With the same vrf-target on both leaves, each imports the other type-5 route into T.Why: Each goal is a state the lab can check on the running device. Verify with: show route table T.inet.0 H1 reaches H2 in the other subnet The hosts use their own IRB as gateway; L1 routes into L3VNI 50001 towards L2.Why: Each goal is a state the lab can check on the running device. Verify with: ping 192.168.20.12
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 vQFX leaves with a different VLAN and subnet behind each. Put each IRB in VRF T and carry the VRF over L3VNI 50001 so the hosts route to each other across the fabric.
What you will be able to do
L1 exports its subnet as a type-5 route
L1 holds the far subnet in T.inet.0 from EVPN
H1 reaches H2 in the other subnet
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 · gw 192.168.10.1 H2 192.168.20.12/24 · gw 192.168.20.1 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 gw 192.168.10.1
H2 PC 192.168.20.12 / 255.255.255.0 gw 192.168.20.1
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
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 L1 exports its subnet as a type-5 route 25 On L1: show evpn ip-prefix-database output matches 192\.168\.10\.0/24 +Created.
2 L1 holds the far subnet in T.inet.0 from EVPN 30 On L1: show route table T.inet.0 output matches 192\.168\.20\.0/24\s+\*\[EVPN/170\].
3 H1 reaches H2 in the other subnet 45 On H1: ping 192.168.20.12 must succeed.
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:
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
set vlans V10 l3-interface irb.10
set interfaces irb unit 10 family inet address 192.168.10.1/24
set routing-instances T instance-type vrf
set routing-instances T interface irb.10
set routing-instances T route-distinguisher 10.255.0.1:100
set routing-instances T vrf-target target:65000:5001
set routing-instances T protocols evpn ip-prefix-routes advertise direct-nexthop
set routing-instances T protocols evpn ip-prefix-routes encapsulation vxlan
set routing-instances T protocols evpn ip-prefix-routes vni 50001
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 V20
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:10
set protocols evpn encapsulation vxlan
set protocols evpn extended-vni-list all
set vlans V20 vlan-id 20
set vlans V20 vxlan vni 10020
set vlans V20 l3-interface irb.20
set interfaces irb unit 20 family inet address 192.168.20.1/24
set routing-instances T instance-type vrf
set routing-instances T interface irb.20
set routing-instances T route-distinguisher 10.255.0.2:100
set routing-instances T vrf-target target:65000:5001
set routing-instances T protocols evpn ip-prefix-routes advertise direct-nexthop
set routing-instances T protocols evpn ip-prefix-routes encapsulation vxlan
set routing-instances T protocols evpn ip-prefix-routes vni 50001
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