MikroTik MTCINE lab 10 of 12
BGP L3VPN with OSPF and eBGP towards customers
Build Oakridge Clinic's layer 3 VPN across Fernvale's MPLS core: a VRF on each PE, route distinguishers and route targets, VPNv4 between the PEs, eBGP to one site and OSPF to the other. Find the route-target typo a colleague left on PE2, prove a second customer with the same addresses stays separate, and read an MPLS VPN traceroute.
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 10 - BGP L3VPN with OSPF and eBGP towards customers
- Level
- Advanced
- Time
- About 90 minutes
- Nodes need
- 6 vCPU, 1,536 MB
- Smallest plan
- Lite
The scenario
Oakridge Clinic wants its head office (CE-OAK1, on PE1) and its new branch (CE-OAK2, on PE2) joined by a layer 3 VPN across Fernvale's MPLS core. The head office already speaks eBGP (AS 65201); the branch router only does OSPF. A colleague started on PE2 (VRF OAK and the branch link), and PE2 also carries a second customer, Brightwater, whose LAN happens to use the same 192.168.10.0/24 as Oakridge HQ. The core runs OSPF and LDP, and PE1 and PE2 already have an iBGP session for VPNv4.
| Device | VRF | Link | Customer LAN |
|---|---|---|---|
| CE-OAK1 (AS 65201) | OAK on PE1 ether2 | 172.16.11.0/30 (PE1 .1, CE .2) | 192.168.10.0/24 |
| CE-OAK2 (OSPF) | OAK on PE2 ether2 | 172.16.22.0/30 (PE2 .1, CE .2) | 192.168.20.0/24 |
| CE-BRW (static) | BRW on PE2 ether3 | 172.16.33.0/30 (PE2 .1, CE .2) | 192.168.10.0/24 |
Oakridge's plan: route target 64500:100, route distinguishers 64500:1100 (PE1) and 64500:1200 (PE2). Brightwater: route target 64500:200.
What you’ll practise
- Explain the L3VPN building blocks: VRF, route distinguisher, route target, VPNv4 and the two-label stack
- Configure /routing bgp vpn with RD, import and export route targets and export redistribution
- Run eBGP and OSPF as PE-CE protocols inside a VRF, and send VPN routes back to the customer
- Troubleshoot a route-target mismatch from the VRF tables and the VPN configuration
- Explain what traceroute shows, and hides, through an MPLS VPN
The tasks
- The L3VPN building blocks
- Build Oakridge's VRF on PE1
- eBGP to the head office, inside the VRF
- OSPF to the branch, inside the VRF
- Find the colleague's mistake
- Overlapping customers and the VPN traceroute
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
- CE-OAK1
ether1to PE1ether2 - PE1
ether1to Pether1 - P
ether2to PE2ether1 - PE2
ether2to CE-OAK2ether1 - PE2
ether3to CE-BRWether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PE1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| P | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| PE2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-OAK1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-OAK2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-BRW | 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
10 - BGP L3VPN with OSPF and eBGP towards customersand 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.