zNetLaB › Guided labs › Service Provider
Segment routing: Nokia SR OS with IOS XE in the middle
Service Provider Advanced 3 devices 4 checked tasks 100 points Plan lab
Two Nokia 7750 SR-1 routers and a Catalyst 8000V in one IS-IS level-2 domain. Give each loopback a node index in the 16000 block and send traffic from A to C on a 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 Nokia 7750 SR-1 routers and a Catalyst 8000V in one IS-IS level-2 domain. Give each loopback a node index in the 16000 block and send traffic from A to C on a 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. A, X, C 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
A lists the node SIDs of all three routers (30 pts) A has an SR tunnel to C through X (25 pts) X pops the labels of its two neighbours (20 pts) A reaches C system address (25 pts)
The activity, in order
A lists the node SIDs of all three routers On A and C: the system address, port 1/1/1 and the core interface, mpls-labels sr-labels 16000-23999, IS-IS level 2 with segment-routing enabled and an ipv4-node-sid index on system. On X: IS-IS level-2-only with segment-routing mpls and 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 router isis prefix-sids A has an SR tunnel to C through X The tunnel table fills from the prefix SIDs once IS-IS has them.Why: Each goal is a state the lab can check on the running device. Verify with: show router tunnel-table X pops the labels of its two neighbours X is the last hop before A and C, so it removes their labels.Why: Each goal is a state the lab can check on the running device. Verify with: show mpls forwarding-table A reaches C system address Ping 3.3.3.3 from A once the tunnel is there.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 Nokia 7750 SR-1 routers and a Catalyst 8000V in one IS-IS level-2 domain. Give each loopback a node index in the 16000 block and send traffic from A to C on a label.
What you will be able to do
A lists the node SIDs of all three routers
A has an SR tunnel to C through X
X pops the labels of its two neighbours
A reaches C system address
The network
Nokia 7750 SR-1, Catalyst 8000V — 3 devices in all, already cabled.
1/1/1 Gi1 Gi2 1/1/1 A X C Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
A Nokia 7750 SR-1 configure it
X Catalyst 8000V configure it
C Nokia 7750 SR-1 configure it
Cabling
A 1/1/1 ↔ X Gi1
X Gi2 ↔ C 1/1/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 A lists the node SIDs of all three routers 30 On A: show router isis prefix-sids output matches No\. of Prefix/SIDs: 3.
2 A has an SR tunnel to C through X 25 On A: show router tunnel-table output matches 3\.3\.3\.3/32\s+isis \(0\)\s+MPLS.
3 X pops the labels of its two neighbours 20 On X: show mpls forwarding-table output matches 16001\s+Pop Label. and On X: show mpls forwarding-table output matches 16003\s+Pop Label.
4 A reaches C system address 25 On A: 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:
A edit-config private
configure router router-id 1.1.1.1
configure router interface "system" ipv4 primary address 1.1.1.1 prefix-length 32
configure port 1/1/1 admin-state enable
configure router interface "core" port 1/1/1
configure router interface "core" ipv4 primary address 10.0.12.1 prefix-length 30
configure router mpls-labels sr-labels start 16000 end 23999
configure router isis 0 admin-state enable
configure router isis 0 area-address 49.0001
configure router isis 0 level-capability 2
configure router isis 0 advertise-router-capability as
configure router isis 0 traffic-engineering true
configure router isis 0 segment-routing admin-state enable
configure router isis 0 segment-routing prefix-sid-range global
configure router isis 0 interface "system" passive true
configure router isis 0 interface "system" ipv4-node-sid index 1
configure router isis 0 interface "core" interface-type point-to-point
commit
quit-config
C edit-config private
configure router router-id 3.3.3.3
configure router interface "system" ipv4 primary address 3.3.3.3 prefix-length 32
configure port 1/1/1 admin-state enable
configure router interface "core" port 1/1/1
configure router interface "core" ipv4 primary address 10.0.23.2 prefix-length 30
configure router mpls-labels sr-labels start 16000 end 23999
configure router isis 0 admin-state enable
configure router isis 0 area-address 49.0001
configure router isis 0 level-capability 2
configure router isis 0 advertise-router-capability as
configure router isis 0 traffic-engineering true
configure router isis 0 segment-routing admin-state enable
configure router isis 0 segment-routing prefix-sid-range global
configure router isis 0 interface "system" passive true
configure router isis 0 interface "system" ipv4-node-sid index 3
configure router isis 0 interface "core" interface-type point-to-point
commit
quit-config
X 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