CloudLabBox
Try the free demo

CCNP Service Provider lab 14 of 23

L3VPN: VRFs, MP-BGP and three PE-CE protocols

Build an MPLS L3VPN on IOS XR for two customers with overlapping addresses. Create VRFs, run MP-BGP, and connect sites with eBGP, OSPF and static routing.

Run this lab

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

In your workspace: Shared, then CCNP Service Provider guided labs, then 14 - L3VPN - VRFs MP-BGP and three PE-CE protocols

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

Level
Advanced
Time
About 90 minutes
Nodes need
7 vCPU, 9,728 MB
Smallest plan
Standard

The scenario

Fellgate Carrier has two new VPN customers. Each has two sites, and they connect in different ways:

CustomerSite 1Site 2
Maple Foods, AS 65001eBGP on PE1eBGP on PE2, same AS number
Rowan FreightOSPF on PE1Static on PE2

Both customers use 192.168.1.0/24 at site 1. They've never heard of each other, and neither should have to change anything.

The core is ready: IS-IS and LDP run on PE1, P and PE2, and the CE routers are configured. The customer ports on the PEs aren't configured yet.

DeviceInterfaceAddressConnects to
M1Loopback1192.168.1.1/24
M1Gi0/0172.16.1.2/30PE1 Gi0/0/0/2
R1Loopback1192.168.1.1/24
R1Gi0/0172.16.3.2/30PE1 Gi0/0/0/3
PE1Loopback010.255.0.1/32
PE1Gi0/0/0/010.0.12.1/30P Gi0/0/0/0
PLoopback010.255.0.2/32
PGi0/0/0/010.0.12.2/30PE1 Gi0/0/0/0
PGi0/0/0/110.0.23.1/30PE2 Gi0/0/0/0
PE2Loopback010.255.0.3/32
PE2Gi0/0/0/010.0.23.2/30P Gi0/0/0/1
M2Loopback1192.168.2.1/24
M2Gi0/0172.16.2.2/30PE2 Gi0/0/0/2
R2Loopback1192.168.4.1/24
R2Gi0/0172.16.4.2/30PE2 Gi0/0/0/3

What you’ll practise

  • Define VRFs, RDs and RTs on IOS XR
  • Run VPNv4 between PEs
  • Use as-override for sites with the same AS
  • Run OSPF between PE and CE, with redistribution
  • Use a static route in a VRF
  • Prove customer separation and find the label stack

The tasks

  1. VRFs and route targets
  2. MP-BGP between the PEs
  3. eBGP to Maple, and the AS problem
  4. OSPF to Rowan site 1
  5. A static route to Rowan site 2
  6. Prove the separation

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 L3VPN - VRFs MP-BGP and three PE-CE protocols7 nodes, 6 links. Every link is listed as text below the diagram.M1R1PE1PPE2M2R2Gi0/0/0/0Gi0/0/0/0Gi0/0/0/1Gi0/0/0/0Gi0/0Gi0/0/0/2Gi0/0Gi0/0/0/3Gi0/0/0/2Gi0/0Gi0/0/0/3Gi0/0
7 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Every link, as text
  • M1 Gi0/0 to PE1 Gi0/0/0/2
  • R1 Gi0/0 to PE1 Gi0/0/0/3
  • PE1 Gi0/0/0/0 to P Gi0/0/0/0
  • P Gi0/0/0/1 to PE2 Gi0/0/0/0
  • PE2 Gi0/0/0/2 to M2 Gi0/0
  • PE2 Gi0/0/0/3 to R2 Gi0/0
Nodes in L3VPN: VRFs, MP-BGP and three PE-CE protocols, with the image each runs and the vCPU and RAM it’s set to
NodeDeviceImage in Add NodeSet to
M1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE1Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
PCisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
PE2Cisco IOS XRvxrv-k9-demo-6.3.11 vCPU, 2,560 MB
M2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
R2Cisco 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 CCNP Service Provider guided labs.

  3. Open 14 - L3VPN - VRFs MP-BGP and three PE-CE protocols 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 CCNP Service Provider labs

All CCNP Service Provider 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.