CCNP ENCOR lab 23 of 36
QoS with MQC: interpret, classify, mark, queue, shape and police
Read an existing HQ QoS policy the way the exam shows it, then build Bristol's: trust-boundary marking and policing, LLQ and CBWFQ on the WAN, and a hierarchical shaper that matches the 1 Mbit/s contract, all verified with live counters.
Run this lab
It needs Lite: its 3 nodes are set to 3 vCPU and 1,536 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 23 - QoS with MQC - interpret classify mark queue shape and police
- Level
- Advanced
- Time
- About 70 minutes
- Nodes need
- 3 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight's Bristol branch is moving its phones to the WAN. The provider sells Bristol a 1 Mbit/s service delivered on a gigabit port, so the router will happily send faster than the contract and the provider will drop the excess, voice included. (The rates in this lab are a tenth of a typical branch's, because these virtual routers forward only about 2 Mbit/s; the commands and percentages work the same at any speed.) HQ (R2) already has a QoS policy, and the telephony team wants you to (a) explain it and (b) build Bristol's (R1):
- Treat the LAN as untrusted: mark RTP voice (UDP 16384–32767) EF, SIP signalling (UDP/TCP 5060) CS3, and everything else default (0). Police voice to 100 kbit/s at the edge.
- On the WAN, shape to 1 Mbit/s, give EF a 10% priority queue, give CS3 10% of the remaining bandwidth, and fair-queue the rest.
PHONE is a router in host mode that generates traffic: IP SLA 10 sends a G.711-sized RTP stream to HQ's responder, and IP SLA 20 sends SIP-like UDP 5060 packets.
| Device | Interface | Address |
|---|---|---|
| PHONE | Gi0/0 | 10.20.10.20/24, gateway 10.20.10.1 |
| R1 | Gi0/0 (LAN) / Gi0/1 (WAN) | 10.20.10.1/24 / 10.0.12.1/30 |
| R2 | Gi0/1 / Lo10 | 10.0.12.2/30 / 10.10.30.1/24 (HQ servers, IP SLA responder) |
Topology: PHONE — R1 — R2.
What you’ll practise
- Interpret class maps, policy maps and service policies, including priority, bandwidth remaining, WRED and shaping
- Classify traffic with ACLs and mark it with DSCP at the trust boundary
- Police a class and read conform/exceed counters
- Build LLQ and CBWFQ inside a hierarchical shaping policy for a sub-rate WAN
- Verify every class with show policy-map interface
The tasks
- Interpret HQ's policy
- Classify and mark at the trust boundary
- Police voice at the edge
- Queue for the WAN
- Shape to the contract and apply
- Read the counters
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.
Every link, as text
- PHONE
Gi0/0to R1Gi0/0 - R1
Gi0/1to R2Gi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PHONE | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP ENCOR 350-401 guided labs.Open
23 - QoS with MQC - interpret classify mark queue shape and policeand 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 ENCOR 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.