MPLS and L3VPN lab 4 of 11

PE-CE routing: static, eBGP and OSPF

One customer, four sites, three ways of talking to the provider. Bring static, eBGP and OSPF sites into one VPN, see why OSPF routes arrive as externals and fix it with a domain ID, and find the down bit that stops routes looping back in.

Run this lab

It needs Lite: its 6 nodes are set to 6 vCPU and 3,072 MB in total. That fits the free demo too.

In your workspace: Shared, then MPLS and L3VPN guided labs, then 04 - PE-CE routing - static eBGP and OSPF

Try it free for 30 minutesRun it on Lite from £3 a day

The free demo needs no card and no email. Every lab plan includes every guided lab.

Level
Intermediate
Time
About 90 minutes
Nodes need
6 vCPU, 3,072 MB
Smallest plan
Lite

The scenario

Wrenfield Networks has one customer, Alder Foods, with four sites and four opinions. Each site's IT firm chose a different way to route with its provider, and your job is to bring them all into the same VPN.

SitePERouting with the PEStatus
Site 1, 192.168.1.0/24PE1StaticYours to do
Site 2, 192.168.2.0/24PE1eBGP, AS 65201Yours to do
Site 3, 192.168.3.0/24PE2OSPFYours to do
Site 4, 192.168.4.0/24PE1OSPFAlready running, router ospf 10 vrf ALDER

VRF ALDER uses RD 65100:1 on PE1, RD 65100:2 on PE2 and route target 65100:100. PE1 and PE2 are directly connected here, so no P is needed for this lab.

DeviceInterfaceAddressConnects to
CE1Loopback1192.168.1.1/24
CE1Gi0/0172.16.1.2/30PE1 Gi0/1
CE2Loopback1192.168.2.1/24
CE2Gi0/0172.16.2.2/30PE1 Gi0/2
CE4Loopback1192.168.4.1/24
CE4Gi0/0172.16.4.2/30PE1 Gi0/3
PE1Loopback010.255.0.1/32
PE1Gi0/010.0.12.1/30PE2 Gi0/0
PE1Gi0/1172.16.1.1/30CE1 Gi0/0
PE1Gi0/2172.16.2.1/30CE2 Gi0/0
PE1Gi0/3172.16.4.1/30CE4 Gi0/0
PE2Loopback010.255.0.2/32
PE2Gi0/010.0.12.2/30PE1 Gi0/0
PE2Gi0/1172.16.3.1/30CE3 Gi0/0
CE3Loopback1192.168.3.1/24
CE3Gi0/0172.16.3.2/30PE2 Gi0/1

What you’ll practise

  • Bring a static customer site into a VPN with redistribution
  • Build an eBGP PE-CE session inside a VRF
  • Run an OSPF process per VRF and redistribute both ways
  • Explain how the OSPF domain ID decides between O IA and O E2
  • Find the down bit in an LSA and explain what it prevents
  • Say what a sham link does and when one is needed

The tasks

  1. Static routing with a customer
  2. eBGP with a customer
  3. OSPF with a customer
  4. Make the core look like OSPF
  5. One site is missing
  6. The down bit, and what you can't see here
  7. Prove all four sites talk

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 PE-CE routing - static eBGP and OSPF6 nodes, 5 links. Every link is listed as text below the diagram.CE1CE2CE4PE1PE2CE3Gi0/0Gi0/2Gi0/1Gi0/0Gi0/0Gi0/0Gi0/0Gi0/1Gi0/0Gi0/3
6 nodes, with the interface names each link uses. On a narrow screen, scroll the diagram sideways.
Nodes in PE-CE routing: static, eBGP and OSPF, 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
CE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CE4Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE1Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
PE2Cisco IOSvvios-adventerprisek9-m.spa.159-3.m91 vCPU, 512 MB
CE3Cisco 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 MPLS and L3VPN guided labs.

  3. Open 04 - PE-CE routing - static eBGP and OSPF 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.