MikroTik MTCINE lab 12 of 12
Capstone - troubleshoot an ISP with BGP and L3VPN and VPLS services
Monday morning at Fernvale: an Internet customer is offline, Oakridge's VPN is down and its office routes are leaking to the upstream, and Larkspur's VPLS has lost a depot. Work through ten routers, from BGP sessions to labels to route targets, find the five planted faults and prove every service works.
Run this lab
It needs Standard: its 10 nodes are set to 10 vCPU and 2,560 MB in total.
In your workspace: Shared, then MikroTik MTCINE RouterOS v7 guided labs, then 12 - Capstone - troubleshoot an ISP with BGP and L3VPN and VPLS services
- Level
- Advanced
- Time
- About 150 minutes
- Nodes need
- 10 vCPU, 2,560 MB
- Smallest plan
- Standard
The scenario
Fernvale ran a weekend maintenance window and changed several routers. On Monday morning three customers call:
- Copperleaf Hosting (AS 65010, an Internet customer on PE3): "we have no Internet at all".
- Oakridge Clinic (L3VPN): "head office and branch can't see each other". Northgate's NOC also mails: "you are announcing 192.168.10.0/24 to us, please stop".
- Larkspur Logistics (BGP VPLS): "depot 2 has dropped off our network".
Plain IP inside the core is fine: OSPF is up everywhere and every loopback pings. Five faults were introduced. Find them all, fix them with the smallest change, and prove each service works. The intended design is in the notes on the canvas and in the table.
| Router | Loopback | Role and services |
|---|---|---|
| EDGE | 10.255.255.1 | eBGP to Northgate (203.0.113.1, AS 64510); announces 198.51.100.0/24; iBGP (IPv4) to PE2 and PE3, next-hop-self |
| P | 10.255.255.2 | core label switch: OSPF and LDP on all three core links |
| PE2 | 10.255.255.3 | Oakridge HQ (VRF OAK, eBGP AS 65201, ether2), Larkspur depot 1 (VE 1, ether3); iBGP VPNv4 and l2vpn to PE3 |
| PE3 | 10.255.255.4 | Oakridge branch (VRF OAK, OSPF, ether2), Larkspur depot 2 (VE 2, ether3), Copperleaf (eBGP AS 65010, ether4) |
What you’ll practise
- Troubleshoot a multi-service MPLS network methodically, one service and one layer at a time
- Diagnose eBGP and iBGP faults: session parameters and unusable next hops
- Diagnose LDP faults that break VPN and VPLS traffic while plain IP still works
- Diagnose VRF and route-target faults in L3VPN and BGP VPLS
- Explain the impact of each fault and prove the repair with targeted checks
The tasks
- Copperleaf's Internet service
- The core's labels
- Oakridge's L3VPN, and the leak
- Larkspur's VPLS
- Write the incident report
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
- NORTHGATE
ether1to EDGEether1 - EDGE
ether2to Pether1 - P
ether2to PE2ether1 - P
ether3to PE3ether1 - PE2
ether2to CE-OAK1ether1 - PE2
ether3to CE-LARK1ether1 - PE3
ether2to CE-OAK2ether1 - PE3
ether3to CE-LARK2ether1 - PE3
ether4to COPPERLEAFether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| NORTHGATE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| EDGE | 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 |
| PE3 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-OAK1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-LARK1 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-OAK2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CE-LARK2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| COPPERLEAF | 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
12 - Capstone - troubleshoot an ISP with BGP and L3VPN and VPLS servicesand 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.