MikroTik MTCINE lab 1 of 12
eBGP with the v7 connection and template model
Fernvale Networks has its own AS number at last. Bring up its first eBGP session to an upstream with RouterOS 7's template, connection and session model, advertise Fernvale's address block, connect a stub customer that uses a private AS, and stop that private AS leaking to the Internet.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 1,792 MB in total. That fits the free demo too.
In your workspace: Shared, then MikroTik MTCINE RouterOS v7 guided labs, then 01 - eBGP with the v7 connection and template model
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 1,792 MB
- Smallest plan
- Lite
The scenario
Fernvale Networks, the regional ISP you have been building since the MTCNA labs, has received its own autonomous system number, AS 64500, and the provider-independent block 198.51.100.0/24. Until now Fernvale used static routes to one upstream. Today it turns up its first eBGP session to the transit provider Northgate Transit (AS 64510), and connects its first BGP customer, Copperleaf Hosting, which uses the private AS 65010 and a /26 out of Fernvale's block.
Northgate has already configured its side of the session. You configure FV-EDGE and Copperleaf's router (Fernvale manages it for them). The hosts 198.18.0.1 and 198.18.1.1 on NORTHGATE stand for the Internet.
| Router | AS | Addresses |
|---|---|---|
| NORTHGATE | 64510 | ether1 203.0.113.1/30 · Internet 198.18.0.1/24, 198.18.1.1/24 |
| FV-EDGE | 64500 | ether1 203.0.113.2/30 · ether2 172.16.0.1/30 · lan 198.51.100.1/25 · loopback 10.255.255.1 |
| COPPERLEAF | 65010 | ether1 172.16.0.2/30 · ether2 198.51.100.193/26 |
| CL-SRV (VPCS) | - | 198.51.100.200/26, gateway .193 |
What you’ll practise
- Explain autonomous systems, the path-vector idea and why BGP runs over TCP port 179
- Build eBGP sessions with /routing bgp template and /routing bgp connection, and read /routing bgp session
- Advertise a prefix with an address list and output.network, and know why it needs a matching route
- Give a stub customer a default route only, with an output filter and default-originate
- Remove a customer's private AS number before routes leave your AS
The tasks
- Look before you build
- Bring up eBGP to Northgate with a template and a connection
- Advertise Fernvale's block
- Connect a stub customer
- Remove the private AS
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 FV-EDGEether1 - FV-EDGE
ether2to COPPERLEAFether1 - COPPERLEAF
ether2to CL-SRVeth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| NORTHGATE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| FV-EDGE | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| COPPERLEAF | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| CL-SRV | 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 MTCINE RouterOS v7 guided labs.Open
01 - eBGP with the v7 connection and template modeland 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.