MikroTik MTCINE lab 11 of 12
Traffic engineering with RSVP-TE - static and CSPF paths
Fernvale's IGP sends everything over the south path while the north path sits idle. Advertise link bandwidth with OSPF TE, build an RSVP-TE tunnel on an explicit path with a reservation for a broadcaster's VPLS, watch the pseudowire move onto it, then let CSPF place more tunnels and refuse one that doesn't fit.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 1,536 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCINE RouterOS v7 guided labs, then 11 - Traffic engineering with RSVP-TE - static and CSPF paths
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 6 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
Kestrel Media, a regional broadcaster, rents a layer 2 contribution link from its studio (CE1, on PE1) to its transmitter site (CE4, on PE4). It is an LDP VPLS (lab 7), and it already works. Kestrel's contract says 10 Mbit/s guaranteed, on a path kept away from Fernvale's busy south links. Today OSPF sends everything, Kestrel included, over the south path (cost 1 per link), and the north path (cost 10) is idle. You'll fix that with RSVP-TE.
| Router | Loopback | North link | South link |
|---|---|---|---|
| PE1 | 10.255.255.1 | ether1 10.0.12.1/30 to P2 | ether2 10.0.13.1/30 to P3 |
| P2 | 10.255.255.2 | ether1 10.0.12.2/30, ether2 10.0.24.1/30 | |
| P3 | 10.255.255.3 | ether1 10.0.13.2/30, ether2 10.0.34.1/30 | |
| PE4 | 10.255.255.4 | ether1 10.0.24.2/30 to P2 | ether2 10.0.34.2/30 to P3 |
Every core link counts as 100 Mbit/s for traffic engineering.
What you’ll practise
- Explain what traffic engineering adds to IGP routing: constraints, explicit paths and reservations
- Advertise TE link information with /mpls traffic-eng interface and OSPF TE extensions
- Build RSVP-TE tunnels on a static explicit path and on a dynamic CSPF path
- Read tunnel, RSVP flow and remaining-bandwidth state, and explain admission control
- Steer a VPLS pseudowire onto a TE tunnel, and explain bandwidth allocation versus bandwidth limitation
The tasks
- See where the traffic goes today
- Tell the network about bandwidth
- A tunnel on an explicit path
- Put Kestrel's pseudowire on the tunnel, in both directions
- Allocation and limitation
- Let CSPF place the next tunnels, and watch admission control
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
- PE1
ether1to P2ether1 - PE1
ether2to P3ether1 - P2
ether2to PE4ether1 - P3
ether2to PE4ether2 - PE1
ether3to CE1ether1 - PE4
ether3to CE4ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PE1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| P2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| P3 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PE4 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE4 | 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 MTCINE RouterOS v7 guided labs.Open
11 - Traffic engineering with RSVP-TE - static and CSPF pathsand 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 MTCINE 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.