HCIP-Datacom Core lab 8 of 14
MPLS L3VPN
Carry two customers with the same addresses over one MPLS core: VPN instances, RDs and route targets, MP-BGP, eBGP to one customer, direct routes for the other, and the two-label stack.
Run this lab
It needs Standard: its 9 nodes are set to 10 vCPU and 14,336 MB in total.
In your workspace: Shared, then HCIP-Datacom Core H12-821 guided labs, then 08 - MPLS L3VPN
- Level
- Advanced
- Time
- About 100 minutes
- Nodes need
- 10 vCPU, 14,336 MB
- Smallest plan
- Standard
The scenario
Northwind's carrier arm has signed two customers. Customer A has two offices with their own routers, which speak BGP. Customer B has two small offices with no router: the PCs plug into the PEs. Both customers use 192.168.1.0/24 and 192.168.2.0/24, and neither will renumber. The core already runs IS-IS and LDP, and its P router is an NE40E, a carrier router on VRP 8, working alongside the AR routers on VRP 5. Your job is to keep the two customers apart on one network, and to keep the P router out of it altogether.
| Device | Addresses |
|---|---|
| PE1 | LoopBack0 1.1.1.1, GE0/0/0 10.0.12.1/24, GE0/0/1 172.16.1.1/24 (VPN A, to CE1), GE0/0/2 192.168.1.1/24 (VPN B, PCB1) |
| P (NE40E) | LoopBack0 2.2.2.2, Ethernet1/0/0 10.0.12.2/24, Ethernet1/0/1 10.0.23.2/24 |
| PE2 | LoopBack0 3.3.3.3, GE0/0/0 10.0.23.3/24, GE0/0/1 172.16.2.1/24 (VPN A, to CE2), GE0/0/2 192.168.2.1/24 (VPN B, PCB2) |
| CE1 (AS 65001) | GE0/0/0 172.16.1.2/24, GE0/0/1 192.168.1.1/24 (PCA1 .10) |
| CE2 (AS 65002) | GE0/0/0 172.16.2.2/24, GE0/0/1 192.168.2.1/24 (PCA2 .10) |
| VPN | RD | Route target |
|---|---|---|
| A | 100:1 | 100:1 both ways |
| B | 100:2 | 100:2 both ways |
What you’ll practise
- Explain what the RD and the route target each do
- Create VPN instances and bind interfaces to them
- Build an MP-iBGP session for VPNv4
- Run eBGP with a customer inside a VPN instance
- Read VPN routes and labels on a PE, and confirm the P router knows none of them
The tasks
- Task 0: Load the starting configuration
- Concept: how L3VPN keeps customers apart
- Task 1: Check the core
- Task 2: Create the VPN instances
- Concept: MP-BGP
- Task 3: Connect the PEs with MP-BGP
- Concept: PE to CE routing
- Task 4: Connect the customers
- Task 5: Read what you built
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.
Every link, as text
- PE1
GE0/0/0to PEthernet1/0/0 - P
Ethernet1/0/1to PE2GE0/0/0 - PE1
GE0/0/1to CE1GE0/0/0 - PE2
GE0/0/1to CE2GE0/0/0 - CE1
GE0/0/1to PCA1eth0 - CE2
GE0/0/1to PCA2eth0 - PE1
GE0/0/2to PCB1eth0 - PE2
GE0/0/2to PCB2eth0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| PE1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| P | Huawei NetEngine NE40E | huaweine40e-bundled | 2 vCPU, 2,048 MB |
| PE2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| CE1 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| CE2 | Huawei AR1000V router | huaweiar1k-5.170-V300R022C00SPC100-Auto-update-esn | 1 vCPU, 2,048 MB |
| PCA1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PCA2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PCB1 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
| PCB2 | VPCS host | Built in to EVE-NG | Counted as 1 vCPU, 1,024 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
HCIP-Datacom Core H12-821 guided labs.Open
08 - MPLS L3VPNand 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 HCIP-Datacom Core labs
Related labs in other courses
CloudLabBox is independent of Huawei. The lab follows exam topics and isn’t vendor training material; vendor names identify the exams and the images in the workspace.