BGP in depth lab 7 of 14
Multihoming and traffic engineering
Tern Logistics connects to two ISPs and wants its web traffic in through one and its staff traffic in through the other. Control what goes out with local preference, then find out how far prepending and MED really get you on the way in, and why a provider's community is sometimes the only tool that works.
Run this lab
It needs Lite: its 5 nodes are set to 5 vCPU and 2,304 MB in total. That fits the free demo too.
In your workspace: Shared, then BGP in depth guided labs, then 07 - Multihoming and traffic engineering
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 5 vCPU, 2,304 MB
- Smallest plan
- Lite
The scenario
Tern Logistics (AS 64510) has an IOS router, CE1, with two links to ISP A, and a MikroTik, CE2, with one link to ISP B. The ISPs peer with each other and with a distant network. Tern's brief:
| Traffic | Requirement |
|---|---|
| Everything going out | Leaves through ISP A, on CE1 |
| Into the web block, 203.0.113.0/25 | Arrives through ISP A, on the main link |
| Into the staff block, 203.0.113.128/25 | Arrives through ISP B |
| Anything between ISP A and ISP B | Must never cross Tern |
You can only configure CE1 and CE2. The ISPs have published how they treat customers:
| ISP | Local preference | Community you can send |
|---|---|---|
| ISP A, AS 64501 | Customers 150, peers 100 | 64501:80 sets your route to 80 |
| ISP B, AS 64502 | Customers 150, peers 100 | 64502:80 sets your route to 80 |
| Device | Interface | Address | Connects to |
|---|---|---|---|
| CE1 | Loopback1 | 203.0.113.1/25 | |
| CE1 | Gi0/0 | 172.16.1.1/30 | ISPA Gi0/0 |
| CE1 | Gi0/1 | 172.16.2.1/30 | ISPA Gi0/1 |
| CE1 | Gi0/2 | 10.0.12.1/30 | CE2 ether2 |
| CE2 | ether1 | 172.16.3.1/30 | ISPB Gi0/0 |
| CE2 | ether2 | 10.0.12.2/30 | CE1 Gi0/2 |
| CE2 | staff | 203.0.113.129/25 | |
| ISPA | Gi0/0 | 172.16.1.2/30 | CE1 Gi0/0 |
| ISPA | Gi0/1 | 172.16.2.2/30 | CE1 Gi0/1 |
| ISPA | Gi0/2 | 172.16.4.1/30 | ISPB Gi0/1 |
| ISPA | Gi0/3 | 172.16.5.1/30 | REMOTE Gi0/0 |
| ISPB | Gi0/0 | 172.16.3.2/30 | CE2 ether1 |
| ISPB | Gi0/1 | 172.16.4.2/30 | ISPA Gi0/2 |
| ISPB | Gi0/2 | 172.16.6.1/30 | REMOTE Gi0/1 |
| REMOTE | Loopback1 | 198.51.100.1/24 | |
| REMOTE | Gi0/0 | 172.16.5.2/30 | ISPA Gi0/3 |
| REMOTE | Gi0/1 | 172.16.6.2/30 | ISPB Gi0/2 |
What you’ll practise
- Use local preference to choose the outbound exit, on one router, for the whole AS
- Use MED to choose between two links to the same provider
- Use AS-path prepending to influence distant networks, on IOS and RouterOS
- Explain why a provider's own local preference beats any prepend you send
- Use provider communities to change a provider's decision
- Keep a multihomed customer from becoming a transit path
The tasks
- Read the baseline
- Outbound with local preference
- Two links to one provider: MED
- Prepending
- A provider community
- The same for the staff block
- Prove the paths
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
- CE1
Gi0/0to ISPAGi0/0 - CE1
Gi0/1to ISPAGi0/1 - CE1
Gi0/2to CE2ether2 - CE2
ether1to ISPBGi0/0 - ISPA
Gi0/2to ISPBGi0/1 - ISPA
Gi0/3to REMOTEGi0/0 - ISPB
Gi0/2to REMOTEGi0/1
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| CE1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| CE2 | MikroTik RouterOS | mikrotik-7.14.2 | 1 vCPU, 256 MB |
| ISPA | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| ISPB | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| REMOTE | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 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
07 - Multihoming and traffic engineeringand 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
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.