zNetLaB › Guided labs › Service Provider
Segment routing across Junos and IOS XE
Service Provider Advanced 3 devices 4 checked tasks 100 points Plan lab
Two vMX routers with a Catalyst 8000V between them in one IS-IS level-2 domain. Give every loopback a node index in the shared block starting at 16000 so each router reaches the others by label. 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 vMX routers with a Catalyst 8000V between them in one IS-IS level-2 domain. Give every loopback a node index in the shared block starting at 16000 so each router reaches the others by label.
Your role: an engineer in the provider’s network operations centre. Level: Advanced Done when: all 4 goals show as passed (100 points).
Network status
Devices: 3 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. J1, X2, J3 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
J1 has an IS-IS adjacency to X2 (15 pts) J1 pushes label 16003 to reach J3 (30 pts) J1 pops 16002 towards its neighbour X2 (25 pts) J1 reaches J3 loopback (30 pts)
The activity, in order
J1 has an IS-IS adjacency to X2 On the vMXs: family inet, iso and mpls on ge-0/0/0.0, an iso address on lo0, IS-IS point-to-point with level 1 disabled. On X2: ip router isis on both links and the loopback, level-2-only, metric-style wide.Why: Each goal is a state the lab can check on the running device. Verify with: show isis adjacency J1 pushes label 16003 to reach J3 Under protocols isis source-packet-routing set srgb start-label 16000 index-range 8000 and node-segment ipv4-index 1 and 3.Why: Each goal is a state the lab can check on the running device. Verify with: show route table inet.3 J1 pops 16002 towards its neighbour X2 On X2 enable segment-routing mpls under router isis and give 2.2.2.2/32 index 2 in the connected-prefix-sid-map.Why: Each goal is a state the lab can check on the running device. Verify with: show route table mpls.0 J1 reaches J3 loopback Once the labels are in place, ping 3.3.3.3 from J1.Why: Each goal is a state the lab can check on the running device. Verify with: ping 3.3.3.3
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 vMX routers with a Catalyst 8000V between them in one IS-IS level-2 domain. Give every loopback a node index in the shared block starting at 16000 so each router reaches the others by label.
What you will be able to do
J1 has an IS-IS adjacency to X2
J1 pushes label 16003 to reach J3
J1 pops 16002 towards its neighbour X2
J1 reaches J3 loopback
The network
vMX, Catalyst 8000V — 3 devices in all, already cabled.
ge-0/0/0 Gi1 Gi2 ge-0/0/0 J1 X2 J3 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
J1 vMX configure it
X2 Catalyst 8000V configure it
J3 vMX configure it
Cabling
J1 ge-0/0/0 ↔ X2 Gi1
X2 Gi2 ↔ J3 ge-0/0/0
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 J1 has an IS-IS adjacency to X2 15 On J1: show isis adjacency output matches X2\s+2\s+Up.
2 J1 pushes label 16003 to reach J3 30 On J1: show route table inet.3 output matches 3\.3\.3\.3/32[\s\S]*?Push 16003.
3 J1 pops 16002 towards its neighbour X2 25 On J1: show route table mpls.0 output matches 16002\s+\*\[L-ISIS/14\][\s\S]*?Pop.
4 J1 reaches J3 loopback 30 On J1: ping 3.3.3.3 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:
J1 configure
set interfaces ge-0/0/0 unit 0 family inet address 10.0.12.1/30
set interfaces ge-0/0/0 unit 0 family iso
set interfaces ge-0/0/0 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 1.1.1.1/32
set interfaces lo0 unit 0 family iso address 49.0001.0000.0000.0001.00
set protocols isis interface ge-0/0/0.0 point-to-point
set protocols isis interface lo0.0 passive
set protocols isis level 1 disable
set protocols mpls interface all
set protocols isis source-packet-routing srgb start-label 16000 index-range 8000
set protocols isis source-packet-routing node-segment ipv4-index 1
commit
exit
J3 configure
set interfaces ge-0/0/0 unit 0 family inet address 10.0.23.2/30
set interfaces ge-0/0/0 unit 0 family iso
set interfaces ge-0/0/0 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 3.3.3.3/32
set interfaces lo0 unit 0 family iso address 49.0001.0000.0000.0003.00
set protocols isis interface ge-0/0/0.0 point-to-point
set protocols isis interface lo0.0 passive
set protocols isis level 1 disable
set protocols mpls interface all
set protocols isis source-packet-routing srgb start-label 16000 index-range 8000
set protocols isis source-packet-routing node-segment ipv4-index 3
commit
exit
X2 interface Loopback0
ip address 2.2.2.2 255.255.255.255
ip router isis
exit
interface GigabitEthernet1
ip address 10.0.12.2 255.255.255.252
ip router isis
isis network point-to-point
no shutdown
exit
interface GigabitEthernet2
ip address 10.0.23.1 255.255.255.252
ip router isis
isis network point-to-point
no shutdown
exit
router isis
net 49.0001.0000.0000.0002.00
is-type level-2-only
metric-style wide
segment-routing mpls
exit
segment-routing mpls
connected-prefix-sid-map
address-family ipv4
2.2.2.2/32 index 2 range 1
exit-address-family
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