CCNP ENCOR lab 13 of 36
eBGP to a single provider
Bring up Fernhill's first eBGP session to its internet provider with MD5 protection, advertise the company's public block, accept only a default route, and hand that default to the inside network.
Run this lab
It needs Lite: its 4 nodes are set to 4 vCPU and 2,048 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP ENCOR 350-401 guided labs, then 13 - eBGP to a single provider
- Level
- Intermediate
- Time
- About 60 minutes
- Nodes need
- 4 vCPU, 2,048 MB
- Smallest plan
- Lite
The scenario
Fernhill Freight has signed up with its first internet provider, ISP1 (AS 64500), and received the public block 192.0.2.0/24 and the private AS number 65010. ISP1 has already configured its side of the eBGP session and will send Fernhill a default route. Its welcome letter says:
*Peer address 203.0.113.1, your address 203.0.113.2. MD5 key
Fh-ISP1-key. Advertise only 192.0.2.0/24. We send you 0.0.0.0/0 and, for now, our full table.*
Your job: bring the session up, advertise the block, accept only the default route, and give the inside network (R2) a way out. You may look at ISP1 and INET, but treat them as somebody else's routers: don't change them.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| R1 | Gi0/0 | 203.0.113.2/30 | ISP1 Gi0/0 |
| R1 | Gi0/1 | 10.0.12.1/30 | R2 Gi0/1 |
| R1 | Lo0 / Lo100 | 10.255.0.1/32 / 192.0.2.1/32 (public service address) | – |
| R2 | Gi0/1 | 10.0.12.2/30 | R1 Gi0/1 |
| R2 | Lo10 | 10.10.30.1/24 (HQ servers) | – |
| ISP1 | Gi0/0 / Gi0/1 | 203.0.113.1/30 / 203.0.113.9/30 | R1 / INET |
| INET | Gi0/1 | 203.0.113.10/30 | ISP1 Gi0/1 |
| INET | Lo1 / Lo2 | 198.51.100.1/25 / 198.51.100.129/25 | – |
R1 and R2 already run OSPF area 0 between them.
Topology: R2 — R1 — ISP1 — INET.
What you’ll practise
- Configure an eBGP neighbour and follow it through the BGP finite-state machine to Established
- Advertise a prefix with a network statement and anchor it with a Null0 route
- Read the BGP table: status codes, next hop, AS_PATH and origin
- Filter what you send and accept with prefix lists, and check them with received-routes and advertised-routes
- Inject the provider's default route into OSPF for the inside network
The tasks
- Look before you touch
- Bring up the session, safely
- Advertise Fernhill's public block
- Send only your block, accept only the default
- Read the BGP table
- Give the inside network a way out
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
- R2
Gi0/1to R1Gi0/1 - R1
Gi0/0to ISP1Gi0/0 - ISP1
Gi0/1to INETGi0/1
| 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 |
| ISP1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| INET | 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
CCNP ENCOR 350-401 guided labs.Open
13 - eBGP to a single providerand 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 CCNP ENCOR labs
Related labs in other courses
CloudLabBox is independent of Cisco. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.