CloudLabBox
Try the free demo

BGP in depth lab 14 of 14

Capstone - a small ISP edge

Your last job at Kestrel Fibre: build the whole BGP edge from a one-page design, with no steps to follow. A route reflector on IOS, a transit edge on Junos, a peering edge on EOS and a customer edge on RouterOS, all tagging routes on the way in, preferring customers over peers over transit, and sending only what they should.

Run this lab

It needs Standard: its 7 nodes are set to 8 vCPU and 8,448 MB in total.

In your workspace: Shared, then BGP in depth guided labs, then 14 - Capstone - a small ISP edge

Run it on Standard from £5 a day

The free demo can’t run it: it has 6 vCPU and 8 GB, and this lab’s nodes need 8 vCPU and 8,448 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 150 minutes
Nodes need
8 vCPU, 8,448 MB
Smallest plan
Standard

The scenario

Kestrel Fibre is moving to a new edge. The design below is all you get. There are no steps: read it, plan the order, and build it. Everything you need is in the earlier labs.

The design

RoleRouterPeerSession details
Route reflectorCORESRX1, EOS1, CHR1 as clientsLoopbacks, sending communities
Transit edgeSRX1TRANSIT, AS 64496MD5 key Kestrel-T1
Peering edgeEOS1PEER, AS 64497MD5 key Kestrel-P1
Customer edgeCHR1CUST, AS 64510
RuleRequirement
Next hopEach edge sets itself as next hop towards the reflector
TaggingRoutes get a community where they enter: transit 64500:1000, peer 64500:2000, customer 64500:3000
PreferenceLocal preference: customer 200, peer 150, transit 100
Customer filterFrom CUST, accept only 203.0.113.0/24
Export to TRANSIT and PEEROnly routes tagged customer
Inbound engineeringTowards TRANSIT, add one extra copy of AS 64500, so that the world prefers to come in through PEER
Export to CUSTA default route only
PrefixAnnounced byExpected at CORE
198.51.100.0/24TRANSIT and PEERThrough EOS1, local preference 150
192.0.2.0/24TRANSITThrough SRX1, local preference 100
198.18.77.0/24PEERThrough EOS1, local preference 150
203.0.113.0/24CUSTThrough CHR1, local preference 200
10.50.0.0/16CUST, by mistakeRejected
DeviceInterfaceAddressConnects to
CORELoopback010.255.0.1/32
COREGi0/010.0.1.1/30SRX1 ge-0/0/0
COREGi0/110.0.2.1/30EOS1 Ethernet1
COREGi0/210.0.3.1/30CHR1 ether1
SRX1ge-0/0/010.0.1.2/30CORE Gi0/0
SRX1ge-0/0/1172.16.1.1/30TRANSIT Gi0/0
SRX1lo010.255.0.2/32
EOS1Ethernet110.0.2.2/30CORE Gi0/1
EOS1Ethernet2172.16.2.1/30PEER Gi0/0
EOS1Loopback010.255.0.3/32
CHR1loopback10.255.0.4/32
CHR1ether110.0.3.2/30CORE Gi0/2
CHR1ether2172.16.3.1/30CUST Gi0/0
TRANSITLoopback010.255.0.8/32
TRANSITLoopback1198.51.100.1/24
TRANSITLoopback2192.0.2.1/24
TRANSITGi0/0172.16.1.2/30SRX1 ge-0/0/1
PEERLoopback010.255.0.7/32
PEERLoopback1198.51.100.1/24
PEERLoopback2198.18.77.1/24
PEERGi0/0172.16.2.2/30EOS1 Ethernet2
CUSTLoopback010.255.0.9/32
CUSTLoopback1203.0.113.1/24
CUSTLoopback210.50.0.1/16
CUSTGi0/0172.16.3.2/30CHR1 ether2

What you’ll practise

  • Turn a written design into working configuration on four vendors
  • Build iBGP with a route reflector and next-hop-self on every edge
  • Classify routes with communities at the point of entry
  • Enforce customer, peer and transit preference with local preference
  • Stop transit between providers with an export policy based on communities
  • Prove the design from outside the AS

The tasks

  1. Plan the order
  2. Build iBGP
  3. Build the edges
  4. Prove it

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.

Topology of Capstone - a small ISP edge7 nodes, 6 links. Every link is listed as text below the diagram.CORESRX1EOS1CHR1TRANSITPEERCUSTGi0/2ether1ge-0/0/1Gi0/0Ethernet2Gi0/0ether2Gi0/0Gi0/0ge-0/0/0Gi0/1Ethernet1
7 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CORE Gi0/0 to SRX1 ge-0/0/0
  • CORE Gi0/1 to EOS1 Ethernet1
  • CORE Gi0/2 to CHR1 ether1
  • SRX1 ge-0/0/1 to TRANSIT Gi0/0
  • EOS1 Ethernet2 to PEER Gi0/0
  • CHR1 ether2 to CUST Gi0/0
Nodes in Capstone - a small ISP edge, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CORECisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
SRX1Juniper vSRX NextGen templatevsrxng-23.4R2-S3.92 vCPU, 4,096 MB
EOS1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
CHR1MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
TRANSITCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PEERCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CUSTCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB

How to open this lab

  1. Sign in to your workspace at lab.cloudlabbox.com.

  2. In File Manager, open Shared, then the folder BGP in depth guided labs.

  3. Open 14 - Capstone - a small ISP edge and 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

All 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.