zNetLaB › Guided labs › Service Provider
IOS XR L3VPN with as-override
Service Provider Advanced 5 devices 6 checked tasks 100 points Plan lab
Three ASR 9001s form the provider core: IS-IS level 2 and LDP inside, VPNv4 between the PE loopbacks. Two customer sites share one AS, so the PEs must rewrite the path before a site will take the other one's route. You build it in a browser, type real commands at each device, and every task below is
checked against the running configuration — so you find out it is wrong before anybody else does.
Open this lab in the simulator
The simulator runs in your browser with nothing to install. This lab is part of the full simulator: open it free for 7 days with a new account, then with a plan. It needs an account, which keeps your progress.
The scenario
Three ASR 9001s form the provider core: IS-IS level 2 and LDP inside, VPNv4 between the PE loopbacks. Two customer sites share one AS, so the PEs must rewrite the path before a site will take the other one's route.
Your role: an engineer in the provider’s network operations centre. Level: Advanced Done when: all 6 goals show as passed (100 points).
Network status
Devices: 5 routers, cabled as drawn. No Layer 1 or Layer 2 faults: every link is connected and up. CE1, PE1, P, PE2, CE2 start with an empty configuration.
Known problems
None: nothing is misconfigured. The network is simply not finished: what the goals list is what you have to build or secure.
Goals
LDP is up on both core links of P (15 pts) The PEs exchange VPNv4 between loopbacks (15 pts) PE1 holds the far site in VRF C (20 pts) CE1 accepts CE2's loopback although both are AS 65001 (20 pts) The P router knows no customer prefix (10 pts) CE1 reaches CE2 across the core (20 pts)
The activity, in order
LDP is up on both core links of P On P, PE1 and PE2: a Loopback0, IS-IS level 2 with point-to-point core links, and the core interfaces under mpls ldp. Commit on each.Why: Each goal is a state the lab can check on the running device. Verify with: show mpls ldp neighbor The PEs exchange VPNv4 between loopbacks Under router bgp 100 enable address-family vpnv4 unicast, then a neighbour at the far PE loopback with update-source Loopback0 and the same address family.Why: Each goal is a state the lab can check on the running device. Verify with: show bgp vpnv4 unicast summary PE1 holds the far site in VRF C Make VRF C with import and export route-target 100:1, put the customer port in it, give the VRF an RD under BGP and peer with the CE through a pass route-policy in both directions.Why: Each goal is a state the lab can check on the running device. Verify with: show route vrf C CE1 accepts CE2's loopback although both are AS 65001 Add as-override to the CE neighbour on each PE, so the PE puts its own AS in place of 65001 before sending.Why: Each goal is a state the lab can check on the running device. Verify with: show ip bgp The P router knows no customer prefix Keep BGP on the PEs only; P switches labels and needs nothing but IS-IS and LDP.Why: Each goal is a state the lab can check on the running device. Verify with: show route CE1 reaches CE2 across the core With the routes in place, ping the far loopback from CE1.Why: Each goal is a state the lab can check on the running device. Verify with: ping 172.16.2.1 source Loopback0
Tips
Work in the order given: later goals depend on the earlier ones. After every change, run the verify command before moving on; do not guess. Stuck? Read the verify output first. It names the interface, neighbour or route that is wrong.
Why this matters
Three ASR 9001s form the provider core: IS-IS level 2 and LDP inside, VPNv4 between the PE loopbacks. Two customer sites share one AS, so the PEs must rewrite the path before a site will take the other one's route.
What you will be able to do
LDP is up on both core links of P
The PEs exchange VPNv4 between loopbacks
PE1 holds the far site in VRF C
CE1 accepts CE2's loopback although both are AS 65001
The network
Catalyst 8000V, ASR 9001 — 5 devices in all, already cabled.
Gi1 Gi0/0/0/0 Gi0/0/0/1 Gi0/0/0/0 Gi0/0/0/1 Gi0/0/0/1 Gi0/0/0/0 Gi1 CE1 PE1 P PE2 CE2 Drawn from this lab: devices, cables, ports and the addresses already set.
Device Model Address already set
CE1 Catalyst 8000V configure it
PE1 ASR 9001 configure it
P ASR 9001 configure it
PE2 ASR 9001 configure it
CE2 Catalyst 8000V configure it
Cabling
CE1 Gi1 ↔ PE1 Gi0/0/0/0
PE1 Gi0/0/0/1 ↔ P Gi0/0/0/0
P Gi0/0/0/1 ↔ PE2 Gi0/0/0/1
PE2 Gi0/0/0/0 ↔ CE2 Gi1
What is configured at the start
Nothing is configured to start with beyond the addresses above: you build the configuration from a clean start.
Tasks, and how each one is checked
Every task is decided by reading the live network — a neighbour in FULL, a ping that succeeds, a line in the running configuration — not by looking for a keyword you typed. The same command shows you what the lab sees.
# Task Pts How to verify it yourself
1 LDP is up on both core links of P 15 On P: show mpls ldp neighbor output matches Peer LDP Identifier: 1\.1\.1\.1:0[\s\S]*Peer LDP Identifier: 3\.3\.3\.3:0.
2 The PEs exchange VPNv4 between loopbacks 15 On PE1: show bgp vpnv4 unicast summary output matches 3\.3\.3\.3\s+0\s+100.
3 PE1 holds the far site in VRF C 20 On PE1: show route vrf C output matches 172\.16\.2\.1/32.
4 CE1 accepts CE2's loopback although both are AS 65001 20 On CE1: show ip route lists 172.16.2.1/32.
5 The P router knows no customer prefix 10 On P: show mpls ldp neighbor output matches Peer LDP Identifier: 1\.1\.1\.1:0. and On P: show ip route does not list 172.16.2.1/32.
6 CE1 reaches CE2 across the core 20 On CE1: ping 172.16.2.1 must succeed.
Stuck? Ask the coach
Tell the coach what you see or what you tried. It gives you a hint, not the answer, the way a senior engineer would. Included with a free trial or any plan.
Ask the coach
Reference solution
Try it yourself first — the lab checks your work either way. This is one configuration that makes every task pass, device by device:
P configure
interface Loopback0
ipv4 address 2.2.2.2 255.255.255.255
no shutdown
exit
interface GigabitEthernet0/0/0/0
ipv4 address 10.1.0.2 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/0/1
ipv4 address 10.2.0.2 255.255.255.0
no shutdown
exit
router isis CORE
is-type level-2-only
net 49.0001.0000.0000.0002.00
address-family ipv4 unicast
metric-style wide
exit
interface Loopback0
passive
address-family ipv4 unicast
exit
exit
interface GigabitEthernet0/0/0/0
point-to-point
address-family ipv4 unicast
exit
exit
interface GigabitEthernet0/0/0/1
point-to-point
address-family ipv4 unicast
exit
exit
exit
mpls ldp
router-id 2.2.2.2
interface GigabitEthernet0/0/0/0
exit
interface GigabitEthernet0/0/0/1
exit
exit
commit
PE1 configure
vrf C
address-family ipv4 unicast
import route-target
100:1
exit
export route-target
100:1
exit
exit
exit
interface Loopback0
ipv4 address 1.1.1.1 255.255.255.255
no shutdown
exit
interface GigabitEthernet0/0/0/1
ipv4 address 10.1.0.1 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/0/0
vrf C
ipv4 address 192.168.1.1 255.255.255.0
no shutdown
exit
router isis CORE
is-type level-2-only
net 49.0001.0000.0000.0001.00
address-family ipv4 unicast
metric-style wide
exit
interface Loopback0
passive
address-family ipv4 unicast
exit
exit
interface GigabitEthernet0/0/0/1
point-to-point
address-family ipv4 unicast
exit
exit
exit
mpls ldp
router-id 1.1.1.1
interface GigabitEthernet0/0/0/1
exit
exit
route-policy PASS
pass
end-policy
router bgp 100
bgp router-id 1.1.1.1
address-family vpnv4 unicast
exit
neighbor 3.3.3.3
remote-as 100
update-source Loopback0
address-family vpnv4 unicast
exit
exit
vrf C
rd 1:1
address-family ipv4 unicast
redistribute connected
exit
neighbor 192.168.1.2
remote-as 65001
address-family ipv4 unicast
route-policy PASS in
route-policy PASS out
as-override
exit
exit
exit
exit
commit
PE2 configure
vrf C
address-family ipv4 unicast
import route-target
100:1
exit
export route-target
100:1
exit
exit
exit
interface Loopback0
ipv4 address 3.3.3.3 255.255.255.255
no shutdown
exit
interface GigabitEthernet0/0/0/1
ipv4 address 10.2.0.3 255.255.255.0
no shutdown
exit
interface GigabitEthernet0/0/0/0
vrf C
ipv4 address 192.168.2.1 255.255.255.0
no shutdown
exit
router isis CORE
is-type level-2-only
net 49.0001.0000.0000.0003.00
address-family ipv4 unicast
metric-style wide
exit
interface Loopback0
passive
address-family ipv4 unicast
exit
exit
interface GigabitEthernet0/0/0/1
point-to-point
address-family ipv4 unicast
exit
exit
exit
mpls ldp
router-id 3.3.3.3
interface GigabitEthernet0/0/0/1
exit
exit
route-policy PASS
pass
end-policy
router bgp 100
bgp router-id 3.3.3.3
address-family vpnv4 unicast
exit
neighbor 1.1.1.1
remote-as 100
update-source Loopback0
address-family vpnv4 unicast
exit
exit
vrf C
rd 3:1
address-family ipv4 unicast
redistribute connected
exit
neighbor 192.168.2.2
remote-as 65001
address-family ipv4 unicast
route-policy PASS in
route-policy PASS out
as-override
exit
exit
exit
exit
commit
CE1 interface GigabitEthernet1
ip address 192.168.1.2 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 172.16.1.1 255.255.255.255
exit
router bgp 65001
neighbor 192.168.1.1 remote-as 100
network 172.16.1.1 mask 255.255.255.255
exit
CE2 interface GigabitEthernet1
ip address 192.168.2.2 255.255.255.0
no shutdown
exit
interface Loopback0
ip address 172.16.2.1 255.255.255.255
exit
router bgp 65001
neighbor 192.168.2.1 remote-as 100
network 172.16.2.1 mask 255.255.255.255
exit
Related labs
Where to start
The lessons are open to everyone, all guided labs are listed by track, and
plans explains what is free and what is not.
CCNA®, CCNP® and Cisco® are trademarks of Cisco Systems, Inc. zNetLaB is not affiliated with or endorsed by Cisco.
Try the simulator in your browser, no sign-up