CCNP Service Provider lab 12 of 23

SR-TE policies, explicit paths and binding SIDs

Send traffic off the IGP path with segment routing. Build an SR policy with an explicit segment list and a binding SID, steer with a tunnel, and use the binding SID from another router.

Run this lab

It needs Standard: its 4 nodes are set to 4 vCPU and 10,240 MB in total.

In your workspace: Shared, then CCNP Service Provider guided labs, then 12 - SR-TE policies explicit paths and binding SIDs

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 4 vCPU and 10,240 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 75 minutes
Nodes need
4 vCPU, 10,240 MB
Smallest plan
Standard

The scenario

Fellgate Carrier's main path from R1 to R4 goes through R2. R3 is on a longer, lower-latency route that the IGP doesn't choose, and the product team wants one traffic class to use it. On a classic core that would mean RSVP-TE, with state on every router along the path. With SR-TE, only the headend knows there's a path: it writes the route into the label stack.

The four routers run IS-IS with SR, and MPLS TE is enabled, so tunnels can be built.

What this release can't do. XRv 6.3 builds SR policies and binding SIDs, but it doesn't steer BGP routes into a policy by colour, and a policy has no autoroute. So this lab steers with tunnel-te and with a binding SID. It also refuses an explicit binding SID inside the default local block, 15000 to 15999: the policy shows Error: already assigned, because the label manager holds that block. So this lab takes 30100 from the dynamic range. Colour and on-demand next hop (ODN) are described as concepts.

DeviceInterfaceAddressConnects to
R1Loopback010.255.0.1/32
R1Gi0/0/0/010.0.12.1/30R2 Gi0/0/0/0
R1Gi0/0/0/110.0.13.1/30R3 Gi0/0/0/0
R2Loopback010.255.0.2/32
R2Gi0/0/0/010.0.12.2/30R1 Gi0/0/0/0
R2Gi0/0/0/110.0.24.1/30R4 Gi0/0/0/0
R3Loopback010.255.0.3/32
R3Gi0/0/0/010.0.13.2/30R1 Gi0/0/0/1
R3Gi0/0/0/110.0.34.1/30R4 Gi0/0/0/1
R4Loopback010.255.0.4/32
R4Gi0/0/0/010.0.24.2/30R2 Gi0/0/0/1
R4Gi0/0/0/110.0.34.2/30R3 Gi0/0/0/1

What you’ll practise

  • Name the parts of an SR policy
  • Build an explicit segment list and a policy on IOS XR
  • Steer traffic with a tunnel-te SR path and autoroute
  • Use a binding SID from an upstream router
  • Explain colour, on-demand next hop and PCE

The tasks

  1. An SR policy
  2. Steer traffic with a tunnel
  3. Use the binding SID from another router
  4. Colour and on-demand next hop

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 SR-TE policies explicit paths and binding SIDs4 nodes, 4 links. Every link is listed as text below the diagram.R1R2R3R4Gi0/0/0/0Gi0/0/0/0Gi0/0/0/1Gi0/0/0/0Gi0/0/0/1Gi0/0/0/0Gi0/0/0/1Gi0/0/0/1
4 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in SR-TE policies, explicit paths and binding SIDs, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R2Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R3Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
R4Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 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 CCNP Service Provider guided labs.

  3. Open 12 - SR-TE policies explicit paths and binding SIDs 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 CCNP Service Provider labs

All CCNP Service Provider labs

Related labs in other courses

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