CloudLabBox
Try the free demo

CCNA lab 30 of 46

QoS per-hop behaviour on a WAN edge

Protect voice on a congested branch link: classify and mark traffic at the edge, give voice a priority queue and video a bandwidth guarantee, shape the WAN to the provider's rate, police on the far side, and read the counters while iperf fills the pipe.

Run this lab

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

In your workspace: Shared, then CCNA 200-301 guided labs, then 30 - QoS per-hop behaviour on a WAN edge

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 50 minutes
Nodes need
5 vCPU, 4,096 MB
Smallest plan
Lite

The scenario

Ashcombe Surveyors' branch office (R1) shares a 1 Mb/s WAN service to head office (R2) between IP phones and everything else. Every afternoon, when people sync large files, calls break up. You'll mark traffic as it enters R1, queue it on the WAN so voice always goes first, shape to the provider's rate, and police at HQ, then fill the link with iperf and watch the counters.

DeviceInterfaceAddress
R1Gi0/0 (WAN) / Gi0/1 (voice LAN) / Gi0/2 (data LAN)10.0.12.1/30 / 10.30.1.1/24 / 10.30.2.1/24
R2Gi0/0 (WAN) / Gi0/1 (servers)10.0.12.2/30 / 10.30.9.1/24
PC1voice LAN ("IP phone")10.30.1.10
H1data LAN (iperf client)10.30.2.10 (you set it)
H2servers (iperf server)10.30.9.100 (you set it)

Exam versions. QoS per-hop behaviour is a v1.1 topic (4.7). v2.0 dropped it as a separate topic but still expects you to configure ports for IP phones (2.2.c), whose traffic relies on these markings.

What you’ll practise

  • Explain classification, marking (CoS and DSCP), queuing, congestion avoidance, policing and shaping
  • Classify traffic with class-maps and mark it with an input policy
  • Build an LLQ/CBWFQ output policy under a hierarchical shaper
  • Police traffic and compare policing with shaping
  • Verify QoS behaviour with show policy-map interface while generating traffic

The tasks

  1. Learn the per-hop behaviours
  2. Prepare the hosts and measure the baseline
  3. Classify and mark at the edge
  4. Queue on the WAN
  5. Shape to the provider's rate
  6. Police at head office
  7. Load the link and 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.

Topology of QoS per-hop behaviour on a WAN edge5 nodes, 4 links. Every link is listed as text below the diagram.R1R2PC1H1H2Gi0/1eth0Gi0/1eth0Gi0/2eth0Gi0/0Gi0/0
5 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • R1 Gi0/0 to R2 Gi0/0
  • R1 Gi0/1 to PC1 eth0
  • R1 Gi0/2 to H1 eth0
  • R2 Gi0/1 to H2 eth0
Nodes in QoS per-hop behaviour on a WAN edge, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
R1Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
R2Cisco IOSvvios-adventerprisek9-m.SPA.159-3.M61 vCPU, 1,024 MB
PC1VPCS hostBuilt in to EVE-NGCounted as 1 vCPU, 1,024 MB
H1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
H2Alpine 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 CCNA 200-301 guided labs.

  3. Open 30 - QoS per-hop behaviour on a WAN edge 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 CCNA labs

All CCNA 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.