BGP in depth lab 1 of 14
BGP session basics on three vendors
A partner on Arista and a customer on MikroTik are joining Kestrel Fibre's edge. Build sessions that survive a failed link by peering between loopbacks, then protect them with MD5 and TTL security, and see the same ideas in three vendors' commands.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 3,328 MB in total. That fits the free demo too.
In your workspace: Shared, then BGP in depth guided labs, then 01 - BGP session basics on three vendors
- Level
- Intermediate
- Time
- About 75 minutes
- Nodes need
- 4 vCPU, 3,328 MB
- Smallest plan
- Lite
The scenario
Kestrel Fibre (AS 64500) has two core routers, R1 and R2, joined by two links. A partner on Arista (AS 64510) has two links to R1. A customer on MikroTik (AS 64520) has one link to R2. Your job is to bring up all three BGP sessions so that one failed link doesn't reset anything, then secure them before the change window closes.
| Session | Type | Between | Protection |
|---|---|---|---|
| R1 to R2 | iBGP | Loopbacks | Survives a link failure |
| R1 to EOS1 | eBGP | Loopbacks | MD5 Kestrel-Edge1, TTL security |
| R2 to CHR1 | eBGP | Link addresses | MD5 Kestrel-Edge2, TTL security |
| Device | AS | Announces |
|---|---|---|
| R1 | 64500 | 203.0.113.0/24 |
| EOS1 | 64510 | 198.51.100.0/24 |
| CHR1 | 64520 | 192.0.2.0/24 |
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Loopback0 | 10.255.0.1/32 | |
| R1 | Loopback1 | 203.0.113.1/24 | |
| R1 | Gi0/0 | 10.0.12.1/30 | R2 Gi0/0 |
| R1 | Gi0/1 | 10.0.112.1/30 | R2 Gi0/1 |
| R1 | Gi0/2 | 172.16.1.1/30 | EOS1 Ethernet1 |
| R1 | Gi0/3 | 172.16.2.1/30 | EOS1 Ethernet2 |
| R2 | Loopback0 | 10.255.0.2/32 | |
| R2 | Gi0/0 | 10.0.12.2/30 | R1 Gi0/0 |
| R2 | Gi0/1 | 10.0.112.2/30 | R1 Gi0/1 |
| R2 | Gi0/2 | 172.16.3.1/30 | CHR1 ether1 |
| EOS1 | Ethernet1 | 172.16.1.2/30 | R1 Gi0/2 |
| EOS1 | Ethernet2 | 172.16.2.2/30 | R1 Gi0/3 |
| EOS1 | Loopback0 | 10.255.0.10/32 | |
| EOS1 | Loopback1 | 198.51.100.1/24 | |
| CHR1 | ether1 | 172.16.3.2/30 | R2 Gi0/2 |
| CHR1 | lan | 192.0.2.1/24 |
What you’ll practise
- Build iBGP between loopbacks with update-source and next-hop-self, and say why each is needed
- Build eBGP between loopbacks across parallel links on IOS and EOS
- Explain why eBGP needs multihop or TTL security when peers aren't directly connected
- Add MD5 authentication on IOS, EOS and RouterOS
- Apply TTL security on IOS, EOS and RouterOS, and read the TTL values on the session
- Prove a session survives the loss of one link
The tasks
- iBGP between loopbacks
- eBGP between loopbacks
- MD5 on IOS and EOS
- Swap multihop for TTL security
- The MikroTik customer
- Prove it survives a link failure
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
- R1
Gi0/0to R2Gi0/0 - R1
Gi0/1to R2Gi0/1 - R1
Gi0/2to EOS1Ethernet1 - R1
Gi0/3to EOS1Ethernet2 - R2
Gi0/2to CHR1ether1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| R2 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| EOS1 | Arista vEOS | veos-4.33.1.1F | 1 vCPU, 2,048 MB |
| CHR1 | 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
BGP in depth guided labs.Open
01 - BGP session basics on three vendorsand 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 BGP in depth labs
Related labs in other courses
CloudLabBox is independent of Arista Networks, Cisco, Juniper Networks and MikroTik. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.