CloudLabBox
Try the free demo

Nokia SR OS NRS I lab 13 of 14

Troubleshooting services

Two customers down: find five provisioning faults in an Epipe and a VPRN, using service flags, OAM and BGP output.

Run this lab

It needs Standard: its 6 nodes are set to 8 vCPU and 11,648 MB in total.

In your workspace: Shared, then Nokia SR OS NRS I guided labs, then 13 - Troubleshooting services

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 8 vCPU and 11,648 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
8 vCPU, 11,648 MB
Smallest plan
Standard

The scenario

Rivermark's core is healthy: OSPF, LDP and BGP are all up between R1 and R2. But two customers have called the same morning.

Alder Foods says its Ethernet link between H1 and H2 has stopped working. Cedar Mutual says A1 can't reach A2 over its VPRN. The two tickets were both caused by a junior engineer's rushed provisioning run, and there are five faults in all, spread across R1 and R2. Fix them and prove each service works.

DeviceInterfacePortAddressConnects to
R1system-10.255.0.1/32
R1to-R21/1/c1/110.0.12.1/30R2
R2system-10.255.0.2/32
R2to-R11/1/c1/110.0.12.2/30R1
H1eth0-172.16.10.1/24R1
H2eth0-172.16.10.2/24R2
A1eth0-172.16.1.10/24 (gateway 172.16.1.1)R1
A2eth0-172.16.2.10/24 (gateway 172.16.2.1)R2

What you’ll practise

  • Read SDP and binding state and flags
  • Compare two ends of a service with svc-ping
  • Fix VC ID, far-end and MTU faults
  • Fix route target and tunnel binding faults in a VPRN

The tasks

  1. Start with what the service says
  2. Fix the Epipe
  3. Fix the VPRN

The Lab Tasks pane has the scenario, these tasks, the checks to run, hints and the full solution.

Topology and devices

The network as it opens in EVE-NG, drawn from the lab’s own canvas, and the image each node runs.

Topology of Troubleshooting services6 nodes, 5 links. Every link is listed as text below the diagram.R1R2H1H2A1A2p1/1/2eth0p1/1/2eth0p1/1/3eth0p1/1/3eth0p1/1/1p1/1/1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 p1/1/1 to R2 p1/1/1
  • R1 p1/1/2 to H1 eth0
  • R2 p1/1/2 to H2 eth0
  • R1 p1/1/3 to A1 eth0
  • R2 p1/1/3 to A2 eth0
Nodes in Troubleshooting services, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Nokia Integrated router (VSR NG template)timos-ng-21.10.R12 vCPU, 4,800 MB
R2Nokia Integrated router (VSR NG template)timos-ng-21.10.R12 vCPU, 4,800 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
A1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
A2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder Nokia SR OS NRS I guided labs.

  3. Open 13 - Troubleshooting services and start its nodes, then open Lab Tasks for the scenario and the steps.

The lab is read-only. You can start the nodes and configure the devices, but changes to the topology can’t be saved. To change it, rebuild it in your own folder.

More Nokia SR OS NRS I labs

All Nokia SR OS NRS I labs

Related labs in other courses

CloudLabBox is independent of Nokia. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.