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

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
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.

DeviceVRFLinkCustomer LAN
CE-OAK1 (AS 65201)OAK on PE1 ether2172.16.11.0/30 (PE1 .1, CE .2)192.168.10.0/24
CE-OAK2 (OSPF)OAK on PE2 ether2172.16.22.0/30 (PE2 .1, CE .2)192.168.20.0/24
CE-BRW (static)BRW on PE2 ether3172.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

  1. The L3VPN building blocks
  2. Build Oakridge's VRF on PE1
  3. eBGP to the head office, inside the VRF
  4. OSPF to the branch, inside the VRF
  5. Find the colleague's mistake
  6. 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.

Topology of BGP L3VPN with OSPF and eBGP towards customers6 nodes, 5 links. Every link is listed as text below the diagram.PE1PPE2CE-OAK1CE-OAK2CE-BRWether1ether2ether1ether1ether2ether1ether2ether1ether3ether1
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in BGP L3VPN with OSPF and eBGP towards customers, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
PE1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PMikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PE2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE-OAK1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE-OAK2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE-BRWMikroTik 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 MTCINE RouterOS v7 guided labs.

  3. Open 10 - BGP L3VPN with OSPF and eBGP towards customers 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 MTCINE labs

All 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.