CloudLabBox
Try the free demo

MPLS and L3VPN lab 11 of 11

Capstone: a three-vendor provider edge

Build a new region from a design brief: LDP across IOS, Junos and RouterOS, a VPNv4 route reflector, two customers with overlapping addresses on eBGP, OSPF and static, and Internet access through one PE with VRF-aware NAT.

Run this lab

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

In your workspace: Shared, then MPLS and L3VPN guided labs, then 11 - Capstone - a three-vendor provider 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 12 vCPU and 8,448 MB together. Every lab plan includes every guided lab.

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

The scenario

Wrenfield Networks is opening a new region. Everything you've met in this course comes together here: one IOS PE, one Junos PE and one RouterOS PE around one IOS core router, with two customers and an Internet service. This is a design brief, not a set of steps. The tasks tell you what must be true, and it's up to you how to get there.

The design

  • Core: OSPF already runs. Labels run on every core link.
  • Route reflection: no full mesh. P is the VPNv4 route reflector, and PE1, PE2 and PE3 are its clients, each peering with 10.255.0.2. P keeps no customer routes in any forwarding table.
CustomerSiteCEPELANPE-CERDRT
Alder Foods1CE1PE1, 172.16.1.1192.168.1.0/24eBGP, AS 6520165100:165100:100
Alder Foods2CE2PE2, 172.16.2.1192.168.2.0/24eBGP, AS 6520165100:365100:100
Alder Foods3CE3PE3, 172.16.3.1192.168.3.0/24OSPF area 065100:465100:100
Birch Logistics1Loopback20 on PE1PE1192.168.1.0/24Directly attached65100:1165100:200
Birch Logistics2B2PE3, 172.16.6.1192.168.2.0/24Static65100:1465100:200
  • Internet: PE1's uplink to UP is in the global table. All of Alder's sites use it, with NAT to 203.0.113.2. UP's filter drops any 192.168.x.x source. Birch gets no Internet service.
  • Overlap: the two customers use the same addresses. That's expected.
DeviceInterfaceAddressConnects to
CE1Loopback1192.168.1.1/24
CE1Gi0/0172.16.1.2/30PE1 Gi0/0
UPLoopback1198.51.100.1/24
UPGi0/0203.0.113.1/30PE1 Gi0/3
PE1Loopback010.255.0.1/32
PE1Gi0/110.0.12.1/30P Gi0/0
PE1Gi0/3203.0.113.2/30UP Gi0/0
PLoopback010.255.0.2/32
PGi0/010.0.12.2/30PE1 Gi0/1
PGi0/110.0.23.1/30PE2 ge-0/0/0
PGi0/210.0.24.1/30PE3 ether1
PE2ge-0/0/010.0.23.2/30P Gi0/1
PE2ge-0/0/1CE2 Gi0/0
PE2lo010.255.0.3/32, 127.0.0.1/32
CE2Loopback1192.168.2.1/24
CE2Gi0/0172.16.2.2/30PE2 ge-0/0/1
PE3loopback10.255.0.4/32
PE3ether110.0.24.2/30P Gi0/2
CE3ether1172.16.3.2/30PE3 ether2
CE3lan192.168.3.1/24
B2ether1172.16.6.2/30PE3 ether3
B2lan192.168.2.1/24

What you’ll practise

  • Bring up LDP and MP-BGP across three vendors from a design brief
  • Run a VPNv4 route reflector on a router with no VRFs
  • Connect customers with eBGP, OSPF and static routing on different vendors
  • Keep two customers with the same addresses apart
  • Deliver Internet access to every site of one customer through one PE

The Lab Tasks pane has the scenario, the 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 three-vendor provider edge9 nodes, 8 links. Every link is listed as text below the diagram.CE1UPPE1PPE2CE2PE3CE3B2Gi0/0Gi0/3ge-0/0/1Gi0/0ether2ether1ether3ether1Gi0/1Gi0/0Gi0/0Gi0/0Gi0/1ge-0/0/0Gi0/2ether1
9 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • CE1 Gi0/0 to PE1 Gi0/0
  • UP Gi0/0 to PE1 Gi0/3
  • PE1 Gi0/1 to P Gi0/0
  • P Gi0/1 to PE2 ge-0/0/0
  • P Gi0/2 to PE3 ether1
  • PE2 ge-0/0/1 to CE2 Gi0/0
  • PE3 ether2 to CE3 ether1
  • PE3 ether3 to B2 ether1
Nodes in Capstone: a three-vendor provider edge, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
CE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
UPCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PCisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE2Juniper vJunos-routervjunosrouter-24.2R1-S2.54 vCPU, 5,120 MB
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE3MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
CE3MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 MB
B2MikroTik RouterOSmikrotik-7.14.21 vCPU, 256 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 MPLS and L3VPN guided labs.

  3. Open 11 - Capstone - a three-vendor provider 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 MPLS and L3VPN labs

All MPLS and L3VPN labs

Related labs in other courses

CloudLabBox is independent of 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.