zNetLaB › Guided labs › Service Provider
Troubleshoot: IOS XR L3VPN, one direction only
Service Provider Advanced 5 devices 2 checked tasks 100 points Plan lab
The XR provider core is built and every session is up, yet the two customer sites cannot ping each other. Find out why one PE holds the far route and the other does not, and fix it. 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
The XR provider core is built and every session is up, yet the two customer sites cannot ping each other. Find out why one PE holds the far route and the other does not, and fix it.
Your role: an engineer in the provider’s network operations centre. Level: Advanced Done when: all 2 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 starts with addresses (G1 192.168.1.2/24, L0 172.16.1.1/32) and BGP 65001 already configured. PE1 starts with and ISIS CORE, BGP 100 already configured. P starts with and ISIS CORE already configured. PE2 starts with and ISIS CORE, BGP 100 already configured. CE2 starts with addresses (G1 192.168.2.2/24, L0 172.16.2.1/32) and BGP 65001 already configured.
Known problems
The network worked and now does not: the scenario above says what users report. The cause is a configuration fault, not a cable. Find it with show commands (interfaces, routes, neighbours, running-config) before you change anything; fix only what is wrong.
Goals
PE2 holds CE1 loopback in VRF C (50 pts) CE1 reaches CE2 (50 pts)
The activity, in order
PE2 holds CE1 loopback in VRF C Compare show running-config vrf C on both PEs: PE2 imports 100:2 while PE1 exports 100:1. Add import route-target 100:1 under VRF C on PE2.Why: Each goal is a state the lab can check on the running device. Verify with: show route vrf C CE1 reaches CE2 With both PEs importing the other one routes, the return path exists.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
The XR provider core is built and every session is up, yet the two customer sites cannot ping each other. Find out why one PE holds the far route and the other does not, and fix it.
What you will be able to do
PE2 holds CE1 loopback in VRF C
CE1 reaches CE2
The network
Catalyst 8000V, ASR 9001 — 5 devices in all, already cabled.
Gi1 192.168.1.2/24 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 192.168.2.2/24 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
These are already configured when the lab opens — including, where this is a troubleshooting lab, the fault itself:
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:2
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
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 PE2 holds CE1 loopback in VRF C 50 On PE2: show route vrf C output matches 172\.16\.1\.1/32.
2 CE1 reaches CE2 50 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:
PE2 configure
vrf C
address-family ipv4 unicast
import route-target
100:1
exit
exit
exit
commit
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