MikroTik MTCTCE lab 2 of 8

Simple queues: limits, parents, order and burst

Share Fernvale's Riverside office uplink between two staff PCs with simple queues: per-PC limits in both directions, a parent queue for the whole office, the first-match order that decides which queue a packet uses, and burst, which makes short downloads feel fast without raising the long-term rate. Every rate is measured with RouterOS's own bandwidth test.

Run this lab

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

In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 02 - Simple queues - limits parents order and burst

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
Intermediate
Time
About 60 minutes
Nodes need
4 vCPU, 1,024 MB
Smallest plan
Lite

The scenario

Fernvale's Riverside office has two staff PCs behind its router, and a small uplink that one big download can fill. You'll share it with simple queues: a limit per PC, a parent queue for the whole office, and burst so that short downloads finish quickly.

About the rates in this course. Our virtual routers run RouterOS's free licence, which caps each interface at about 1 Mbit/s. So every rate is in kbit/s, well under that cap; the configuration is the same as at 100 Mbit/s. Measured rates come out a few per cent under the configured limit, and vary a little from run to run.

DeviceAddressRole
NET192.0.2.1/30the Internet, with a bandwidth-test server (no login needed)
RIVERSIDEether1 192.0.2.2/30 · ether2 192.168.50.1/24the office router, where the queues live
PC1 · PC2192.168.50.11 · 192.168.50.12RouterOS routers playing staff PCs

What you’ll practise

  • Read a simple queue's target, max-limit and limit-at, and which value is upload and which is download
  • Measure a queue's effect with /tool bandwidth-test
  • Build a parent queue and child queues, and explain the first-match order of simple queues
  • Configure burst-limit, burst-threshold and burst-time, and predict how long a burst lasts

The tasks

  1. Measure before you shape
  2. A queue per PC
  3. A parent queue for the office
  4. Queue order: the first match wins
  5. Burst

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 Simple queues - limits parents order and burst4 nodes and 1 network, 4 links. Every link is listed as text below the diagram.NETRIVERSIDEPC1PC2Officeether2ether1ether1ether1ether1
4 nodes and 1 network, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in Simple queues: limits, parents, order and burst, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
NETMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
RIVERSIDEMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PC2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 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 MikroTik MTCTCE RouterOS v7 guided labs.

  3. Open 02 - Simple queues - limits parents order and burst 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 MikroTik MTCTCE labs

All MikroTik MTCTCE labs

Related labs in other courses

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