MikroTik MTCRE lab 7 of 14
Single-area OSPF on RouterOS 7
Bring up OSPF the RouterOS 7 way (instance, area, interface templates), watch neighbours reach Full and 2-Way, control the DR/BDR election on a shared segment, read the link-state database, and steer traffic with interface costs.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 3,072 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCRE RouterOS v7 guided labs, then 07 - Single-area OSPF on RouterOS 7
- Level
- Intermediate
- Time
- About 65 minutes
- Nodes need
- 6 vCPU, 3,072 MB
- Smallest plan
- Lite
The scenario
Fernvale's static routes have become unmanageable, so the core is moving to OSPF. Four routers share a core switch (the Core LAN), and the branch router R4 also has two point-to-point links to R2 and R3. Design goals: R1 is always the designated router on the core LAN, R2 the backup, R3 and R4 never; router IDs come from loopbacks; LANs are advertised but never send hellos; and branch traffic to HQ prefers the R2 link.
| Router | Core LAN (ether1/ether4) | Other links | LAN | Loopback |
|---|---|---|---|---|
| R1 | 10.0.0.1/24, priority 200 | – | 192.168.1.1/24 | 10.255.255.1 |
| R2 | 10.0.0.2/24, priority 100 | 10.0.24.1/30 → R4 | – | 10.255.255.2 |
| R3 | 10.0.0.3/24, priority 0 | 10.0.34.1/30 → R4 | – | 10.255.255.3 |
| R4 | 10.0.0.4/24 (ether4), priority 0 | 10.0.24.2/30, 10.0.34.2/30 | 192.168.4.1/24 | 10.255.255.4 |
What you’ll practise
- Configure an OSPF instance, the backbone area and interface templates in RouterOS 7
- Use loopback router IDs, passive interfaces and point-to-point network types
- Explain neighbour states and why DROTHERs stay in 2-Way
- Control the DR/BDR election with priorities
- Read router and network LSAs
- Steer paths with interface costs and recognise OSPF ECMP
The tasks
- Know how OSPF builds its database
- Configure OSPF on RouterOS 7
- Read the neighbours and the DR election
- Read the link-state database
- Steer traffic with cost
- Network types and multicast (reading)
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
- R1
ether1to Core-LAN (network) - R2
ether1to Core-LAN (network) - R3
ether1to Core-LAN (network) - R4
ether4to Core-LAN (network) - R2
ether2to R4ether1 - R3
ether2to R4ether2 - R1
ether2to PC1eth0 - R4
ether3to PC2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| R2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| R3 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| R4 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PC1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PC2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
MikroTik MTCRE RouterOS v7 guided labs.Open
07 - Single-area OSPF on RouterOS 7and 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 MTCRE 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.