CloudLabBox
Try the free demo

CCNP Service Provider lab 19 of 23

QoS services: marking, policing, queuing and MPLS models

Mark a customer's voice traffic at the edge, police it to the contract, prove the EXP value in the core, give it priority towards the core, and compare the MPLS QoS models.

Run this lab

It needs Lite: its 5 nodes are set to 5 vCPU and 6,144 MB in total. That fits the free demo too.

In your workspace: Shared, then CCNP Service Provider guided labs, then 19 - QoS services - marking policing queuing and MPLS models

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Advanced
Time
About 60 minutes
Nodes need
5 vCPU, 6,144 MB
Smallest plan
Lite

The scenario

A Fellgate Carrier customer runs voice between two sites, and Fellgate has sold it a priority class. Your job is to recognise that traffic at the edge, mark it in a way the MPLS core can see, police it to the contracted rate, and give it priority on the way into the core.

PE1 runs IOS XE, and P, PE2, CE1 and CE2 run IOSv. OSPF and LDP are up. Here, ICMP between the two site LANs stands in for voice.

Why IOS XE here. On this XRv image, a service policy on an interface won't install, so QoS has to use the CSR and IOSv. IOSv forwards about 2 Mbps, so the rates in this lab are low. The MQC syntax on XR is almost the same, with policy-map and service-policy.

DeviceInterfaceAddressConnects to
CE1Loopback1192.168.1.1/24
CE1Gi0/0172.16.1.2/30PE1 Gi2
PE1Loopback010.255.0.1/32
PE1Gi110.0.12.1/30P Gi0/0
PE1Gi2172.16.1.1/30CE1 Gi0/0
PLoopback010.255.0.2/32
PGi0/010.0.12.2/30PE1 Gi1
PGi0/110.0.23.1/30PE2 Gi0/0
PE2Loopback010.255.0.3/32
PE2Gi0/010.0.23.2/30P Gi0/1
PE2Gi0/1172.16.2.1/30CE2 Gi0/0
CE2Loopback1192.168.2.1/24
CE2Gi0/0172.16.2.2/30PE2 Gi0/1

What you’ll practise

  • Classify and mark with DSCP and MPLS EXP
  • Police to a contracted rate
  • Prove a marking on the next router
  • Build priority queuing with a shaped default class
  • Compare the uniform, pipe and short pipe models
  • Hide the core from a customer traceroute

The tasks

  1. Trust boundaries and where marking happens
  2. Classify, mark and police at the edge
  3. Prove the marking in the core
  4. Queue and shape towards the core
  5. MPLS QoS models

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 QoS services - marking policing queuing and MPLS models5 nodes, 4 links. Every link is listed as text below the diagram.CE1PE1PPE2CE2Gi0/0Gi2Gi1Gi0/0Gi0/1Gi0/0Gi0/1Gi0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CE1 Gi0/0 to PE1 Gi2
  • PE1 Gi1 to P Gi0/0
  • P Gi0/1 to PE2 Gi0/0
  • PE2 Gi0/1 to CE2 Gi0/0
Nodes in QoS services: marking, policing, queuing and MPLS models, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE1Cisco CSR 1000vcsr1000vng-universalk9.17.03.08a-serial1 vCPU, 4,096 MB
PCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 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 CCNP Service Provider guided labs.

  3. Open 19 - QoS services - marking policing queuing and MPLS models 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.