CloudLabBox
Try the free demo

MikroTik MTCINE lab 8 of 12

BGP-signalled VPLS with auto-discovery

Build a three-site VPLS for Larkspur Logistics where BGP does the work: each PE announces its site once with a route target, and every PE builds the full mesh of pseudowires by itself. Read the l2vpn routes, the label blocks and the dynamic pseudowires, and add a site without touching the other PEs' VPLS configuration.

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 08 - BGP-signalled VPLS with auto-discovery

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 75 minutes
Nodes need
6 vCPU, 1,536 MB
Smallest plan
Lite

The scenario

Fernvale's layer 2 service is selling well, and the LDP VPLS of lab 7 doesn't scale: every new site means a new pseudowire configured on every existing PE. For the next customer, Larkspur Logistics (depots on PE1 and PE2 today, a third depot on PE3 next week), Fernvale switches to BGP-signalled VPLS. The core already runs OSPF and LDP, and the three PEs already have iBGP sessions for the l2vpn address family.

RouterLoopbackLarkspur site
PE110.255.255.1depot 1: CE1 10.60.0.1, VE ID 1
PE210.255.255.2depot 2: CE2 10.60.0.2, VE ID 2
PE310.255.255.3depot 3: CE3 10.60.0.3, VE ID 3

What you’ll practise

  • Explain BGP auto-discovery and signalling for VPLS (RFC 4761): VE IDs, label blocks, route distinguishers and route targets
  • Read iBGP sessions that carry the l2vpn address family
  • Create /routing bgp vpls instances and read the dynamic pseudowires they build
  • Compare the work needed to add a site with LDP VPLS and with BGP VPLS

The tasks

  1. BGP for layer 2: the l2vpn address family
  2. Create the VPLS on the first two PEs
  3. Read what BGP carries
  4. Add the third depot without touching PE1 or PE2

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-signalled VPLS with auto-discovery6 nodes, 6 links. Every link is listed as text below the diagram.PE1PE2PE3CE1CE2CE3ether3ether1ether3ether1ether3ether1ether1ether1ether2ether1ether2ether2
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • PE1 ether1 to PE2 ether1
  • PE1 ether2 to PE3 ether1
  • PE2 ether2 to PE3 ether2
  • PE1 ether3 to CE1 ether1
  • PE2 ether3 to CE2 ether1
  • PE3 ether3 to CE3 ether1
Nodes in BGP-signalled VPLS with auto-discovery, 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
PE2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
PE3MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE3MikroTik 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 08 - BGP-signalled VPLS with auto-discovery 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.