CCNP Service Provider lab 15 of 23
L3VPN shared services and Internet access
Give two VPN customers shared services without letting them see each other, using route targets and an export policy on IOS XR. Then leak a default and a public block for Internet access from a VRF.
Run this lab
It needs Lite: its 6 nodes are set to 6 vCPU and 7,168 MB in total. That fits the free demo too.
In your workspace: Shared, then CCNP Service Provider guided labs, then 15 - L3VPN shared services and Internet access
- Level
- Advanced
- Time
- About 75 minutes
- Nodes need
- 6 vCPU, 7,168 MB
- Smallest plan
- Lite
The scenario
Maple Foods and Rowan Freight are happy with their VPNs and they want more. Both want to use Fellgate Carrier's hosted services in 10.200.0.0/24: DNS, monitoring and a software mirror. Neither may see the other. Maple also wants Internet access for its public web servers in 203.0.113.64/29, through its VPN connection.
The VPNs work. PE1 has VRF MAPLE and the Internet uplink, in the global table. PE2 has VRF ROWAN and VRF SHARED. SHARED exports 64500:900 and imports 64500:910.
| Device | Interface | Address | Connects to |
|---|---|---|---|
| M1 | Loopback1 | 192.168.1.1/24 | |
| M1 | Gi0/0 | 172.16.1.2/30 | PE1 Gi0/0/0/2 |
| M1 | Loopback2 | 203.0.113.65/29 | |
| UP | Loopback1 | 198.51.100.1/24 | |
| UP | Gi0/0 | 198.18.0.2/30 | PE1 Gi0/0/0/3 |
| PE1 | Loopback0 | 10.255.0.1/32 | |
| PE1 | Gi0/0/0/0 | 10.0.12.1/30 | PE2 Gi0/0/0/0 |
| PE1 | Gi0/0/0/2 | 172.16.1.1/30 | M1 Gi0/0 |
| PE1 | Gi0/0/0/3 | 198.18.0.1/30 | UP Gi0/0 |
| PE2 | Loopback0 | 10.255.0.2/32 | |
| PE2 | Gi0/0/0/0 | 10.0.12.2/30 | PE1 Gi0/0/0/0 |
| PE2 | Gi0/0/0/2 | 172.16.2.1/30 | R1 Gi0/0 |
| PE2 | Gi0/0/0/3 | 172.16.9.1/30 | SVC Gi0/0 |
| R1 | Loopback1 | 192.168.2.1/24 | |
| R1 | Gi0/0 | 172.16.2.2/30 | PE2 Gi0/0/0/2 |
| SVC | Loopback1 | 10.200.0.1/24 | |
| SVC | Gi0/0 | 172.16.9.2/30 | PE2 Gi0/0/0/3 |
What you’ll practise
- Design route targets for shared services
- Add a route target to chosen routes with an export policy
- Leak a default route from the global table into a VRF
- Leak a public block from a VRF into the global table
- Prove what is and is not reachable
The tasks
- See the starting point
- Tag routes for the shared VPN
- Internet access from a VRF
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
- M1
Gi0/0to PE1Gi0/0/0/2 - UP
Gi0/0to PE1Gi0/0/0/3 - PE1
Gi0/0/0/0to PE2Gi0/0/0/0 - PE2
Gi0/0/0/2to R1Gi0/0 - PE2
Gi0/0/0/3to SVCGi0/0
| Node | Device | Image in Add Node | Set to |
|---|---|---|---|
| M1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| UP | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| PE1 | Cisco IOS XRv | xrv-k9-demo-6.3.1 | 1 vCPU, 2,560 MB |
| PE2 | Cisco IOS XRv | xrv-k9-demo-6.3.1 | 1 vCPU, 2,560 MB |
| R1 | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
| SVC | Cisco IOSv | vios-adventerprisek9-m.spa.159-3.m9 | 1 vCPU, 512 MB |
How to open this lab
Sign in to your workspace at
lab.cloudlabbox.com.In File Manager, open Shared, then the folder
CCNP Service Provider guided labs.Open
15 - L3VPN shared services and Internet accessand 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.