Arista EOS lab 19 of 20

BGP L3VPN with overlapping customers

Run two customers with the same addresses over one SR-MPLS core: VRFs, route distinguishers, route targets, a VPNv4 session between PEs, eBGP to a customer router, then a shared-services VRF that both customers reach without reaching each other.

Run this lab

It needs Standard: its 9 nodes are set to 9 vCPU and 10,752 MB in total.

In your workspace: Shared, then Arista EOS guided labs, then 19 - BGP L3VPN with overlapping customers

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 9 vCPU and 10,752 MB together. Every lab plan includes every guided lab.

Level
Advanced
Time
About 95 minutes
Nodes need
9 vCPU, 10,752 MB
Smallest plan
Standard

The scenario

Northwind now sells VPNs. RED and BLUE both use 192.168.20.0/24 at their second site, and neither will renumber. The IS-IS and SR-MPLS core is already running. You'll keep the two customers apart with VRFs, carry their routes between PEs with BGP, connect RED's own router with eBGP, and then give both customers one shared service without letting them reach each other.

CustomerSiteWhereSubnetHost
REDAPE1 Et310.10.1.0/24 (PE1 .1)red1 10.10.1.10
REDBPE2 Et3 to CE2 (AS 65102)172.16.2.0/31 (PE2 .0, CE2 .1), then 192.168.20.0/24 behind CE2red2 192.168.20.10
BLUEAPE1 Et410.20.1.0/24 (PE1 .1)blue1 10.20.1.10
BLUEBPE2 Et4192.168.20.0/24 (PE2 .1)blue2 192.168.20.10
Shared-PE2 Et510.99.0.0/24 (PE2 .1)svc1 10.99.0.10
VRFPERDExport RTImport RT
REDPE165000:10165000:1065000:10, 65000:990
REDPE265000:10265000:1065000:10
BLUEPE165000:20165000:2065000:20, 65000:990
BLUEPE265000:20265000:2065000:20
SHAREDPE265000:99165000:99065000:99

Core links: PE1 Et1 to P1 Et1 10.0.1.0/31, PE2 Et1 to P1 Et2 10.0.3.0/31. Loopbacks: PE1 10.255.0.1, PE2 10.255.0.2, P1 10.255.0.11. Core AS 65000.

What you’ll practise

  • Create VRFs and move customer ports into them
  • Explain route distinguishers and route targets with live examples
  • Bring up a VPNv4 session between PEs and read VPN routes and labels
  • Run eBGP from a PE to a customer router inside a VRF
  • Prove customers are isolated although they share addresses
  • Give both customers a shared service with route targets

The tasks

  1. Address the hosts and check the transport
  2. Create the VRFs
  3. Bring up VPNv4 and carry the routes
  4. Connect RED's router with eBGP
  5. Prove the customers are separate
  6. Give both customers one shared service

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 BGP L3VPN with overlapping customers9 nodes, 8 links. Every link is listed as text below the diagram.PE1P1PE2CE2red1blue1red2blue2svc1Ethernet2eth0Ethernet5eth0Ethernet1Ethernet1Ethernet1Ethernet2Ethernet3eth0Ethernet4eth0Ethernet3Ethernet1Ethernet4eth0
9 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in BGP L3VPN with overlapping customers, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
PE1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
P1Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
PE2Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
CE2Arista vEOSveos-4.33.1.1F1 vCPU, 2,048 MB
red1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
blue1Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
red2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
blue2Alpine Linuxclbalpinebase-alpine-base-3-20-31 vCPU, 512 MB
svc1Alpine Linuxclbalpinebase-alpine-base-3-20-31 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 Arista EOS guided labs.

  3. Open 19 - BGP L3VPN with overlapping customers 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 Arista EOS labs

All Arista EOS labs

Related labs in other courses

CloudLabBox is independent of Arista Networks. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.