CloudLabBox
Try the free demo

Cisco Catalyst SD-WAN CLI lab 10 of 14

QoS on the WAN edge

Classify and mark traffic at the LAN edge, schedule it with a low-latency queue and two weighted queues, and shape the WAN port to the contracted rate.

Run this lab

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

In your workspace: Shared, then Cisco Catalyst SD-WAN CLI guided labs, then 10 - QoS on the 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 60 minutes
Nodes need
6 vCPU, 5,120 MB
Smallest plan
Lite

The scenario

Manchester's WAN port is a 1 Gbps handoff on a 2 Mbps contract. Anything above 2 Mbps gets dropped by the provider, with no regard for what it is. You take control: classify at the LAN edge, mark, queue, and shape the port to the contract, so voice is protected when the line is busy. Meridian treats ICMP as voice in this lab because it is easy to generate and count.

NodeSystem IPSiteINET (ge0/0)LAN, VPN 10 (ge0/1)
BR110.255.0.1111198.51.100.1110.11.10.1/24, H1 10.11.10.10
BR210.255.0.1212198.51.100.1210.12.10.1/24, H2 10.12.10.10
ClassTrafficQueueSchedulingBandwidthDSCP
c-voiceICMP (stands in for voice)0LLQ20%46
c-businessTCP port 80801WRR40%26
c-defaulteverything else2WRR40%

What this course leaves out. There is no SD-WAN Manager (vManage) in any of these labs. A virtual edge can't join the Manager's inventory without a signed device list from Cisco, which these labs don't have. So you won't see the Manager's GUI, dashboards, templates, Policy Builder or zero-touch onboarding. You work at the CLI of the controllers and edges, with a private lab CA and device lists typed by hand. In production you'd build this as a localised policy in the Manager. Per-tunnel QoS and AppQoE need IOS XE edges and aren't in this course. The hosts have fixed addresses set at boot, because the DHCP server on these vEdge images can lock up the edge at start-up.

What you’ll practise

  • Map classes to queues
  • Mark traffic with a localized access list
  • Build a QoS map and shape a transport interface

The tasks

  1. Start the lab
  2. Map classes to queues
  3. Classify and mark at the LAN edge
  4. Build the schedulers and the map
  5. Apply it and shape
  6. Prove it

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 on the WAN edge6 nodes and 1 network, 6 links. Every link is listed as text below the diagram.vBondvSmartBR1BR2H1H2INETG0/1eth0G0/1eth0ge0/0eth0G0/0G0/0
6 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • vBond ge0/0 to INET (network)
  • vSmart eth0 to INET (network)
  • BR1 G0/0 to INET (network)
  • BR2 G0/0 to INET (network)
  • BR1 G0/1 to H1 eth0
  • BR2 G0/1 to H2 eth0
Nodes in QoS on the WAN edge, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
vBondCisco vBondvtbond-20.12.21 vCPU, 1,024 MB
vSmartCisco vSmartvtsmart-20.12.21 vCPU, 1,024 MB
BR1Cisco vEdgevtedge-20.12.21 vCPU, 1,024 MB
BR2Cisco vEdgevtedge-20.12.21 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 Cisco Catalyst SD-WAN CLI guided labs.

  3. Open 10 - QoS on the 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 Cisco Catalyst SD-WAN CLI labs

All Cisco Catalyst SD-WAN CLI 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.