MikroTik MTCTCE lab 8 of 8
Capstone: ISP subscriber shaping with plans, PCQ and a voice class
Fernvale's Riverside access point sells two plans, Bronze and Silver, and carries a voice service that must come first. Its download shaping was set up in a hurry and three faults let one customer run unshaped, make Bronze customers share a single rate, and starve voice of its class. Find and fix them, then build the missing upload shaping, and prove every plan with measurements.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 1,280 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCTCE RouterOS v7 guided labs, then 08 - Capstone - ISP subscriber shaping with plans PCQ and a voice class
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 5 vCPU, 1,280 MB
- Smallest plan
- Lite
The scenario
Fernvale's Riverside access point (AP) sells two plans, and carries a voice service:
| Plan | Download | Upload | Subscribers |
|---|---|---|---|
| Bronze | 256k each | 128k each | SUB1 (192.168.50.11), SUB3 (192.168.50.13) |
| Silver | 512k each | 256k each | SUB2 (192.168.50.12) |
| Voice | 128k guaranteed, up to 256k, before anything else | SUB3's calls, marked DSCP 46 by the voice provider |
The download side was configured in a hurry: address lists per plan, a mangle mark per plan, and a queue tree down on ether2 with a PCQ leaf per plan and a voice leaf. Upload shaping was never built. Customers complain: the Silver customer is "unbelievably fast", the two Bronze customers slow each other down, and SUB3's calls stutter when SUB3 downloads.
Small rates are used because of the CHR licence (lab 2 explains); the design is the same at real speeds.
| Device | Address |
|---|---|
| NET (Internet, voice provider, bandwidth-test server) | 192.0.2.1/30 |
| AP | ether1 192.0.2.2/30 (backhaul) · ether2 192.168.50.1/24 (subscribers) |
| SUB1 · SUB2 · SUB3 | 192.168.50.11 · .12 · .13 |
For every measurement in this lab use:
:local r [/tool bandwidth-test address=192.0.2.1 direction=receive protocol=tcp duration=10s as-value]; :put ("rx=" . (($r->"rx-total-average") / 1000) . "k")(direction=transmit and tx-total-average for uploads; protocol=udp on SUB3 to send "voice").
What you’ll practise
- Design per-plan shaping with address lists, mangle marks, an HTB tree and PCQ leaves
- Troubleshoot a subscriber missing from its plan, a PCQ classifier and the order of mangle rules
- Give a DSCP-marked voice class priority within the tree
- Build upload shaping on the uplink interface with the right classifiers
- Verify each plan's download and upload rate with measurements
The tasks
- Measure each complaint
- Find and fix the three download faults
- Build upload shaping
- Prove every plan
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
- NET
ether1to APether1 - AP
ether2to Subscribers (network) - SUB1
ether1to Subscribers (network) - SUB2
ether1to Subscribers (network) - SUB3
ether1to Subscribers (network)
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| NET | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| AP | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| SUB1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| SUB2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| SUB3 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCTCE RouterOS v7 guided labs.Open
08 - Capstone - ISP subscriber shaping with plans PCQ and a voice classand 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
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.