SPlab 111

CCIE SP Lab 1 Workbook version 1.
1
Section 1. Implement, Optimize and Troubleshooting Core IP Technologies............................................... 5
1.1 IS-IS FOR IPV4 TROUBLESHOOTING – AS9 ........................................................................................ 5
PROBLEM: ........................................................................................................................................... 5
SOLUTION: ............................................................................................................................................ 6
VALIDATION: ......................................................................................................................................... 7
1.2 IS-IS FOR IPV6 TROUBLESHOOTING – AS9 ........................................................................................ 7
PROBLEM: ............................................................................................................................................. 8
1.3 IS-IS FOR IPV4 TROUBLESHOOTING – AS1009 ................................................................................10
1.4 OSPF FOR IPV6 TROUBLESHOOTING – AS1009 ..............................................................................11
1.5 IS-IS LEVEL 1 FOR AS9 AND AS1009 ..............................................................................................13
1.6 OSPFV3 HELLO .............................................................................................................................15
1.7 IBGP IPV4 UNICAST T ROUBLESHOOTING ........................................................................................16
1.8 IBGP IPV6 UNICAST T ROUBLESHOOTING ........................................................................................24
1.9 E BGP IPV4 UNICAST T ROUBLESHOOTING ........................................................................................31
1.10 E BGP IPV6 UNICAST T ROUBLESHOOTING ........................................................................................34
1.11 BGP IPV4 UNICAST PATH SELECTION ..............................................................................................37

1.12 MPLS LDP TROUBLESHOOTING ......................................................................................................38
1.13 MPLS TRAFFIC ENGINEERING -1 ......................................................................................................43
1.14 MPLS TRAFFIC ENGINEERING -2 ......................................................................................................47
1.15 IPV4 PIM-SM TROUBLESHOOTING .................................................................................................51
1.16 IPV4 PIM-SM RP .........................................................................................................................56
1.18 MPLS LDP AUTHENTICATION .........................................................................................................65
Section 2. Implement, Optimize and Troubleshooting Access/Edge connection technologies .................67
2.1 MULTILINK PPP .............................................................................................................................67
Section 3. Implement, Optimize and Troubleshooting L3 VPN Technologies.............................................69
3.1 IBGP VPN V4 TROUBLESHOOTING ...................................................................................................69
3.2 IBGP VPN V6 TROUBLESHOOTING ...................................................................................................75
3.3 INTRA AS VPN V4 ..........................................................................................................................79

3.4 INTRA AS VPN V6 ..........................................................................................................................85
3.5 INTER-AS VPN V4 ..........................................................................................................................91
3.6 INTER-AS VPN V6 ........................................................................................................................101
3.7 CARRIER SUPPORTING CARRIER - 1 ...............................................................................................110
3.8 CARRIER SUPPORTING CARRIER - 2 ...............................................................................................120
3.9 INTRA AS MULTICAST VPN ..........................................................................................................130
3.10 BGP IPV4 MDT ..........................................................................................................................134
2
Section 4. Implement, Optimize and Troubleshooting L2 VPN Technologies...........................................142
4.1 PPP OVER MPLS .........................................................................................................................142
4.2 FRAME RELAY OVER L2TPV3 ........................................................................................................143
4.3 VPLS ..........................................................................................................................................146
Section 5. Useful Command Aliases ..........................................................................................................148
3
lo0
.0.16
XYZ Site 2
IS-IS L2 Second-level customer network
CCIE SP Lab1 IPv4 Diagram – first two octets 192.9.
E0/0 R16 E0/1
.146.16 .156.16
lo0 vrf XYZ vrf XYZ vrf XYZ vrf XYZ

172.9.0.24 E0/0 lo1 lo1 E0/0
.146.14 .0.14 .0.15 .156.15
IOL125 IOL126
E0/2 E0/2
FR SW .145.14.145.15
R28 R24 R14 R15
S2/0
SW1 SW2
E0/2 E0/1 lo0 lo0 E0/1
.214.24
Vlan 104 .143.14 .0.14 .0.15 .157.15 VPN customer network
Second-level customer network R28 S2/3 vrf ABC AS112 OSPF Area 0 – first two octets 172.9.
lo0 lo1
– first two octets 192.9. R28 S2/1
Gi0/0/0/4
.0.17 vrf ABC .0.1 vrf ABC vrf ABC vrf ABC ABC Site 2
vrf ABC
G
lo0 i0
.143.3
vrf XYZ lo1 FR lo0 lo0 /0 lo1 lo1
Lo1 .0.9 lo0 .0.2 .0.2 / 0/ vrf ABC
.0.9 5 .0.3 .0.7
E0/0
.0.17 S2/0 .0.1
.157.7
E0/0 Gi0/0/0/0
Vrf XYZ E0/0 Gi0/0/0/0
.197.17 .19.9 12.1
E0/2 23.2 Gi0/0/0/0 FR
vrf ABC Gi0/0/0/2 Gi0/0/0/2 Gi0/0/0/2 .37.3 E0/2 S2/0
.179.17 S2/0
R17 E0/2 R9 19.1 R1 12.2 R2 23.3 R3 .37.7 R7 .217.21 R21
XYZ Site 3 .197.9
/3
Gi0/0/0/1
.34.3
E0/1
.35.3
E0/1 Gi0/0/0/1
/0/0
E0/1 Gi0/0/0/1 lo0 lo0
16.1 25.2 .78.7
.178.17 .109.9
Gi0
.0.3 .0.7 lo0
lo2 172.9.0.21
Core provider network

– first two octets 172.9.
VPN customer network

.0.22
E0/0 ABC Site 3 (for Tunnel)
.179.19
OSPF AS178 AS1009 AS9
Area 0 EIGRP 100
R19 IS-IS L2 IS-IS L1
lo0
E0/1 vrf XYZ vrf ABC
.0.19 lo0
.189.19 Lo1 lo1
.0.18 .0.10
.0.5
Gi0/0/0/1
lo0 lo0 lo0 lo0
E0/1 E0/1 .0.10 .0.6 E0/1
.34.4
lo0 E0/1 E0/2 .0.4 .0.8
.109.10 E0/1
.178.18 .0.18 .16.6
.25.5 .35.5 .78.8
E0/0
.45.5 Gi0/0/0/0
E0/0 E0/0 S2/0 S2/0 48.4
Gi0/0/0/2 E0/2
.108.18 .106.10 .56.6 .56.5 S2/0
Vrf XYZ 45.4 48.8
S2/0
E0/2 R18 vrf ABC R10 E0/2 R6 ppp R5 R8 223.22 R22
.189.18 E0/2 .106.6 R4 vrf ABC
.108.10
/0
/ 4 AS112 E0/0 lo2
/0
vrf ABC
Gi0/0/0/3
114.4
i0 vrf ABC vrf ABC .128.8 .0.88
G
lo1 lo1 (for Tunnel) lo0
.0.4 .0.8 172.9.0.22
OSPF Area 0 VPN customer network
lo0 lo0
E0/3 E0/1 .0.11 .0.12 E0/1 – first two octets 172.9.
Vlan 101 .114.11 .128.12
E0/2
ABC Site 1
E0/2
.112.11 .112.12
SW3
R20 R23 IOL127 R11 R12
vrf XYZ vrf XYZ
vrf XYZ lo0 E0/0 vrf XYZ
lo0 E0/0
lo0 lo1 .0.13 lo1
Service provider network 9.9.0.0 172.9.0.23 .113.11 .123.12
9.9.0.20 .0.11 .0.12
VPN customer network 172.9.0.0 E0/0
E0/1
Second-level customer 192.9.0.0 .113.13
.123.13 XYZ Site 1
All links subnet masks are /24
IS-IS L2
All loopbacks masks are /32 R13
Second-level customer network – first two octets 192.9.
4
Section 1. Implement, Optimize and Troubleshooting Core IP Technologies
1.1 IS-IS FOR IPV4 TROUBLESHOOTING – AS9
IS-IS for IPv4 routing on the routers in AS9 has been pre-configured as shown in the Table 1.
All link subnets are /24, all loopbacks /32.
Table 1: Preconfigured IPv4 addresses in the Core IGP, AS9

Router IS-IS Net Interface IPv4 address
R2 47.0009. Loopback0 9.9.0.2
47.0009. GigabitEthernet0/0/0/0 9.9.23.2
R3 47.0009. Loopback0 9.9.0.3
R4 47.0009. Loopback0 9.9.0.4
R5 47.0009. Loopback0 9.9.0.5
47.0009. Ethernet0/0 9.9.45.5
47.0009. Ethernet0/1 9.9.25.5
47.0009. Ethernet0/2 9.9.35.5
R7 47.0009. Loopback0 9.9.0.7
47.0009. Ethernet0/1 9.9.78.7
47.0009. Ethernet0/2 9.9.37.7
R8 47.0009. Loopback0 9.9.0.8
47.0009. Ethernet0/1 9.9.78.8
47.0009. Ethernet0/2 9.9.48.8
PROBLEM:
R2 and R4 cannot establish IS-IS neighbor relationship. Fix the problem to ensure that IS-IS works
properly. (Score: 2 points).
5
SOLUTION:
Warning: Configuration strings required to fulfill this particular task only are shown! All other string
that may persist in the configuration required for other tasks.
NB! All L1 routers in the same Area must have the same Net value – 47.0009. in this case
(IOS)log-adjacency-changes all/(IOS-XR)log adjacency changes – it is not required but very
helpful during configuration and troubleshooting. Logging of the IS-IS state changes is disabled by
default in both IOS and IOS-XR.
R2: R5:
router isis 1 router isis
net 47.0009.0000.0000.2222.00 net 47.0009.0000.0000.5555.00
log adjacency changes log-adjacency-changes all
address-family ipv4 unicast !
! interface Loopback0
interface Loopback0 ip address 9.9.0.5 255.255.255.255
address-family ipv4 unicast ip router isis
! !
! interface Ethernet0/0
interface GigabitEthernet0/0/0/0 description Link to R4 Gig 0/0/0/2
address-family ipv4 unicast ip address 9.9.45.5 255.255.255.0
! ip router isis
! !
interface GigabitEthernet0/0/0/1 interface Ethernet0/1
address-family ipv4 unicast description Link to R2 Gi0/0/0/1
! ip address 9.9.25.5 255.255.255.0
! ip router isis
!
interface Ethernet0/2
description Link to R3 Gi0/0/0/3
ip address 9.9.35.5 255.255.255.0
ip router isis
!
R3: R4:
router isis 1 router isis 1
net 47.0009.0000.0000.3333.00 net 47.0009.0000.0000.4444.00
log adjacency changes log adjacency changes
address-family ipv4 unicast address-family ipv4 unicast
!
interface Loopback0 address-family ipv4 unicast
! !
! interface GigabitEthernet0/0/0/0
interface GigabitEthernet0/0/0/0 address-family ipv4 unicast
! !
! !
!
!
interface GigabitEthernet0/0/0/3
address-family ipv4 unicast
!
6
R7: R8:
router isis router isis
net 47.0009.0000.0000.7777.00 net 47.0009.0000.0000.8888.00
log-adjacency-changes all log-adjacency-changes all
! !
interface Loopback0 interface Loopback0
ip address 9.9.0.7 255.255.255.255 ip address 9.9.0.8 255.255.255.255
ip router isis ip router isis
! !
interface Ethernet0/1 interface Ethernet0/1
description Link to R8 E0/1 description Link to R7 E0/1
! !
description Link to R3 Gi0/0/0/0 description Link to R4 Gi0/0/0/0
! !
VALIDATION:
R5#sh isis neighbors
Tag null:
System Id Type Interface IP Address State Holdtime Circuit Id
R2 L1 Et0/1 9.9.25.2 UP 25 R5.03
R3 L1 Et0/2 9.9.35.3 UP 21 R5.04
R4 L1 Et0/0 9.9.45.4 UP 27 R5.02
RP/0/0/CPU0:R2#sh isis neighbors

Mon Dec 10 12:52:10.739 MSK
IS-IS 1 neighbors:
System Id Interface SNPA State Holdtime Type IETF-NSF
R3 Gi0/0/0/0 0205.a986.18a6 Up 29 L1 Capable
R5 Gi0/0/0/1 aabb.cc00.6910 Up 8 L1 Capable
All link prefixes are /64 in length, all loopbacks - /128.

R2 47.0009. Loopback0 2002:9:9::2
47.0009. GigabitEthernet0/0/0/0 2002:9:9:23::2
R3 47.0009. Loopback0 2002:9:9::3
R4 47.0009. Loopback0 2002:9:9::4
47.0009. GigabitEthernet0/0/0/0 2002:9:9:48:4
7
R5 47.0009. Loopback0 2002:9:9::5
47.0009. Ethernet0/0 2002:9:9:45.5
47.0009. Ethernet0/1 2002:9:9:25.5
47.0009. Ethernet0/2 2002:9:9:35.5
R7 47.0009. Loopback0 2002:9:9::7
47.0009. Ethernet0/1 2002:9:9:78::7
47.0009. Ethernet0/2 2002:9:9:37::7
R8 47.0009. Loopback0 2002:9:9::8
47.0009. Ethernet0/1 2002:9:9:78:8
47.0009. Ethernet0/2 2002:9:9:48::8
PROBLEM:
R5’s routing table should contain two equal paths to IPv6 network of 2002:9:9:78::/64, but there is
only one there. Fix the problem to ensure that IS-IS works properly. (Score: 2 points).
SOLUTION:
NB!
- The command metric-style wide in the address-family ipv4 unicast is required to make MPLS
traffic-engineering works
- By default IOS-XR runs in multiple-topology mode that means IS-IS SPF process runs separately
for IPv4 and IPv6; IOS runs in single-topology mode, so If you’d like to use IS-IS for both IPv4
and IPv6 routing you need to configure multiple-topology in IOS or single-topology in IOS-XR.
Please read carefully the task and preconfigured values in routers configurations. If
preconfigured value for IOS routers is multiple-topology please left IOS-XR configuration by
default. If IOS-XR routers contain preconfigured value single-topology please left IOS
configuration by default.
R2: R5:
router isis 1 ipv6 unicast-routing
net 47.0009.0000.0000.2222.00 ipv6 cef ! turned on automatically after
address-family ipv4 unicast previous command
metric-style wide !
address-family ipv6 unicast ipv6 address 2002:9:9::5/128
single-topology ipv6 router isis
! !
interface Loopback0 interface Ethernet0/0
address-family ipv6 unicast description Link to R4 Gig 0/0/0/2
! ipv6 address 2002:9:9:45::5/64
! ipv6 router isis
interface GigabitEthernet0/0/0/0 !
address-family ipv6 unicast interface Ethernet0/1
! description Link to R2 Gi0/0/0/1
! ipv6 address 2002:9:9:25::5/64
interface GigabitEthernet0/0/0/1 ipv6 router isis
ipv6 address 2002:9:9:35::5/64
ipv6 router isis
8
R3: R4:
net 47.0009.0000.0000.3333.00 net 47.0009.0000.0000.4444.00
metric-style wide metric-style wide
! !
single-topology single-topology
! !
! !
! !
interface GigabitEthernet0/0/0/0 interface GigabitEthernet0/0/0/0
! !
! !
! !
! !
! !
! !
!
!
!
R7: R8:
ipv6 address 2002:9:9::7/128 ipv6 address 2002:9:9::8/128
ipv6 router isis ipv6 router isis
! !
ipv6 address 2002:9:9:78::7/64 ipv6 address 2002:9:9:78::8/64
! !
! !
VALIDATION:
R5#sh ipv6 route 2002:9:9:78::/64
Routing entry for 2002:9:9:78::/64

Known via "isis", distance 115, metric 30, type level-1
Route count is 2/2, share count 0
Routing paths:
FE80::28:8CFF:FEAE:DE6C, Ethernet0/2
Last updated 18:24:15 ago
FE80::B7:B3FF:FE1A:3224, Ethernet0/0
Last updated 18:24:15 ago
9
All link subnets are /24, all loopbacks /32.

R9 47.0109. Loopback0 9.9.0.9
47. 0109. Ethernet0/0 9.9.19.9
47. 0109. Ethernet0/1 9.9.109.9
R10 47.0110. Loopback0 9.9.0.10
47. 0110. Ethernet0/0 9.9.106.10
47. 0110. Ethernet0/1 9.9.109.10
R1 47.0101. Loopback0 9.9.0.1
47. 0101. GigabitEthernet0/0/0/1 9.9.16.1
47. 0101. GigabitEthernet0/0/0/2 9.9.19.1
R6 47.0106. Loopback0 9.9.0.6
47. 0106. Ethernet0/1 9.9.16.6
47. 0106. Ethernet0/2 9.9.106.6
PROBLEM:
R10 should have CLNS neighborship with R9 of type L2 only. Fix the problem so that the
neighborship type to R9 will be L2 only.
SOLUTION:
R9: R10:
net 47.0109.0000.0000.9999.00 net 47.0110.0000.0000.1010.00
is-type level-2-only is-type level-2-only
log-adjacency-changes all log-adjacency-changes all
! !
! !
description Link to R1 Gi0/0/0/2 description Link to R6 E0/2
! !
! !
10
R1: R6:
is-type level-2-only net 47.0106.0000.0000.6666.00
net 47.0101.0000.0000.1111.00 is-type level-2-only
log adjacency changes log-adjacency-changes all
address-family ipv4 unicast ip router isis
! ip pim sparse-mode
! !
address-family ipv4 unicast description Link to R1 Gi0/0/0/1
! ip address 9.9.16.6 255.255.255.0
! ip router isis
! description Link to R10 E0/0 via SW3 E1/1
! ip address 9.9.106.6 255.255.255.0
! ip router isis
!
VALIDATION:
R10#sh isis neighbors
Tag null:
System Id Type Interface IP Address State Holdtime Circuit Id
R20 L2 Mu1 9.9.120.20 UP 23 00
R6 L2 Et0/0 9.9.106.6 UP 23 R10.02
R9 L2 Et0/1 9.9.109.9 UP 25 R10.03
1.4 OSPF FOR IPV6 TROUBLESHOOTING – AS1009
OSPFv3 for IPv6 routing on the routers in AS1009 has been pre-configured as shown in the Table 4.
All link prefixes are /64 in length, all loopbacks are /128.

Router OSPF Area Interface IPv4 address
R9 1009 Loopback0 2002:9:9::9
1009 Ethernet0/0 2002:9:9:19::9
1009 Ethernet0/1 2002:9:9:109::9
R10 1009 Loopback0 2002:9:9::10
1009 Ethernet0/0 2002:9:9:106::10
1009 Ethernet0/1 2002:9:9:109::10
R1 0 Loopback0 2002:9:9::1
0 GigabitEthernet0/0/0/1 2002:9:9:16::1
1009 GigabitEthernet0/0/0/2 2002:9:9:19::1
R6 0 Loopback0 2002:9:9::6
0 Ethernet0/1 2002:9:9:16::6
1009 Ethernet0/2 2002:9:9:106::6
PROBLEM:
R9 and R10 cannot establish OSPFv3 neighborship, fix the problem and ensure they can exchange
OSPF v3 update.
11
SOLUTION:
R9: R10:
ipv6 router ospf 1009 ipv6 router ospf 1009
router-id 9.9.0.9 router-id 9.9.0.10
! !
ipv6 address 2002:9:9::9/128 ipv6 address 2002:9:9::10/128
ipv6 ospf 1009 area 1009 ipv6 ospf 1009 area 1009
! !
! !
! !
R1: R6:
router ospfv3 1009 ipv6 router ospf 1009
area 0 router-id 9.9.0.6
interface Loopback0 !
passive interface Loopback0
! ipv6 address 2002:9:9::6/128
interface GigabitEthernet0/0/0/1 ipv6 ospf 1009 area 0
! !
area 1009 description Link to R1 Gi0/0/0/1
interface GigabitEthernet0/0/0/2 ipv6 address 2002:9:9:16::6/64
! ipv6 ospf 1009 area 0
! !
description Link to R10 E0/0 via SW3 E1/1
ipv6 address 2002:9:9:106::6/64
ipv6 ospf 1009 area 1009
!
VALIDATION:
R9#sh ipv6 ospf neighbor
OSPFv3 Router with ID (9.9.0.9) (Process ID 1009)
Neighbor ID Pri State Dead Time Interface ID Interface

9.9.0.10 1 FULL/BDR 00:00:39 3 Ethernet0/1
R10#sh ipv6 ospf neighbor
OSPFv3 Router with ID (9.9.0.10) (Process ID 1009)
Neighbor ID Pri State Dead Time Interface ID Interface

9.9.0.9 1 FULL/DR 00:00:32 3 Ethernet0/1
12
1.5 IS-IS LEVEL 1 FOR AS9 AND AS1009
Configure IS-IS in the routers in AS9 and AS1009 (Refer to questions 1.1 and 1.3 for routers’ names,
interfaces and Areas’ specifications.
- Configure the routers’ interfaces in AS9 as IS-IS Level-1-only. Ensure that these subnets are
shown in the routing table as IS-IS routes and that you can ping the subnets under the IS-IS
domain from any of the routers via IPv4 and IPv6.
- Configure the routers’ interfaces in AS1009 as IS-IS Level-2-only. Ensure that these subnets are
shown in the routing table as IS-IS routes and that you can ping the subnets under the IS-IS
domain from any of the routers via IPv4.
SOLUTION:
This task can be solved by two methods: since all interfaces of IS-IS routers in the AS9 and
AS1009 should be in the L1 and L2 areas accordingly, and then command is-type level-1 or is-
type level-2 only in the routing process will be enough. Another method is to define the IS-IS
interface type on the interface level by the command isis circuit-type level-1 (IOS) or circuit-
type level-1 (IOS-XR). Please read the task wording and preconfigured IS-IS parameters precisely
to choose which method is the most appropriate for this case. Both methods are shown in the
tables below.
AS9:
R2: R5:
is-type-level-1 is-type level-1
! !
circuit-type level-1 isis circuit-type level-1
! !
! !
interface GigabitEthernet0/0/0/1 description Link to R2 Gi0/0/0/1
!
! !
isis circuit-type level-1
!
13
R3: R4:
is-type level-1 is-type level-1
! !
circuit-type level-1 circuit-type level-1
! !
! !
! !
! !
! !
! !
! !
!
circuit-type level-1
!
R7: R8:
is-type level-1 is-type level-1
! !
isis circuit-type level-1 isis circuit-type level-1
! !
! !
! !
AS1009:
R9: R10:
! !
isis circuit-type level-2-only isis circuit-type level-2-only
! !
! !
! !
R1: R6:
! !
circuit-type level-2-only isis circuit-type level-2-only
! !
interface GigabitEthernet0/0/0/1 isis circuit-type level-2-only
circuit-type level-2-only !
! isis circuit-type level-2-only
circuit-type level-2-only
!
!
!
14
1.6 OSPFV3 HELLO
Configure OSPFv3 on routers in AS 1009 (Refer to Question 1.4 for router names, interfaces and
areas specification).
- Configure R1 and R6 so that OSPFv3 hello interval is 5 seconds on VLAN 18 (Link R1 Gi0/0/0/1 –
R6 E0/1 in our topology)
- Ensure that these subnets are shown in the routing table as OSPF routers and that you can ping
subnets in the OSPFv3 domain from any of the routers through IPv6 ???
SOLUTION:
R1: R6:
router ospfv3 1009 interface Ethernet0/1

area 0 description Link to R1 Gi0/0/0/1
interface GigabitEthernet0/0/0/1 ipv6 ospf 1009 area 0
hello-interval 5 ipv6 ospf hello-interval 5
!
!
VALIDATION:
R6#sh ipv6 ospf interface e0/1
Ethernet0/1 is up, line protocol is up
Link Local Address FE80::A8BB:CCFF:FE00:6A10, Interface ID 3
Area 0, Process ID 1009, Instance ID 0, Router ID 9.9.0.6
Network Type BROADCAST, Cost: 10
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 9.9.0.6, local address FE80::A8BB:CCFF:FE00:6A10
Backup Designated router (ID) 9.9.0.1, local address FE80::80:45FF:FE67:6EA9
Timer intervals configured, Hello 5, Dead 20, Wait 20, Retransmit 5
Hello due in 00:00:03
Graceful restart helper support enabled
Index 1/2/2, flood queue length 0
Next 0x0(0)/0x0(0)/0x0(0)
Last flood scan length is 0, maximum is 6
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 9.9.0.1 (Backup Designated Router)
Suppress hello for 0 neighbor(s)
RP/0/0/CPU0:R1#sh ospfv3 interface gi0/0/0/1

Tue Dec 11 16:23:27.799 MSK
GigabitEthernet0/0/0/1 is up, line protocol is up
Link Local address fe80::80:45ff:fe67:6ea9, Interface ID 4
Area 0, Process ID 1009, Instance ID 0, Router ID 9.9.0.1
Network Type BROADCAST, Cost: 1
Transmit Delay is 1 sec, State BDR, Priority 1
Designated Router (ID) 9.9.0.6, local address fe80::a8bb:ccff:fe00:6a10
Backup Designated router (ID) 9.9.0.1, local address fe80::80:45ff:fe67:6ea9
Timer intervals configured, Hello 5, Dead 20, Wait 20, Retransmit 5
Index 0/2/1, flood queue length 0
Next 0(0)/0(0)/0(0)
Last flood scan length is 8, maximum is 8
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 9.9.0.6 (Designated Router)
Suppress hello for 0 neighbor(s)
Reference count is 6
15
1.7 IBGP IPV4 UNICAST TROUBLESHOOTING
R2, R3, R4, R5, R7 and R8 have been preconfigured to belong to AS9. R1, R6, R9, R10 have been
preconfigured to belong to AS 1009.
- R2 and R5 act as the route reflectors for iBGP IPv4 unicast within the AS9. iBGP IPv4 sessions
should NOT be established between R3, R4, R7 and R8.
- R1 and R6 act as the route reflectors for iBGP IPv4 unicast within the AS1009. An iBGP IPv4
session should not be established between R9 and R10.
- The interface Loopback0 address is used to establish iBGP IPv4 sessions.
- All routers Loopback0 networks are advertised as BGP IPv4 unicast updates.
CCIE SP Lab1 iBGP IPv4 Unicast Diagram

R24 SW1 SW2
lo0 lo0 iBGP

.0.9 lo0 .0.2
AS1009 BGP RR .0.1
E0/0 Gi0/0/0/2 Gi0/0/0/0
Gi0/0/0/0
.19.9 19.1 12.1
23.2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 .37.3 E0/2
iBGP iBGP S2/0
R9 R1 12.2 R2 23.3 R3 .37.7 R7 R21
/3
Gi0/0/0/1
.34.3
E0/1
.35.3
E0/1 Gi0/0/0/1 AS9 BGP RR
/0/0
.109.9 lo0 .78.7 lo0
16.1
Gi0 .0.3 .0.7
Gi0/0/0/1
GP
25.2
iBGP
GP
iB
iB
G
iB
P
iBGP
iBGP
AS9
iB
iBGP
GP
AS1009 P
iBG
lo0
.0.5
Gi0/0/0/1
lo0 lo0 lo0 lo0

.0.10 E0/1 .0.6 E0/1
.34.4
E0/1 E0/2 .0.4 .0.8

.16.6 E0/1
.109.10
.25.5 .35.5 .78.8
iBGP
Gi0/0/0/0
S2/0 S2/0 iBGP 48.4 E0/2
.56.6 .56.5 48.8
R10 E0/0 E0/2 R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
.106.10 .106.6 .45.5 45.4 R4
AS1009 BGP RR AS9 BGP RR
iBGP
PROBLEM:
R7 doesn’t have R3 Loopback0 network in BGP IPv4 unicast table. Fix the problem and ensure that IPv4
unicasts are delivered properly within the corresponding AS.
16
SOLUTION:
AS9:
R2: - AS9 BGP IPv4 Unicast Route Reflector R5: - AS9 BGP IPv4 Unicast Route Reflector
router bgp 9 router bgp 9
bgp router-id 9.9.0.2 bgp router-id 9.9.0.5
network 9.9.0.2/32 network 9.9.0.5/32
! !
neighbor 9.9.0.3 neighbor 9.9.0.3
remote-as 9 remote-as 9
update-source Loopback0 update-source Loopback0
route-reflector-client route-reflector-client
! !
! !
! !
neighbor 9.9.0.5 ! Other route reflector neighbor 9.9.0.2 ! Other route reflector
! !
! !
! !
R3: R4:
network 9.9.0.3/32 network 9.9.0.4/32
! !
! !
! !
R7: R8:
bgp log-neighbor-changes bgp log-neighbor-changes
no bgp default ipv4-unicast no bgp default ipv4-unicast
neighbor 9.9.0.2 remote-as 9 neighbor 9.9.0.2 remote-as 9
neighbor 9.9.0.2 update-source Loopback0 neighbor 9.9.0.2 update-source Loopback0
! !
address-family ipv4 address-family ipv4
network 9.9.0.7 mask 255.255.255.255 network 9.9.0.8 mask 255.255.255.255
neighbor 9.9.0.2 activate neighbor 9.9.0.2 activate
exit-address-family exit-address-family
! !
17
AS1009:
R9: R10:

bgp log-neighbor-changes bgp log-neighbor-changes
no bgp default ipv4-unicast no bgp default ipv4-unicast
! !
! !
R1: - AS1009 BGP IPv4 Unicast Route Reflector R6: - AS1009 BGP IPv4 Unicast Route Reflector

address-family ipv4 unicast bgp log-neighbor-changes
network 9.9.0.1/32 no bgp default ipv4-unicast
! neighbor 9.9.0.1 remote-as 1009
neighbor 9.9.0.6 ! other route-reflector neighbor 9.9.0.1 update-source Loopback0
remote-as 1009 neighbor 9.9.0.9 remote-as 1009
update-source Loopback0 neighbor 9.9.0.9 update-source Loopback0
address-family ipv4 unicast neighbor 9.9.0.10 remote-as 1009
! neighbor 9.9.0.10 update-source Loopback0
! !
neighbor 9.9.0.9 address-family ipv4
remote-as 1009 network 9.9.0.6 mask 255.255.255.255
update-source Loopback0 neighbor 9.9.0.1 activate ! other route-reflecor
address-family ipv4 unicast neighbor 9.9.0.9 activate
route-reflector-client neighbor 9.9.0.9 route-reflector-client
! neighbor 9.9.0.10 activate
! neighbor 9.9.0.10 route-reflector-client
neighbor 9.9.0.10 !
remote-as 1009
update-source Loopback0
route-reflector-client
!
VALIDATION:
{----------------------------------------------------AS 9------------------------------------------------------}
R2:
RP/0/0/CPU0:R2#sh bgp ipv4 uni summary

Wed Dec 12 17:27:27.990 MSK
BGP router identifier 9.9.0.2, local AS number 9
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000 RD version: 23
BGP main routing table version 23
BGP scan interval 60 secs
BGP is operating in STANDALONE mode.
Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 23 23 23 23 23 23
Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd
9.9.0.3 0 9 1628 1652 23 0 0 1d03h 1
9.9.0.4 0 9 1627 1645 23 0 0 1d03h 1
9.9.0.5 0 9 1805 1642 23 0 0 1d03h 5 ! other RR
9.9.0.7 0 9 1797 1644 23 0 0 1d03h 1
9.9.0.8 0 9 1802 1651 23 0 0 1d03h 1
18
RP/0/0/CPU0:R2#sh bgp ipv4 uni
Wed Dec 12 17:31:29.753 MSK

Status codes: s suppressed, d damped, h history, * valid, > best
i - internal, r RIB-failure, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 9.9.0.2/32 0.0.0.0 0 32768 i
*>i9.9.0.3/32 9.9.0.3 0 100 0 i
* i 9.9.0.3 0 100 0 i
*>i9.9.0.4/32 9.9.0.4 0 100 0 i
* i 9.9.0.4 0 100 0 i
*>i9.9.0.5/32 9.9.0.5 0 100 0 i
* i9.9.0.7/32 9.9.0.7 0 100 0 i
*>i 9.9.0.7 0 100 0 i
* i9.9.0.8/32 9.9.0.8 0 100 0 i
*>i 9.9.0.8 0 100 0 i
R5:
R5#sh ip bgp ipv4 uni sum

BGP table version is 15, main routing table version 15
10 network entries using 1480 bytes of memory
14 path entries using 896 bytes of memory
6/4 BGP path/bestpath attribute entries using 816 bytes of memory
4 BGP rrinfo entries using 96 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 3312 total bytes of memory
BGP activity 22/0 prefixes, 29/3 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
9.9.0.2 4 9 1652 1816 15 0 0 1d03h 5 ! other RR
9.9.0.3 4 9 1636 1815 15 0 0 1d03h 1
9.9.0.4 4 9 1637 1816 15 0 0 1d03h 1
9.9.0.7 4 9 1806 1818 15 0 0 1d03h 1
9.9.0.8 4 9 1804 1819 15 0 0 1d03h 1
R5#sh ip bgp ipv4 uni
BGP table version is 15, local router ID is 9.9.0.5
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
RPKI validation codes: V valid, I invalid, N Not found
r>i9.9.0.2/32 9.9.0.2 0 100 0 i
r i9.9.0.3/32 9.9.0.3 0 100 0 i
r>i 9.9.0.3 0 100 0 i
r i9.9.0.4/32 9.9.0.4 0 100 0 i
r>i 9.9.0.4 0 100 0 i
*> 9.9.0.5/32 0.0.0.0 0 32768 i
r i9.9.0.7/32 9.9.0.7 0 100 0 i
r>i 9.9.0.7 0 100 0 i
r i9.9.0.8/32 9.9.0.8 0 100 0 i
R3:
RP/0/0/CPU0:R3#sh bgp ipv4 unicast summary
Thu Dec 13 23:58:22.355 MSK


Speaker 26 26 26 26 26 26
19
9.9.0.2 0 9 3483 3458 26 0 0 2d09h 5
9.9.0.5 0 9 3821 3457 26 0 0 2d09h 5
RP/0/0/CPU0:R3#sh bgp ipv4 unicast
Fri Dec 14 00:01:13.269 MSK

i
*>i9.9.0.2/32 9.9.0.2 0 100 0 i
* i 9.9.0.2 0 100 0 i
*> 9.9.0.3/32 0.0.0.0 0 32768 i
*>i9.9.0.4/32 9.9.0.4 0 100 0 i
* i 9.9.0.4 0 100 0 i
* i9.9.0.5/32 9.9.0.5 0 100 0 i
*>i 9.9.0.5 0 100 0 i
*>i9.9.0.7/32 9.9.0.7 0 100 0 i
* i 9.9.0.7 0 100 0 i
*>i9.9.0.8/32 9.9.0.8 0 100 0 i
* i 9.9.0.8 0 100 0 i
R4:
Fri Dec 14 00:06:46.507 MSK


Speaker 31 31 31 31 31 31
9.9.0.2 0 9 3484 3467 31 0 0 2d09h 5
9.9.0.5 0 9 3831 3467 31 0 0 2d09h 5

Fri Dec 14 00:10:13.085 MSK
*>i9.9.0.2/32 9.9.0.2 0 100 0 i
* i 9.9.0.2 0 100 0 i
*>i9.9.0.3/32 9.9.0.3 0 100 0 i
* i 9.9.0.3 0 100 0 i
*> 9.9.0.4/32 0.0.0.0 0 32768 i
* i9.9.0.5/32 9.9.0.5 0 100 0 i
*>i 9.9.0.5 0 100 0 i
*>i9.9.0.7/32 9.9.0.7 0 100 0 i
* i 9.9.0.7 0 100 0 i
*>i9.9.0.8/32 9.9.0.8 0 100 0 i
* i 9.9.0.8 0 100 0 i
20
R7:
R7#sh ip bgp ipv4 unicast summary

3 BGP extended community entries using 72 bytes of memory

9.9.0.2 4 9 3496 3833 18 0 0 2d09h 5
9.9.0.5 4 9 3847 3828 18 0 0 2d09h 5
R7#sh ip bgp ipv4 unicast

r i9.9.0.2/32 9.9.0.2 0 100 0 i
r>i 9.9.0.2 0 100 0 i
r>i9.9.0.3/32 9.9.0.3 0 100 0 i
r i 9.9.0.3 0 100 0 i
r>i9.9.0.4/32 9.9.0.4 0 100 0 i
r i 9.9.0.4 0 100 0 i
r i9.9.0.5/32 9.9.0.5 0 100 0 i
r>i 9.9.0.5 0 100 0 i
*> 9.9.0.7/32 0.0.0.0 0 32768 i
r>i9.9.0.8/32 9.9.0.8 0 100 0 i
r i 9.9.0.8 0 100 0 i
R8:

9.9.0.2 4 9 3565 3911 18 0 0 2d10h 5
9.9.0.5 4 9 3915 3903 18 0 0 2d10h 5

r i9.9.0.2/32 9.9.0.2 0 100 0 i
r>i 9.9.0.2 0 100 0 i
r>i9.9.0.3/32 9.9.0.3 0 100 0 i
r i 9.9.0.3 0 100 0 i
r>i9.9.0.4/32 9.9.0.4 0 100 0 i
r i 9.9.0.4 0 100 0 i
r i9.9.0.5/32 9.9.0.5 0 100 0 i
r>i 9.9.0.5 0 100 0 i
r>i9.9.0.7/32 9.9.0.7 0 100 0 i
r i 9.9.0.7 0 100 0 i
*> 9.9.0.8/32 0.0.0.0 0 32768 i
21
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:


9.9.0.1 4 1009 3562 3917 14 0 0 2d11h 3
9.9.0.6 4 1009 3924 3917 14 0 0 2d11h 3

r i9.9.0.1/32 9.9.0.1 0 100 0 i
r>i 9.9.0.1 0 100 0 i
r i9.9.0.6/32 9.9.0.6 0 100 0 i
r>i 9.9.0.6 0 100 0 i
*> 9.9.0.9/32 0.0.0.0 0 32768 i
r>i9.9.0.10/32 9.9.0.10 0 100 0 i
r i 9.9.0.10 0 100 0 i
R10:
R10#sh ip bgp ipv4 uni summary

9.9.0.1 4 1009 3568 3916 14 0 0 2d11h 9
9.9.0.6 4 1009 3930 3912 14 0 0 2d11h 9


r i9.9.0.1/32 9.9.0.1 0 100 0 i
r>i 9.9.0.1 0 100 0 i
r i9.9.0.6/32 9.9.0.6 0 100 0 i
r>i 9.9.0.6 0 100 0 i
r>i9.9.0.9/32 9.9.0.9 0 100 0 i
r i 9.9.0.9 0 100 0 i
*> 9.9.0.10/32 0.0.0.0 0 32768 i
22
R1: - AS 1009 iBGP IPv4 unicast Route Reflector
Fri Dec 14 01:39:18.089 MSK

Speaker 32 32 32 32 32 32

9.9.0.6 0 1009 3938 3571 32 0 0 2d07h 3 ! other RR
9.9.0.9 0 1009 3924 3568 32 0 0 2d11h 1
9.9.0.10 0 1009 3921 3571 32 0 0 2d11h 1

Fri Dec 14 01:41:28.520 MSK
*> 9.9.0.1/32 0.0.0.0 0 32768 i
*>i9.9.0.6/32 9.9.0.6 0 100 0 i
* i9.9.0.9/32 9.9.0.9 0 100 0 i
*>i 9.9.0.9 0 100 0 i
* i9.9.0.10/32 9.9.0.10 0 100 0 i
*>i 9.9.0.10 0 100 0 i
R6: - AS 1009 iBGP IPv4 unicast Route Reflector
R6#sh ip bgp ipv4 uni summary

9.9.0.1 4 1009 3363 3702 15 0 0 2d07h 3 ! other RR
9.9.0.9 4 1009 3931 3939 15 0 0 2d11h 1
9.9.0.10 4 1009 3923 3941 15 0 0 2d11h 1

r>i9.9.0.1/32 9.9.0.1 0 100 0 i
*> 9.9.0.6/32 0.0.0.0 0 32768 i
r i9.9.0.9/32 9.9.0.9 0 100 0 i
r>i 9.9.0.9 0 100 0 i
r i9.9.0.10/32 9.9.0.10 0 100 0 i
r>i 9.9.0.10 0 100 0 i
23
1.8 IBGP IPV6 UNICAST TROUBLESHOOTING
R2, R3, R4, R5, R7 and R8 have been preconfigured to belong to AS9. R1, R6, R9, R10 have been
preconfigured to belong to AS 1009.
- R5 acts as the route reflector for iBGP IPv6 unicast within the AS9. iBGP IPv6 sessions should
NOT be established between R2, R3, R4, R7 and R8.
- R6 acts as the route reflector for iBGP IPv6 unicast within the AS1009. An iBGP IPv4 session
should not be established between R1, R9 and R10.
- The interface Loopback0 address is used to establish iBGP IPv6 sessions.
- All routers Loopback0 networks are advertised as BGP IPv6 unicast updates.
CCIE SP Lab1 iBGP IPv6 Unicast Diagram

R24 SW1
First octets of the all IPv6 addresses here are 2002:9:9
SW2
lo0 lo0
::9 lo0 ::2
::1
E0/0 Gi0/0/0/2 Gi0/0/0/0
Gi0/0/0/0
:19::9 19::1 12::1
:23::2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 :37::3 E0/2 S2/0
R9 R1 :12::2 R2 :23::3 R3 :37::7 R7 R21
/3
Gi0/0/0/1
:34::3
E0/1
3
E0/1 Gi0/0/0/1
/0/0
:35::
:109::9 lo0 :78::7 lo0
16::1
Gi0
::3 ::7
Gi0/0/0/1
:25::2
GP
iBGP
iB
iBGP
iBGP
AS9
AS1009 P
iBG
lo0
::5
Gi0/0/0/1
lo0 lo0 lo0 lo0

E0/1
:34::4
E0/1 ::10 ::6 E0/1

:16::6 E0/1 E0/2 ::4 ::8
:109::10 :78::8
iBGP :25::5 :35::5
Gi0/0/0/0
S2/0 S2/0 iBGP :48::4 E0/2
:56::6 :56::5 :48::8
R10 E0/0 E0/2
:106::10 :106::6
R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
:45::5 :45::4 R4
iBGP
PROBLEM:
R1 Loopback0 network is not seen in R6, R9 and R10 BGP IPv6 unicast tables. Fix the problem and
ensure that R1 Loopback0 network is present in R6, R9 and R10 BGP IPv6 unicast tables.
SOLUTION:
AS9:
R2: R5: - AS9 BGP IPv6 Route Reflector

address-family ipv6 unicast neighbor 2002:9:9::2 remote-as 9
network 2002:9:9::2/128 neighbor 2002:9:9::2 update-source Loopback0
! neighbor 2002:9:9::3 remote-as 9
neighbor 2002:9:9::5 ! AS9 BGP IPv6 RR neighbor 2002:9:9::3 update-source Loopback0
remote-as 9 neighbor 2002:9:9::4 remote-as 9
update-source Loopback0 neighbor 2002:9:9::4 update-source Loopback0
! neighbor 2002:9:9::7 update-source Loopback0
neighbor 2002:9:9::8 remote-as 9
neighbor 2002:9:9::8 update-source Loopback0
!
address-family ipv6
network 2002:9:9::5/128
24
neighbor 2002:9:9::2 activate
neighbor 2002:9:9::2 route-reflector-client
exit-address-family
R3: R4:

network 2002:9:9::3/128 network 2002:9:9::4/128
! !
neighbor 2002:9:9::5 ! AS9 BGP IPv6 RR !
remote-as 9 2002:9:9::5 ! AS9 BGP IPv6 RR
update-source Loopback0 remote-as 9
address-family ipv6 unicast update-source Loopback0
! address-family ipv6 unicast
!
R7: R8:
router bgp 9
bgp router-id 9.9.0.7 router bgp 9
neighbor 2002:9:9::5 remote-as 9 bgp router-id 9.9.0.8
neighbor 2002:9:9::5 update-source lo0 !neighbor 2002:9:9::5 remote-as 9
! neighbor 2002:9:9::5 update-source Loopback0
address-family ipv6 !
network 2002:9:9::7/128 address-family ipv6
neighbor 2002:9:9::5 activate!AS9 BGP IPv6 RR network 2002:9:9::8/128
exit-address-family neighbor 2002:9:9::5 activate!AS9 BGP IPv6 RR
! exit-address-family
!
AS1009:
R9: R10:

neighbor 2002:9:9::6 remote-as 1009 neighbor 2002:9:9::6 remote-as 1009
neighbor 2002:9:9::6 update-source Loopback0 neighbor 2002:9:9::6 update-source Loopback0
! !
network 2002:9:9::9/128 network 2002:9:9::10/128
neighbor 2002:9:9::6 activate!AS1009 BGP IPv6 RR neighbor 2002:9:9::6 activate!AS1009 BGP IPv6 RR
! !
R1: R6: - AS1009 BGP IPv6 Route Reflector

network 2002:9:9::1/128 neighbor 2002:9:9::1 update-source Loopback0
neighbor 2002:9:9::6 ! AS1009 BGP IPv6 RR neighbor 2002:9:9::9 update-source Loopback0
remote-as 1009 neighbor 2002:9:9::10 remote-as 1009
update-source Loopback0 neighbor 2002:9:9::10 update-source Loopback0
! address-family ipv6
network 2002:9:9::6/128
!
25
VALIDATION:
{----------------------------------------------------AS 9------------------------------------------------------}
R2:

Mon Dec 17 14:48:12.204 MSK

Speaker 34 34 34 34 34 34
2002:9:9::5 0 9 376 331 34 0 0 04:48:27 5 ! AS9 IPv6 RR
Mon Dec 17 14:48:58.789 MSK
*> 2002:9:9::2/128 :: 0 32768 i
*>i2002:9:9::3/128 2002:9:9::3 0 100 0 i
*>i2002:9:9::4/128 2002:9:9::4 0 100 0 i
*>i2002:9:9::5/128 2002:9:9::5 0 100 0 i
*>i2002:9:9::7/128 2002:9:9::7 0 100 0 i
*>i2002:9:9::8/128 2002:9:9::8 0 100 0 i
Processed 6 prefixes, 6 paths
R5: AS9 BGP Ipv6 Route Reflector

R5#sh ip bgp ipv6 unicast sumamery
2002:9:9::2 4 9 341 380 14 0 0 05:37:33 1
2002:9:9::3 4 9 377 424 14 0 0 06:13:12 1
2002:9:9::4 4 9 377 424 14 0 0 06:13:12 1
2002:9:9::7 4 9 415 427 14 0 0 06:13:00 1
2002:9:9::8 4 9 415 427 14 0 0 06:12:57 1
26
R5# sh ip bgp ipv6 unicast

r>i2002:9:9::2/128 2002:9:9::2 0 100 0 i
r>i2002:9:9::3/128 2002:9:9::3 0 100 0 i
r>i2002:9:9::4/128 2002:9:9::4 0 100 0 i
*> 2002:9:9::5/128 :: 0 32768 i
r>i2002:9:9::7/128 2002:9:9::7 0 100 0 i
r>i2002:9:9::8/128 2002:9:9::8 0 100 0 i
R3:

Mon Dec 17 15:42:00.414 MSK

Speaker 18 18 18 18 18 18
2002:9:9::5 0 9 429 381 18 0 0 06:17:54 5 ! AS9 IPv6 RR

Mon Dec 17 15:43:43.850 MSK
*>i2002:9:9::2/128 2002:9:9::2 0 100 0 i
*> 2002:9:9::3/128 :: 0 32768 i
*>i2002:9:9::4/128 2002:9:9::4 0 100 0 i
*>i2002:9:9::5/128 2002:9:9::5 0 100 0 i
*>i2002:9:9::7/128 2002:9:9::7 0 100 0 i
*>i2002:9:9::8/128 2002:9:9::8 0 100 0 i
Processed 5 prefixes, 5 path
R4:
Mon Dec 17 15:45:10.464 MSK

Speaker 18 18 18 18 18 18
2002:9:9::5 0 9 433 384 18 0 0 06:21:04 5 ! AS9 IPv6 RR
27
R7:
R7#show bgp ipv6 unicast summary

2002:9:9::5 4 9 439 426 14 0 0 06:22:55 5! AS9 IPv6 RR
R7# show bgp ipv6 unicast

r>i2002:9:9::2/128 2002:9:9::2 0 100 0 i
r>i2002:9:9::3/128 2002:9:9::3 0 100 0 i
r>i2002:9:9::4/128 2002:9:9::4 0 100 0 i
r>i2002:9:9::5/128 2002:9:9::5 0 100 0 i
*> 2002:9:9::7/128 :: 0 32768 i
r>i2002:9:9::8/128 2002:9:9::8 0 100 0 i
R8:
R8# show bgp ipv6 unicast summary

2002:9:9::5 4 9 440 428 14 0 0 06:25:01 5! AS9 IPv6 RR
R8# show bgp ipv6 unicast

r>i2002:9:9::2/128 2002:9:9::2 0 100 0 i
r>i2002:9:9::3/128 2002:9:9::3 0 100 0 i
r>i2002:9:9::4/128 2002:9:9::4 0 100 0 i
r>i2002:9:9::5/128 2002:9:9::5 0 100 0 i
r>i2002:9:9::7/128 2002:9:9::7 0 100 0 i
*> 2002:9:9::8/128 :: 0 32768 i
28
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:

2002:9:9::6 4 1009 1455 1448 14 0 0 21:51:21 3 !AS1009 IPv6 RR

r>i2002:9:9::1/128 2002:9:9::1 0 100 0 i
r>i2002:9:9::6/128 2002:9:9::6 0 100 0 i
*> 2002:9:9::9/128 :: 0 32768 i
r>i2002:9:9::10/128 2002:9:9::10 0 100 0 i
R10:
R10# sh ip bgp ipv6 unicast summary

2002:9:9::6 4 1009 1584 1574 14 0 0 23:50:35 3 !AS1009 IPv6 RR
R10#show ip bgp ipv6 unicast
r>i2002:9:9::1/128 2002:9:9::1 0 100 0 i
r>i2002:9:9::6/128 2002:9:9::6 0 100 0 i
r>i2002:9:9::9/128 2002:9:9::9 0 100 0 i
*> 2002:9:9::10/128 :: 0 32768 i
29
R1:

Tue Dec 18 09:19:45.373 MSK

Speaker 21 21 21 21 21 21
2002:9:9::6 0 1009 1593 1439 21 0 0 23:55:42 3 ! AS1009 IPv6 RR

Tue Dec 18 09:21:02.548 MSK
*> 2002:9:9::1/128 :: 0 32768 i
*>i2002:9:9::6/128 2002:9:9::6 0 100 0 i
*>i2002:9:9::9/128 2002:9:9::9 0 100 0 i
*>i2002:9:9::10/128 2002:9:9::10 0 100 0 i
R6: AS1009 BGP IPv6 Route Reflector
R6# sh ip bgp ipv6 unicast summary


2002:9:9::1 4 1009 1441 1596 14 0 0 23:58:15 1
2002:9:9::9 4 1009 1591 1598 14 0 0 1d00h 1
2002:9:9::10 4 1009 1587 1597 14 0 0 1d00h 1
R6# sh ip bgp ipv6 unicast
r>i2002:9:9::1/128 2002:9:9::1 0 100 0 i
*> 2002:9:9::6/128 :: 0 32768 i
r>i2002:9:9::9/128 2002:9:9::9 0 100 0 i
r>i2002:9:9::10/128 2002:9:9::10 0 100 0 i
30
1.9 EBGP IPV4 UNICAST TROUBLESHOOTING
- Configure an eBGP IPv4 Unicast session between R1 and R2.

- After you complete these configurations, Loopback0 networks of R2, R3, R4, R5, R7 and R8
should appear in the routing tables of R1, R6, R9, and R10 as BGP IPv4 routes. Loopback0
networks of R1, R6, R9, and R10 should appear in the routing tables of R2, R3, R4, R5, R7 and R8
as BGP IPv4 routes. No other routes should be distributed between AS9 and AS1009.
- Ensure these Loopbacks can ping each other via IPv4.
- Directly connected PPP networks, such as 9.9.12.0/24 and 9.9.56.0/24 are NOT permitted to
be redistributed into IGP routing protocols.
- NB! Commands that were entered on the previous steps but required for better understanding
are highlighted in green
CCIE SP Lab1 eBGP IPv4 Unicast Diagram

R24 SW1 SW2
lo0 lo0 iBGP

.0.9 lo0 AS9 BGP RR .0.2
AS1009 BGP RR .0.1
E0/0 Gi0/0/0/2 Gi0/0/0/0 Gi0/0/0/0
.19.9 19.1 12.1 23.2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 .37.3 E0/2
iBGP iBGP S2/0
R9 R1 12.2 R2 23.3 R3 .37.7 R7 R21
/3
Gi0/0/0/1
.34.3
E0/1
.35.3
E0/1 Gi0/0/0/1 eBGP

/0/0
.109.9 lo0 .78.7 lo0

16.1
Gi0
.0.3 .0.7
Gi0/0/0/1
GP
25.2
iBGP
GP
iB
iB
G
iB
P
iBGP
iBGP
AS9
iB
iBGP
GP
AS1009 P
iBG
lo0
.0.5
Gi0/0/0/1
lo0 lo0 lo0 lo0

.0.10 E0/1 .0.6 E0/1
.34.4
E0/1 E0/2 .0.4 .0.8

.16.6 E0/1
.109.10 eBGP
.25.5 .35.5 .78.8
iBGP
Gi0/0/0/0
S2/0 S2/0 iBGP 48.4 E0/2
.56.6 .56.5 48.8
R10 E0/0 E0/2 R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
.106.10 .106.6 .45.5 45.4 R4
iBGP
SOLUTION:
AS1009 <-> AS9
R1: R2:
! !
description Link to R2 Gi0/0/0/0 description Link to R1 Gig0/0/0/0
cdp cdp
ipv4 address 9.9.12.1 255.255.255.0 ipv4 address 9.9.12.2 255.255.255.0
! !
! !
route-policy default_policy_pass_all in route-policy default_policy_pass_all in
route-policy default_policy_pass_all out route-policy default_policy_pass_all out
! !
next-hop-self next-hop-self
31
! !
! neighbor 9.9.0.4
neighbor 9.9.0.9 remote-as 9
remote-as 1009 address-family ipv4 unicast
address-family ipv4 unicast next-hop-self
next-hop-self !
! neighbor 9.9.0.5
! remote-as 9
neighbor 9.9.0.10 address-family ipv4 unicast
remote-as 1009 next-hop-self
next-hop-self neighbor 9.9.0.7
! remote-as 9
next-hop-self
route-policy default_policy_pass_all !
pass neighbor 9.9.0.8
end-policy remote-as 9
next-hop-self
!
route-policy default_policy_pass_all
pass
end-policy
!
R6: R5:
interface Serial2/0
description PPP Link to R5 S2/0
ip address 9.9.56.6 255.255.255.0 interface Serial2/0
encapsulation ppp description PPP link to R6 S2/0
serial restart-delay 0 ip address 9.9.56.5 255.255.255.0
! encapsulation ppp
router bgp 1009 serial restart-delay 0
neighbor 9.9.56.5 remote-as 9 !
neighbor 9.9.0.1 remote-as 1009 router bgp 9
address-family ipv4 neighbor 9.9.0.4 remote-as 9
neighbor 9.9.56.5 activate neighbor 9.9.0.7 remote-as 9
neighbor 9.9.0.1 next-hop-self neighbor 9.9.0.8 remote-as 9
neighbor 9.9.0.9 next-hop-self !
neighbor 9.9.0.10 next-hop-self address-family ipv4
neighbor 9.9.56.6 activate
! neighbor 9.9.0.1 next-hop-self
neighbor 9.9.0.3 next-hop-self
!
VALIDATION:
{----------------------------------------------------AS 9------------------------------------------------------}
R2:
RP/0/0/CPU0:R2#sh bgp ipv4 unicast | i 1009

Tue Dec 18 14:14:23.580 MSK
*>i9.9.0.1/32 9.9.0.5 0 200 0 1009 i
* 9.9.12.1 0 0 1009 i
*>i9.9.0.6/32 9.9.0.5 0 200 0 1009 i
* 9.9.12.1 0 1009 i
*>i9.9.0.9/32 9.9.0.5 0 200 0 1009 i
* 9.9.12.1 0 1009 i
*>i9.9.0.10/32 9.9.0.5 0 200 0 1009 i
* 9.9.12.1 0 1009 i
R5:
R5#sh ip bgp ipv4 unicast | i 1009

*> 9.9.0.1/32 9.9.56.6 0 1009 i
* i 9.9.0.2 0 100 0 1009 i
* i9.9.0.6/32 9.9.0.2 100 0 1009 i
*> 9.9.56.6 0 0 1009 i
*> 9.9.0.9/32 9.9.56.6 0 1009 i
* i 9.9.0.2 100 0 1009 i
32
*> 9.9.0.10/32 9.9.56.6 0 1009 i
* i 9.9.0.2 100 0 1009 i
R3:

Tue Dec 18 16:03:03.359 MSK
*>i9.9.0.1/32 9.9.0.2 0 100 0 1009 i
* i 9.9.0.5 0 100 0 1009 i
*>i9.9.0.6/32 9.9.0.2 100 0 1009 i
* i 9.9.0.5 0 100 0 1009 i
*>i9.9.0.9/32 9.9.0.2 100 0 1009 i
* i 9.9.0.5 0 100 0 1009 i
*>i9.9.0.10/32 9.9.0.2 100 0 1009 i
* i 9.9.0.5 0 100 0 1009 i
R4:

Tue Dec 18 16:04:43.025 MSK
* i9.9.0.1/32 9.9.0.2 0 100 0 1009 i
*>i 9.9.0.5 0 100 0 1009 i
* i9.9.0.6/32 9.9.0.2 100 0 1009 i
*>i 9.9.0.5 0 100 0 1009 i
* i9.9.0.9/32 9.9.0.2 100 0 1009 i
*>i 9.9.0.5 0 100 0 1009 i
* i9.9.0.10/32 9.9.0.2 100 0 1009 i
*>i 9.9.0.5 0 100 0 1009 i
R7:

* i9.9.0.1/32 9.9.0.5 0 100 0 1009 i
*>i 9.9.0.2 0 100 0 1009 i
* i9.9.0.6/32 9.9.0.5 0 100 0 1009 i
*>i 9.9.0.2 100 0 1009 i
* i9.9.0.9/32 9.9.0.5 0 100 0 1009 i
*>i 9.9.0.2 100 0 1009 i
* i9.9.0.10/32 9.9.0.5 0 100 0 1009 i
*>i 9.9.0.2 100 0 1009 i
R8:
*>i9.9.0.1/32 9.9.0.5 0 100 0 1009 i

* i 9.9.0.2 0 100 0 1009 i
*>i9.9.0.6/32 9.9.0.5 0 100 0 1009 i
* i 9.9.0.2 100 0 1009 i
*>i9.9.0.9/32 9.9.0.5 0 100 0 1009 i
* i 9.9.0.2 100 0 1009 i
*>i9.9.0.10/32 9.9.0.5 0 100 0 1009 i
* i 9.9.0.2 100 0 1009 i
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:
R9#sh ip bgp ipv4 unicast | i 0 9
* i9.9.0.2/32 9.9.0.6 0 100 0 9 i

*>i 9.9.0.1 0 100 0 9 i
* i9.9.0.3/32 9.9.0.6 0 100 0 9 i
*>i 9.9.0.1 100 0 9 i
* i9.9.0.4/32 9.9.0.6 0 100 0 9 i
*>i 9.9.0.1 100 0 9 i
* i9.9.0.5/32 9.9.0.6 0 100 0 9 i
*>i 9.9.0.1 100 0 9 i
* i9.9.0.7/32 9.9.0.6 0 100 0 9 i
*>i 9.9.0.1 100 0 9 i
* i9.9.0.8/32 9.9.0.6 0 100 0 9 i
*>i 9.9.0.1 100 0 9 i
33
R10:
*>i9.9.0.2/32 9.9.0.6 0 100 0 9 i

* i 9.9.0.1 0 100 0 9 i
*>i9.9.0.3/32 9.9.0.6 0 100 0 9 i
* i 9.9.0.1 100 0 9 i
*>i9.9.0.4/32 9.9.0.6 0 100 0 9 i
* i 9.9.0.1 100 0 9 i
* i9.9.0.5/32 9.9.0.1 100 0 9 i
*>i 9.9.0.6 0 100 0 9 i
*>i9.9.0.7/32 9.9.0.6 0 100 0 9 i
* i 9.9.0.1 100 0 9 i
*>i9.9.0.8/32 9.9.0.6 0 100 0 9 i
* i 9.9.0.1 100 0 9 i
R1:
RP/0/0/CPU0:R1#sh bgp ipv4 unicast | i 0 9

Tue Dec 18 21:23:36.025 MSK
* i9.9.0.2/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 0 9 i
* i9.9.0.3/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 9 i
* i9.9.0.4/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 9 i
* i9.9.0.5/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 9 i
* i9.9.0.7/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 9 i
* i9.9.0.8/32 9.9.0.6 0 100 0 9 i
*> 9.9.12.2 0 9 i
R6:
*> 9.9.0.2/32 9.9.56.5 0 9 i
* i 9.9.0.1 0 100 0 9 i
*> 9.9.0.3/32 9.9.56.5 0 9 i
* i 9.9.0.1 100 0 9 i
*> 9.9.0.4/32 9.9.56.5 0 9 i
* i 9.9.0.1 100 0 9 i
*> 9.9.0.5/32 9.9.56.5 0 0 9 i
* i 9.9.0.1 100 0 9 i
*> 9.9.0.7/32 9.9.56.5 0 9 i
* i 9.9.0.1 100 0 9 i
*> 9.9.0.8/32 9.9.56.5 0 9 i
* i 9.9.0.1 100 0 9 i
1.10 EBGP IPV6 UNICAST TROUBLESHOOTING

- After you complete these configurations, Loopback0 networks of R2, R3, R4, R5, R7 and R8
should appear in the routing tables of R1, R6, R9, and R10 as BGP IPv6 routes. Loopback0
networks of R1, R6, R9, and R10 should appear in the routing tables of R2, R3, R4, R5, R7 and R8
as BGP IPv6 routes. No other routes should be distributed between AS9 and AS1009.
- Ensure these Loopbacks can ping each other via IPv6.
- Directly connected PPP networks, such as 2002:9:9:12::/64 and 2002:9:9:56::/24 are NOT
permitted to be redistributed into IGP routing protocols.
- NB! Commands that were entered on the previous steps but required for better understanding
are highlighted in green
34
CCIE SP Lab1 eBGP IPv6 Unicast Diagram
R24 SW1
SW2
lo0 lo0
::9 lo0 ::2
::1
E0/0 Gi0/0/0/2 Gi0/0/0/0 Gi0/0/0/0
:19::9 19::1 12::1 :23::2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 :37::3 E0/2 S2/0
R9 R1 :12::2 R2 :23::3 R3 :37::7 R7 R21
/3
Gi0/0/0/1
:34::3
E0/1
3
E0/1 Gi0/0/0/1
/0/0
:35::
:109::9 16::1 lo0 :78::7 lo0
Gi0
::3 ::7
Gi0/0/0/1
:25::2
GP
iBGP
iB
iBGP
iBGP
AS9
AS1009 P
iBG
lo0
lo0
::5
Gi0/0/0/1
lo0 ::6 lo0 lo0
E0/1
:34::4
E0/1 ::10 E0/1
:16::6 E0/1 E0/2 ::4 ::8
:109::10 eBGP :78::8
iBGP :25::5 :35::5
Gi0/0/0/0
S2/0 S2/0 iBGP :48::4 E0/2
:56::6 :56::5 :48::8
R10 E0/0 E0/2
:106::10 :106::6
R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
:45::5 :45::4 R4
iBGP
SOLUTION:
AS1009 <-> AS9
R6: R5:
interface Serial2/0 interface Serial2/0

description PPP Link to R5 S2/0 description PPP link to R6 S2/0
encapsulation ppp encapsulation ppp
! !
neighbor 2002:9:9:56::5 remote-as 9 neighbor 2002:9:9:56::6 remote-as 1009
address-family ipv6 neighbor 2002:9:9::8 remote-as 9
neighbor 2002:9:9:56::5 activate !
neighbor 2002:9:9::1 next-hop-self address-family ipv6
neighbor 2002:9:9::9 next-hop-self neighbor 2002:9:9:56::6 activate
neighbor 2002:9:9::10 next-hop-self neighbor 2002:9:9::2 next-hop-self
! neighbor 2002:9:9::3 next-hop-self
neighbor 2002:9:9::4 next-hop-self
!
VALIDATION:
{----------------------------------------------------AS 9------------------------------------------------------}
R2:
Tue Dec 18 22:37:03.233 MSK
*>i2002:9:9::1/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::6/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::9/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::10/128 2002:9:9::5 0 100 0 1009 i
35
R5:
R5#show ip bgp ipv6 unicast | i 1009
*> 2002:9:9::1/128 2002:9:9:56::6 0 1009 i

*> 2002:9:9::6/128 2002:9:9:56::6 0 0 1009 i
*> 2002:9:9::9/128 2002:9:9:56::6 0 1009 i
*> 2002:9:9::10/128 2002:9:9:56::6 0 1009 i
R3:
Tue Dec 18 22:40:06.121 MSK
*>i2002:9:9::1/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::6/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::9/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::10/128 2002:9:9::5 0 100 0 1009 i
R4:
Tue Dec 18 22:41:01.748 MSK

*>i2002:9:9::1/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::6/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::9/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::10/128 2002:9:9::5 0 100 0 1009 i
R7:
R7# show ip bgp ipv6 unicast | i 1009
*>i2002:9:9::1/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::6/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::9/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::10/128 2002:9:9::5 0 100 0 1009 i
R8:
R8# show ip bgp ipv6 unicast | i 1009

*>i2002:9:9::1/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::6/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::9/128 2002:9:9::5 0 100 0 1009 i
*>i2002:9:9::10/128 2002:9:9::5 0 100 0 1009 i
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:
R9#show ip bgp ipv6 unicast | i 0 9
*>i2002:9:9::2/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::3/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::4/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::5/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::7/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::8/128 2002:9:9::6 0 100 0 9 i
R10:
*>i2002:9:9::2/128 2002:9:9::6 0 100 0 9 i

*>i2002:9:9::3/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::4/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::5/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::7/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::8/128 2002:9:9::6 0 100 0 9 i
36
R1:
RP/0/0/CPU0:R1#sh bgp ipv6 unicast | i 0 9

Tue Dec 18 22:47:17.577 MSK
*>i2002:9:9::2/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::3/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::4/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::5/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::7/128 2002:9:9::6 0 100 0 9 i
*>i2002:9:9::8/128 2002:9:9::6 0 100 0 9 i
R6:
*> 2002:9:9::2/128 2002:9:9:56::5 0 9 i

*> 2002:9:9::3/128 2002:9:9:56::5 0 9 i
*> 2002:9:9::4/128 2002:9:9:56::5 0 9 i
*> 2002:9:9::5/128 2002:9:9:56::5 0 0 9 i
*> 2002:9:9::7/128 2002:9:9:56::5 0 9 i
*> 2002:9:9::8/128 2002:9:9:56::5 0 9 i
1.11 BGP IPV4 UNICAST PATH SELECTION
- Configure R5 to ensure that IPv4 traffic from AS9 destined to AS 1009 chooses R5 as primary exit
point and R2 as a backup exit point.
- Configure R6 to ensure that IPv4 traffic from AS9 destined to AS 1009 chooses R5 as primary exit
point and R2 as a backup exit point.
SOLUTION:
R5: R6:
ip as-path access-list 1 permit ^1009$ ip as-path access-list 1 permit ^9$
! !
route-map RM_FROM_R6 permit 10 route-map RM_FROM_R5 permit 10
match as-path 1 match as-path 1
set local-preference 200 set local-preference 200
route-map RM_FROM_R6 permit 20 route-map RM_FROM_R5 permit 20
! !
! !
neighbor 9.9.56.6 route-map RM_FROM_R6 in neighbor 9.9.56.5 route-map RM_FROM_R5 in
VALIDATION:
NB! It makes sense to verify the paths to remote AS on the routers located as far as possible from the
AS9 and AS1009 ASBRs. In our topology they are R9 and R7.
{----------------------------------------------------AS 9------------------------------------------------------}
R7:
*>i9.9.0.1/32 9.9.0.5 0 200 0 1009 i

* i 9.9.0.5 0 200 0 1009 i
*>i9.9.0.6/32 9.9.0.5 0 200 0 1009 i
* i 9.9.0.5 0 200 0 1009 i
*>i9.9.0.9/32 9.9.0.5 0 200 0 1009 i
* i 9.9.0.5 0 200 0 1009 i
*>i9.9.0.10/32 9.9.0.5 0 200 0 1009 i
* i 9.9.0.5 0 200 0 1009 i
37
R7#sh ip bgp ipv4 unicast 9.9.0.9
BGP routing table entry for 9.9.0.9/32, version 37

Paths: (2 available, best #1, table default)
Not advertised to any peer
Refresh Epoch 1
1009
9.9.0.5 (metric 30) from 9.9.0.5 (9.9.0.5)
Origin IGP, metric 0, localpref 200, valid, internal, best
Refresh Epoch 1
1009
9.9.0.5 (metric 30) from 9.9.0.2 (9.9.0.2)
Origin IGP, metric 0, localpref 200, valid, internal
Originator: 9.9.0.5, Cluster list: 9.9.0.2
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:
R9# sh ip bgp ipv4 unicast | i 0 9

*>i9.9.0.2/32 9.9.0.6 0 200 0 9 i
* i 9.9.0.6 0 200 0 9 i
*>i9.9.0.3/32 9.9.0.6 0 200 0 9 i
* i 9.9.0.6 0 200 0 9 i
*>i9.9.0.4/32 9.9.0.6 0 200 0 9 i
* i 9.9.0.6 0 200 0 9 i
* i9.9.0.5/32 9.9.0.6 0 200 0 9 i
*>i 9.9.0.6 0 200 0 9 i
*>i9.9.0.7/32 9.9.0.6 0 200 0 9 i
* i 9.9.0.6 0 200 0 9 i
*>i9.9.0.8/32 9.9.0.6 0 200 0 9 i
* i 9.9.0.6 0 200 0 9 i
R9#sh ip bgp ipv4 unicast 9.9.0.7

BGP routing table entry for 9.9.0.7/32, version 41
Paths: (2 available, best #1, table default)
Not advertised to any peer
Refresh Epoch 1
9
9.9.0.6 (metric 30) from 9.9.0.6 (9.9.0.6)
Origin IGP, metric 0, localpref 200, valid, internal, best
Refresh Epoch 1
9
9.9.0.6 (metric 30) from 9.9.0.1 (9.9.0.1)
Origin IGP, metric 0, localpref 200, valid, internal
Originator: 9.9.0.6, Cluster list: 9.9.0.1
1.12 MPLS LDP TROUBLESHOOTING
- R2, R3, R4, R5, R7 and R8 have been enabled MPLS LDP in AS9 on the interfaces that are shown
in the Table 5.
Table 5: MPLS LDP interfaces in AS9

Router Interface
R2 GigabitEthernet0/0/0/0
GigabitEthernet0/0/0/1
R5 Ethernet0/0
Ethernet0/1
38
Ethernet0/2
R7 Ethernet0/1
Ethernet0/2
R8 Ethernet0/1
Ethernet0/2
- R1, R6, R9, and R10 have been enabled MPLS LDP in AS1009 on the interfaces that are shown in
the Table 6.
Table 6: MPLS LDP interfaces in AS1009

Router Interface
R6 Ethernet0/1
Ethernet0/2
R9 Ethernet0/0
Ethernet0/1
R10 Ethernet0/0
Ethernet0/1
- Any interfaces that are NOT listed in the tables 5 and 6 should NOT be MPLS enabled
PROBLEM:
There are NO successful LDP sessions between R7 and R8, R4 and R8. Fix the problem and make LDP
works properly.
SOLUTION:
NB!
- There is no explicit requirement to define the unique label range for each router, but it seriously
helps in MPLS LDP troubleshooting.
- Commands that were entered on the previous steps but required for better understanding are
highlighted in green
AS9:
R2: R5:
mpls label range table 0 26000 26999 mpls label range 5000 5999
! mpls label protocol ldp
mpls ldp mpls ldp router-id Loopback0 force
router-id 9.9.0.2 !
! description Link to R4 Gig 0/0/0/2
interface GigabitEthernet0/0/0/1 mpls ip
! !
mpls ip
!
mpls ip!
39
R3: R4:
mpls label range table 0 36000 36999 mpls label range table 0 46000 46999
mpls ldp mpls ldp
! !
! !
! !
!
!
R7: R8:
mpls label range 7000 7999 mpls label range 8000 8999
mpls label protocol ldp mpls label protocol ldp
mpls ldp router-id Loopback0 force mpls ldp router-id Loopback0 force
! !
mpls ip mpls ip
! !
mpls ip mpls ip
!
AS1009:
R9: R10:
mpls label range 9000 9999 mpls label range 10000 10999
mpls label protocol ldp mpls label protocol ldp
mpls ldp router-id Loopback0 force mpls ldp router-id Loopback0 force
! !
mpls ip mpls ip
! !
mpls ip mpls ip
! !
R1: R5:
mpls label range table 0 16000 16999 mpls label range 5000 5999
! mpls label protocol ldp
mpls ldp mpls ldp router-id Loopback0 force
router-id 9.9.0.1 !
! description Link to R4 Gig 0/0/0/2
interface GigabitEthernet0/0/0/2 mpls ip
! !
mpls ip
!
mpls ip
!
40
VALIDATION:
{----------------------------------------------------AS 9------------------------------------------------------}
R2:
RP/0/0/CPU0:R2#sh mpls ldp nei | i 9.9.
Wed Dec 19 01:07:51.784 MSK

Peer LDP Identifier: 9.9.0.5:0
TCP connection: 9.9.0.5:17207 - 9.9.0.2:646
9.9.0.5 9.9.25.5 9.9.35.5 9.9.45.5
9.9.56.5
TCP connection: 9.9.0.3:46739 - 9.9.0.2:646
9.9.0.3 9.9.23.3 9.9.34.3 9.9.35.3
9.9.37.3
R5:
R5#sh mpls ldp nei | i 9.9.
Peer LDP Ident: 9.9.0.3:0; Local LDP Ident 9.9.0.5:0

TCP connection: 9.9.0.3.646 - 9.9.0.5.40929
Ethernet0/2, Src IP addr: 9.9.35.3
9.9.0.3 9.9.35.3 9.9.23.3 9.9.34.3
9.9.37.3
TCP connection: 9.9.0.2.646 - 9.9.0.5.17207
9.9.0.2 9.9.0.22 9.9.12.2 9.9.25.2
9.9.23.2
TCP connection: 9.9.0.4.646 - 9.9.0.5.63763
9.9.0.4 9.9.45.4 9.9.34.4 9.9.48.4
R3:
RP/0/0/CPU0:R3#sh mpls ldp neighbor | i 9.9.
Wed Dec 19 01:10:18.797 MSK

TCP connection: 9.9.0.5:40929 - 9.9.0.3:646
9.9.0.5 9.9.25.5 9.9.35.5 9.9.45.5
9.9.56.5
TCP connection: 9.9.0.7:29555 - 9.9.0.3:646
9.9.0.7 9.9.37.7 9.9.78.7
TCP connection: 9.9.0.4:31260 - 9.9.0.3:646
9.9.0.4 9.9.34.4 9.9.45.4 9.9.48.4
TCP connection: 9.9.0.2:646 - 9.9.0.3:46739
9.9.0.2 9.9.0.22 9.9.12.2 9.9.23.2
9.9.25.2
R4:
Wed Dec 19 01:11:56.631 MSK

TCP connection: 9.9.0.3:646 - 9.9.0.4:31260
9.9.0.3 9.9.23.3 9.9.34.3 9.9.35.3
9.9.37.3
TCP connection: 9.9.0.8:15668 - 9.9.0.4:646
9.9.0.8 9.9.0.88 9.9.48.8 9.9.78.8
TCP connection: 9.9.0.5:63763 - 9.9.0.4:646
9.9.0.5 9.9.25.5 9.9.35.5 9.9.45.5
9.9.56.5
41
R7:
R7#sh mpls ldp neighbor | i 9.9.

TCP connection: 9.9.0.8.40382 - 9.9.0.7.646
9.9.78.8 9.9.0.8 9.9.0.88 9.9.48.8
TCP connection: 9.9.0.3.646 - 9.9.0.7.29555
9.9.0.3 9.9.35.3 9.9.23.3 9.9.34.3
9.9.37.3
R8:

TCP connection: 9.9.0.7.646 - 9.9.0.8.40382
9.9.78.7 9.9.0.7 9.9.37.7
TCP connection: 9.9.0.4.646 - 9.9.0.8.15668
9.9.0.4 9.9.45.4 9.9.34.4 9.9.48.4
{----------------------------------------------------AS 1009------------------------------------------------------}
R9:

TCP connection: 9.9.0.10.23848 - 9.9.0.9.646
9.9.0.10 9.9.106.10 9.9.109.10 9.9.120.10
TCP connection: 9.9.0.1.646 - 9.9.0.9.35542
9.9.0.1 9.9.19.1 9.9.16.1 9.9.12.1
R10:

TCP connection: 9.9.0.9.646 - 9.9.0.10.23848
9.9.19.9 9.9.0.9 9.9.109.9
TCP connection: 9.9.0.6.646 - 9.9.0.10.62877
9.9.0.6 9.9.16.6 9.9.106.6 9.9.56.6
R1:
Wed Dec 19 01:03:13.778 MSK

TCP connection: 9.9.0.9:35542 - 9.9.0.1:646
9.9.0.9 9.9.19.9 9.9.109.9
TCP connection: 9.9.0.6:52788 - 9.9.0.1:646
9.9.0.6 9.9.16.6 9.9.56.6 9.9.106.6
42
R6:

TCP connection: 9.9.0.10.62877 - 9.9.0.6.646
9.9.0.10 9.9.106.10 9.9.109.10 9.9.120.10
TCP connection: 9.9.0.1.646 - 9.9.0.6.52788
9.9.0.1 9.9.19.1 9.9.16.1 9.9.12.1
1.13 MPLS TRAFFIC ENGINEERING -1
- Configure R2, R3, R4, R5, R7 and R8 to support MPLS traffic engineering.
- Set up MPLS TE Tunnel 82 on R8 to reach R2 via R4, R5, R3 and R2
- Set up MPLS TE Tunnel 28 on R2 to reach R8 via R3, R5, R4 and R8
- Ensure that traffic from R8 to the R2 Loopback2 interface chooses tunnel 82
- Ensure that traffic from R2 to the R8 Loopback2 interface chooses tunnel 28
- You are permitted to define static route on R8 and R2 to accomplish this task
- Configure R2, R3, R4, R5, R7 and R8 to support a maximum 25Mbit/s bandwidth reservation on
each subinterface.
- Set up MPLS TE Tunnel 82 with a bandwidth of 5 Mbit/s. Set up MPLS TE Tunnel 28 with a
bandwidth of 5 Mbit/s.
SOLUTION:
MPLS TE infrastructure
R2: R5:
router isis 1
address-family ipv4 unicast mpls traffic-eng tunnels
metric-style wide !
mpls traffic-eng level-1 router isis
mpls traffic-eng router-id Loopback0 metric-style wide
! mpls traffic-eng router-id Loopback0
mpls traffic-eng mpls traffic-eng level-1
! mpls traffic-eng tunnels
! ip rsvp bandwidth 25000
rsvp !
bandwidth 25000 description Link to R2 Gi0/0/0/1
! mpls traffic-eng tunnels
interface GigabitEthernet0/0/0/1 ip rsvp bandwidth 25000
bandwidth 25000 !
mpls traffic-eng tunnels
ip rsvp bandwidth 25000
!
R3: R4:
router isis 1
address-family ipv4 unicast router isis 1
metric-style wide address-family ipv4 unicast
mpls traffic-eng level-1 metric-style wide
mpls traffic-eng level-1
43
mpls traffic-eng router-id Loopback0 mpls traffic-eng router-id Loopback0
! !
mpls traffic-eng mpls traffic-eng
! !
! !
! !
! rsvp
! bandwidth 25000
rsvp !
bandwidth 25000 bandwidth 25000
! !
bandwidth 25000 bandwidth 25000
! !
bandwidth 25000
!
bandwidth 25000
!
!
R7: R8:
mpls traffic-eng tunnels mpls traffic-eng tunnels
! !
mpls traffic-eng router-id Loopback0 mpls traffic-eng router-id Loopback0
mpls traffic-eng level-1 mpls traffic-eng level-1
! !
ip rsvp bandwidth 25000 ip rsvp bandwidth 25000
! !
ip rsvp bandwidth 25000 ip rsvp bandwidth 25000
! !
MPLS TE Tunnels 82 and 28
R8: R2:
! !
interface Tunnel82 interface tunnel-te28
description TE Tunnel from R8 to R2 bandwidth 5000
ip unnumbered Loopback0 ipv4 unnumbered Loopback0
tunnel mode mpls traffic-eng priority 7 7
tunnel destination 9.9.0.2 destination 9.9.0.8
tunnel mpls traffic-eng priority 7 7 path-option 10 explicit name TE-28
tunnel mpls traffic-eng bandwidth 5000 !
tunnel mpls traffic-eng path-option 10 explicit-path name TE-28
explicit name TE-82 index 10 next-address strict ipv4 unicast 9.9.0.3
! index 20 next-address strict ipv4 unicast 9.9.0.5
ip explicit-path name TE-82 enable index 30 next-address strict ipv4 unicast 9.9.0.4
next-address 9.9.0.4 index 40 next-address strict ipv4 unicast 9.9.0.8
next-address 9.9.0.5 !
next-address 9.9.0.3 router static
next-address 9.9.0.2 address-family ipv4 unicast
! 9.9.0.88/32 tunnel-te28
ip route 9.9.0.22 255.255.255.255 tunnel82 !
!
!
44
VALIDATION:
{------------------------------------Tunnels 82/28 ----------------------------------------}
R8:
R8#sh int tun82
Tunnel82 is up, line protocol is up
Hardware is Tunnel
Description: TE Tunnel from R8 to R2
Interface is unnumbered. Using address of Loopback0 (9.9.0.8)
MTU 17936 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 255/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 9.9.0.8, destination 9.9.0.2
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:03, output hang never
Last clearing of "show interface" counters 05:03:44
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 30000 bits/sec, 35 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
10012 packets output, 1040384 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
R8#sh mpls traffic-eng tunnels tunnel 82

Name: TE Tunnel from R8 to R2 (Tunnel82) Destination: 9.9.0.2
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 10, type explicit TE-82 (Basis for Setup, path weight 40)
Config Parameters:
Bandwidth: 5000 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled Loadshare: 5000 [400000] bw-based
auto-bw: disabled
Active Path Option Parameters:
State: explicit path option 10 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
InLabel : -
OutLabel : Ethernet0/2, 46011
Next Hop : 9.9.48.4
RSVP Signalling Info:
Src 9.9.0.8, Dst 9.9.0.2, Tun_Id 82, Tun_Instance 28
RSVP Path Info:
My Address: 9.9.48.8
Explicit Route: 9.9.48.4 9.9.45.4 9.9.45.5 9.9.35.5
9.9.35.3 9.9.23.3 9.9.23.2 9.9.0.2
Record Route: NONE
Tspec: ave rate=5000 kbits, burst=1000 bytes, peak rate=5000 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=5000 kbits, burst=1000 bytes, peak rate=5000 kbits
Shortest Unconstrained Path Info:
Path Weight: 30 (TE)
Explicit Route: 9.9.48.8 9.9.48.4 9.9.34.4 9.9.34.3
9.9.23.3 9.9.23.2 9.9.0.2
History:
Tunnel:
Time since created: 5 hours, 7 minutes
Time since path change: 5 hours, 2 minutes
Number of LSP IDs (Tun_Instances) used: 28
Current LSP: [ID: 28]
Uptime: 5 hours, 2 minutes
45
R8#traceroute 9.9.0.22
Type escape sequence to abort.
Tracing the route to 9.9.0.22
VRF info: (vrf in name/id, vrf out name/id)
1 9.9.48.4 6 msec 5 msec 6 msec
2 9.9.45.5 [MPLS: Label 5008 Exp 0] 5 msec 5 msec 5 msec
3 9.9.35.3 6 msec 7 msec 6 msec
4 9.9.23.2 4 msec * 5 msec
R2:
RP/0/0/CPU0:R2#sh int tunnel-te 28
Mon Dec 24 13:38:13.834 MSK
tunnel-te28 is up, line protocol is up
Interface state transitions: 1
Hardware is Tunnel-TE
Internet address is 9.9.0.2/32
MTU 1500 bytes, BW 5000 Kbit (Max: 5000 Kbit)
reliability 254/255, txload Unknown, rxload Unknown
Encapsulation TUNNEL, loopback not set,
Last input never, output 00:00:00
Last clearing of "show interface" counters never
0 packets input, 0 bytes, 0 total input drops
0 drops for unrecognized upper-level protocol
Received 0 broadcast packets, 0 multicast packets
4046 packets output, 420264 bytes, 0 total output drops
Output 0 broadcast packets, 0 multicast packets
RP/0/0/CPU0:R2#sh mpls traffic-eng tunnels 28

Mon Dec 24 13:39:49.096 MSK
Name: tunnel-te28 Destination: 9.9.0.8

Status:
path option 10, type explicit TE-28 (Basis for Setup, path weight 40)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 0 kbps CT0
Creation Time: Mon Dec 24 08:29:57 2012 (05:09:52 ago)
Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Hop-limit: disabled
AutoRoute: disabled LockDown: disabled Policy class: not set
Forwarding-Adjacency: disabled
Loadshare: 0 equal loadshares
Auto-bw: disabled
Fast Reroute: Disabled, Protection Desired: None
Path Protection: Not Enabled
Soft Preemption: Disabled
History:
Tunnel has been up for: 05:09:23 (since Mon Dec 24 08:30:26 MSK 2012)
Current LSP:
Uptime: 05:09:23 (since Mon Dec 24 08:30:26 MSK 2012)
Reopt. LSP:
Last Failure:
LSP not signalled, identical to the [CURRENT] LSP
Date/Time: Mon Dec 24 09:29:56 MSK 2012 [04:09:53 ago]
Path info (IS-IS 1 level-1):
Hop0: 9.9.23.3
Hop1: 9.9.35.3
Hop2: 9.9.35.5
Hop3: 9.9.45.5
Hop4: 9.9.45.4
Hop5: 9.9.48.4
Hop6: 9.9.48.8
Hop7: 9.9.0.8
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 1) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
46
RP/0/0/CPU0:R2#traceroute 9.9.0.88
Mon Dec 24 13:50:08.498 MSK

Tracing the route to 9.9.0.88
1 9.9.23.3 4 msec 3 msec 3 msec
2 9.9.35.5 2 msec 6 msec 3 msec
3 9.9.45.4 3 msec 3 msec 2 msec
4 9.9.48.8 4 msec * 3 msec
1.14 MPLS TRAFFIC ENGINEERING -2
- Set up MPLS TE Tunnel 85 on R8 to reach R5 via dynamic path

- Set up MPLS TE Tunnel 45 on R4 to reach R5 via R3 and R5
- Ensure that Tunnel 85 will switch over to Tunnel 45 when Link between R4 and R5 (VLAN 13 in
the real lab) goes down
SOLUTION:
MPLS TE Tunnels 85 and 45
R8: R4:
! !
interface Tunnel85 interface tunnel-te45
ip unnumbered Loopback0 ipv4 unnumbered Loopback0
tunnel mode mpls traffic-eng destination 9.9.0.5
tunnel destination 9.9.0.5 path-option 10 explicit name B-TE-45
tunnel mpls traffic-eng path-option 10 dynamic !
tunnel mpls traffic-eng fast-reroute explicit-path name B-TE-45
! index 10 next-address strict ipv4 unicast 9.9.0.3
index 20 next-address strict ipv4 unicast 9.9.0.5
!
mpls traffic-eng
backup-path tunnel-te 45
!
!
VALIDATION:
Normal condition: Link between R4 (interface Gi0/0/0/2) and R5 (Ethernet 0/0) is UP

R8:
R8#sh int tunnel 85
Tunnel85 is up, line protocol is up
Hardware is Tunnel
Interface is unnumbered. Using address of Loopback0 (9.9.0.8)
MTU 17936 bytes, BW 100 Kbit/sec, DLY 50000 usec,
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 9.9.0.8, destination 9.9.0.5
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output never, output hang never
Last clearing of "show interface" counters 05:32:21
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
47
Name: R8_t85 (Tunnel85) Destination: 9.9.0.5
Status:
path option 10, type dynamic (Basis for Setup, path weight 20)
Config Parameters:
auto-bw: disabled
State: dynamic path option 10 is active
InLabel : -
Next Hop : 9.9.48.4
RSVP Path Info:
Explicit Route: 9.9.48.4 9.9.45.4 9.9.45.5 9.9.0.5
Record Route: NONE
RSVP Resv Info:
Record Route: 9.9.0.4(46010) 9.9.48.4(46010)
9.9.0.5(3)
Explicit Route: 9.9.48.8 9.9.48.4 9.9.45.4 9.9.45.5
9.9.0.5
History:
Tunnel:
Time since path change: 5 hours, 28 minutes
Uptime: 5 hours, 28 minutes
R4:
RP/0/0/CPU0:R4#sh int gigabitEthernet 0/0/0/2
Mon Dec 24 14:16:00.424 MSK
GigabitEthernet0/0/0/2 is up, line protocol is up
Hardware is GigabitEthernet, address is 02b7.b31a.3224 (bia 02b7.b31a.3224)
Description: Link to R5 E0/0
Encapsulation ARPA,
Full-duplex, 1000Mb/s, unknown, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input 00:00:00, output 00:00:00
224382464 runts, 223319040 giants, 0 throttles, 0 parity
1829089280 output errors, 1641926656 underruns, 0 applique, 0 resets
1 carrier transitions
RP/0/0/CPU0:R4#sh int tunnel-te 45

Mon Dec 24 14:04:41.344 MSK
tunnel-te45 is up, line protocol is up
Hardware is Tunnel-TE
MTU 1500 bytes, BW 0 Kbit
reliability 255/255, txload Unknown, rxload Unknown
Encapsulation TUNNEL, loopback not set,
Last input never, output never
48
RP/0/0/CPU0:R4#sh mpls traffic-eng tunnels 45
Mon Dec 24 14:04:57.456 MSK
Name: tunnel-te45 Destination: 9.9.0.5

Status:
path option 10, type explicit B-TE-45 (Basis for Setup, path weight 20)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 0 kbps CT0
Creation Time: Mon Dec 24 08:29:58 2012 (05:34:59 ago)
Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0xffff
Hop-limit: disabled
AutoRoute: disabled LockDown: disabled Policy class: not set
Forwarding-Adjacency: disabled
Loadshare: 0 equal loadshares
Auto-bw: disabled
Fast Reroute: Disabled, Protection Desired: None
Path Protection: Not Enabled
Soft Preemption: Disabled
History:
Tunnel has been up for: 05:34:30 (since Mon Dec 24 08:30:27 MSK 2012)
Current LSP:
Uptime: 05:34:30 (since Mon Dec 24 08:30:27 MSK 2012)
Reopt. LSP:
Last Failure:
LSP not signalled, identical to the [CURRENT] LSP
Date/Time: Mon Dec 24 09:29:57 MSK 2012 [04:35:00 ago]
Path info (IS-IS 1 level-1):
Hop0: 9.9.34.3
Hop1: 9.9.35.3
Hop2: 9.9.35.5
Hop3: 9.9.0.5
Displayed 1 (of 1) heads, 0 (of 3) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
Protection condition: Link between R4 (interface Gi0/0/0/2) and R5 (Ethernet 0/0) is DOWN
R4:
RP/0/0/CPU0:R4#sh int gigabitEthernet 0/0/0/2
Mon Dec 24 14:17:28.278 MSK

GigabitEthernet0/0/0/2 is administratively down, line protocol is administratively down
Hardware is GigabitEthernet, address is 02b7.b31a.3224 (bia 02b7.b31a.3224)
Description: Link to R5 E0/0
Encapsulation ARPA,
Full-duplex, 1000Mb/s, unknown, link type is force-up
output flow control is off, input flow control is off
Carrier delay (up) is 10 msec
loopback not set,
ARP type ARPA, ARP timeout 04:00:00
Last input 00:00:00, output 00:00:03
225246720 runts, 224179200 giants, 0 throttles, 0 parity
1836134400 output errors, 1648250880 underruns, 0 applique, 0 resets
2 carrier transitions
49
R8:
Name: R8_t85 (Tunnel85) Destination: 9.9.0.5
Status:
path option 10, type dynamic (Basis for Setup, path weight 30)
Config Parameters:
auto-bw: disabled
State: dynamic path option 10 is active
InLabel : -
Next Hop : 9.9.78.7
RSVP Path Info:
Explicit Route: 9.9.78.7 9.9.37.7 9.9.37.3 9.9.35.3
9.9.35.5 9.9.0.5
Record Route: NONE
RSVP Resv Info:
Record Route: 9.9.0.7(7020) 9.9.0.3(36023)
9.9.37.3(36023) 9.9.0.5(3)
Explicit Route: 9.9.48.8 9.9.48.4 9.9.34.4 9.9.34.3
9.9.35.3 9.9.35.5 9.9.0.5
History:
Tunnel:
Time since path change: 5 minutes, 40 seconds
Uptime: 5 minutes, 43 seconds
Selection: reoptimization
Prior LSP: [ID: 28]
ID: path option 10 [28]
Removal Trigger: re-route path error
Last Error: RSVP:: Path Error from 9.9.48.4: Notify: Tunnel locally repaired (flags 0)
50
1.15 IPV4 PIM-SM TROUBLESHOOTING
IPv4 multicast and PIM sparse mode have been configured in the service provider network AS9 and
AS 1009 as follows:
- The interfaces that are shown in the Tables 7 and 8 have been configured to PIM sparse mode
Table 7: IPv4 multicast interfaces in the AS9
Router Interface
R2 Loopback0
R3 Loopback0
R4 Loopback0
R5 Loopback0
Ethernet0/0
Ethernet0/1
Ethernet0/2
Serial 2/0
R7 Loopback0
Ethernet0/1
Ethernet0/2
R8 Loopback0
Ethernet0/1
Ethernet0/2
Table 8: IPv4 multicast interfaces in the AS1009
Router Interface
R9 Loopback0
Ethernet0/0
Ethernet0/1
R10 Loopback0
Ethernet0/0
Ethernet0/1
R1 Loopback0
R6 Loopback0
Ethernet0/1
Ethernet0/2
Serial 2/0
51
- Interfaces are not listed in the table should not have PIM-SM enabled
PROBLEM:
- There is no PIM-SM neighboring adjacency between R3 and R4. Fix the problem and ensure that
R3 is the DR in the AS9 and R1 is the DR in the AS1009???
SOLUTION:
AS9:
R2: R5:
multicast-routing ip multicast-routing
enable ip pim sparse-mode
! !
enable description Link to R4 Gig 0/0/0/2
enable interface Ethernet0/1
! !
router pim interface Ethernet0/2
address-family ipv4 description Link to R3 Gi0/0/0/3
interface Loopback0 ip pim sparse-mode
enable !
! interface Serial2/0
interface GigabitEthernet0/0/0/0 description PPP link to R6 S2/0
! !
enable
!
!
!
R3: R4:
multicast-routing multicast-routing
enable enable
! !
enable enable
! !
enable enable
! !
enable enable
! !
enable !
! router pim
router pim enable
rpf-vector interface GigabitEthernet0/0/0/0
interface Loopback0 enable
enable !
interface GigabitEthernet0/0/0/0 enable
enable !
dr-priority 4294967295 interface GigabitEthernet0/0/0/2
! enable
enable !
dr-priority 4294967295 !
!
52
enable
dr-priority 4294967295
!
enable
!
!
R7: R8:
ip multicast-routing ip multicast-routing
! !
ip pim sparse-mode ip pim sparse-mode
! !
! !
! !
AS1009:
R9: R10:
! !
! !
! !
! !
R1: R6:
multicast-routing ip multicast-routing
! !
enable description Link to R1 Gi0/0/0/1
enable interface Ethernet0/2
! description Link to R10 E0/0 via SW3 E1/1
! !
router pim interface Serial2/0
address-family ipv4 description PPP Link to R5 S2/0
interface Loopback0 ip pim sparse-mode
enable !
!
enable
!
enable
!
!
53
VALIDATION:
{--------------------------------------------- AS9----------------------------------------------------}
R2:
RP/0/0/CPU0:R2#sh pim ipv4 neighbor

Sat Dec 29 00:54:18.367 MSK
PIM neighbors in VRF default

Neighbor Address Interface Uptime Expires DR pri Flags
9.9.23.2* GigabitEthernet0/0/0/0 1d11h 00:01:28 1 B P
9.9.23.3 GigabitEthernet0/0/0/0 1d11h 00:01:24 1 (DR) B
9.9.25.5 GigabitEthernet0/0/0/1 1d11h 00:01:37 1 (DR) P
9.9.0.2* Loopback0 1d11h 00:01:42 1 (DR) B P
R5:
R5#sh ip pim neighbor
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
9.9.45.4 Ethernet0/0 1d11h/00:01:20 v2 1 / G
9.9.25.2 Ethernet0/1 1d11h/00:01:37 v2 1 / G
9.9.35.3 Ethernet0/2 1d11h/00:01:27 v2 1 / G
9.9.56.6 Serial2/0 1d11h/00:01:28 v2 1 / S P G
R3:

Sat Dec 29 17:47:14.620 MSK

9.9.34.3* GigabitEthernet0/0/0/1 2d04h 00:01:30 4294967294 (DR) B P
9.9.34.4 GigabitEthernet0/0/0/1 2d04h 00:01:32 1 B
9.9.0.3* Loopback0 2d04h 00:01:39 1 (DR) B P
9.9.23.2 GigabitEthernet0/0/0/2 2d04h 00:01:24 1 B
R4:
Sat Dec 29 17:49:06.591 MSK


9.9.34.3 GigabitEthernet0/0/0/1 2d04h 00:01:38 4294967294 (DR) B
9.9.0.4* Loopback0 2d04h 00:01:24 1 (DR) B P
54
R7:
PIM Neighbor Table
Address Prio/Mode
9.9.78.8 Ethernet0/1 2d04h/00:01:15 v2 1 / DR S P G
9.9.37.3 Ethernet0/2 2d04h/00:01:42 v2 1 / G
R8:
PIM Neighbor Table
Address Prio/Mode
9.9.78.7 Ethernet0/1 2d04h/00:01:19 v2 1 / S P G
9.9.48.4 Ethernet0/2 2d04h/00:01:38 v2 1 / G
{--------------------------------------------- AS1009----------------------------------------------------}
R9:
PIM Neighbor Table
Address Prio/Mode
9.9.19.1 Ethernet0/0 2d04h/00:01:24 v2 1 / G
R10:
PIM Neighbor Table
Address Prio/Mode
9.9.106.6 Ethernet0/0 2d04h/00:01:20 v2 1 / S P G
9.9.109.9 Ethernet0/1 2d04h/00:01:21 v2 1 / S P G
R1:
Sat Dec 29 17:59:35.507 MSK

9.9.0.1* Loopback0 1d19h 00:01:25 1 (DR) B P
9.9.16.6 GigabitEthernet0/0/0/1 2d04h 00:01:29 1 P
R5:

PIM Neighbor Table
Address Prio/Mode
9.9.45.4 Ethernet0/0 2d04h/00:01:27 v2 1 / G
9.9.25.2 Ethernet0/1 2d04h/00:01:44 v2 1 / G
9.9.35.3 Ethernet0/2 2d04h/00:01:33 v2 1 / G
9.9.56.6 Serial2/0 2d04h/00:01:44 v2 1 / S P G
55
1.16 IPV4 PIM-SM RP
Configure PIM-SM RP in the SP network AS-9 and AS-1009 as follows:
 R2, R3, R4, R5, R7 and R8 are in the same multicast domain and use the R5 Loopback0 IPv4
address as the rendezvous point (RP).
 Use the BSR method to distribute the RP within AS-9.
 R1, R6, R9 and R10 are in the same multicast domain and use the R6 Loopback0 IPv4 address as
the rendezvous point (RP).
 Use the BSR method to distribute RP within AS-1009.
 RP information should not leak between the two domains AS-9 and AS-1009.
 Multicast Group addresses have configured as shown in Table 9.
 Ensure that routers within AS-9 can ping the group address within AS-9
 Ensure that routers within AS-1009 can ping the group address within AS-1009
Table 9: IPv4 multicast groups in the AS9 and AS1009
Router Interface IPv4 Multicast Group

R1 Loopback0 239.255.0.1
R2 Loopback0 239.255.0.2
R3 Loopback0 239.255.0.3
R4 Loopback0 239.255.0.4
R5 Loopback0 239.255.0.5
R6 Loopback0 239.255.0.6
R7 Loopback0 239.255.0.7
R8 Loopback0 239.255.0.8
R9 Loopback0 239.255.0.9
R10 Loopback0 239.255.0.10
SOLUTION:
AS9:
R2: R5:
!
router igmp ip pim igmp join-group 239.255.0.5
join-group 239.255.0.2 interface Serial2/0
! description PPP link to R6 S2/0
! ip pim bsr-border
!
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0
!
R3: R4:
! !
router igmp router igmp
join-group 239.255.0.3 join-group 239.255.0.4
! !
R7: R8:
ip pim igmp join-group 239.255.0.7 ip pim igmp join-group 239.255.0.8
! !
56
AS1009:
R9: R10:
! !
ip pim igmp join-group 239.255.0.9 ip pim igmp join-group 239.255.0.10
! !
R1: R6:
!
router igmp ip pim igmp join-group 239.255.0.6
join-group 239.255.0.1 interface Serial2/0
! description PPP Link to R5 S2/0
! ip pim bsr-border
!
ip pim bsr-candidate Loopback0 0
ip pim rp-candidate Loopback0
!
VALIDATION:
{--------------------------------------------- AS9----------------------------------------------------}
R7:
R7#sh ip pim bsr-router
PIMv2 Bootstrap information
BSR address: 9.9.0.5 (?)
Uptime: 3d08h, BSR Priority: 0, Hash mask length: 0
Expires: 00:01:53
R7#sh ip pim rp mapping

PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 9.9.0.5 (?), v2
Info source: 9.9.0.5 (?), via bootstrap, priority 0, holdtime 150
Uptime: 3d08h, expires: 00:02:02
R7#ping 239.255.0.2 r 1
Sending 1, 100-byte ICMP Echos to 239.255.0.2, timeout is 2 seconds:
Reply to request 0 from 9.9.0.2, 10 ms

R7#ping 239.255.0.3 r 1
R7#ping 239.255.0.4 r 1
R7#ping 239.255.0.5 r 1
57
R7#ping 239.255.0.7 r 1

R7#ping 239.255.0.8 r 1
R8:
Expires: 00:01:25
Group(s) 224.0.0.0/4
RP 9.9.0.5 (?), v2
R8#ping 239.255.0.2 r 1
R8#ping 239.255.0.3 r 1
R8#ping 239.255.0.4 r 1

R8#ping 239.255.0.5 r 1

R8#ping 239.255.0.7 r 1
R8#ping 239.255.0.8 r 1
58
R3:
RP/0/0/CPU0:R3#sh pim bsr election

Tue Jan 29 01:43:36.718 MSK
PIM BSR Election State
Cand/Elect-State Uptime BS-Timer BSR C-BSR
No-Info/Accept-Pref 07:31:26 00:01:56 9.9.0.5 [0, 0] 0.0.0.0 [0, 0]
RP/0/0/CPU0:R3#sh pim group-map

Tue Jan 29 01:43:41.847 MSK
IP PIM Group Mapping Table

(* indicates group mappings being used)
(+ indicates BSR group mappings active in MRIB)
Group Range Proto Client Groups RP address Info
224.0.1.39/32* DM perm 0 0.0.0.0

224.0.1.40/32* DM perm 1 0.0.0.0
224.0.0.0/24* NO perm 0 0.0.0.0
232.0.0.0/8* SSM config 0 0.0.0.0
224.0.0.0/4* SM bsr+ 3 9.9.0.5 RPF: Gi0/0/0/3,9.9.35.5
224.0.0.0/4 SM static 0 0.0.0.0 RPF: Null,0.0.0.0
RP/0/0/CPU0:R3#ping 239.255.0.2 c 1
Tue Jan 29 00:55:11.290 MSK

RP/0/0/CPU0:R3#ping 239.255.0.3 c 1
Tue Jan 29 00:55:18.290 MSK
RP/0/0/CPU0:R3#ping 239.255.0.4 c 1
Tue Jan 29 00:55:24.378 MSK
RP/0/0/CPU0:R3#ping 239.255.0.5 c 1
Tue Jan 29 00:55:30.065 MSK
RP/0/0/CPU0:R3#ping 239.255.0.7 c 1
Tue Jan 29 00:57:06.255 MSK
RP/0/0/CPU0:R3#ping 239.255.0.8 c 1
Tue Jan 29 00:57:11.135 MSK
R4:
Tue Jan 29 01:45:22.396 MSK

Tue Jan 29 01:45:29.852 MSK
59
224.0.1.39/32* DM perm 0 0.0.0.0
224.0.1.40/32* DM perm 1 0.0.0.0
224.0.0.0/24* NO perm 0 0.0.0.0
232.0.0.0/8* SSM config 0 0.0.0.0
224.0.0.0/4* SM bsr+ 3 9.9.0.5 RPF: Gi0/0/0/2,9.9.45.5
RP/0/0/CPU0:R4#ping 239.255.0.2 c 1
Tue Jan 29 00:59:27.779 MSK
RP/0/0/CPU0:R4#ping 239.255.0.3 c 1
Tue Jan 29 00:59:35.915 MSK

RP/0/0/CPU0:R4#ping 239.255.0.4 c 1
Tue Jan 29 00:59:41.907 MSK
RP/0/0/CPU0:R4#ping 239.255.0.5 c 1
Tue Jan 29 00:59:47.539 MSK
RP/0/0/CPU0:R4#ping 239.255.0.7 c 1
Tue Jan 29 00:59:57.362 MSK
RP/0/0/CPU0:R4#ping 239.255.0.8 c 1
Tue Jan 29 01:00:03.730 MSK
R2:
Tue Jan 29 01:46:37.893 MSK
Tue Jan 29 01:46:49.653 MSK
224.0.1.39/32* DM perm 0 0.0.0.0
224.0.1.40/32* DM perm 1 0.0.0.0
224.0.0.0/24* NO perm 0 0.0.0.0
232.0.0.0/8* SSM config 0 0.0.0.0
224.0.0.0/4* SM bsr+ 1 9.9.0.5 RPF: Gi0/0/0/1,9.9.25.5
RP/0/0/CPU0:R2#ping 239.255.0.2 c 1
Tue Jan 29 01:01:58.683 MSK
RP/0/0/CPU0:R2#ping 239.255.0.3 c 1
Tue Jan 29 01:02:04.863 MSK
60
RP/0/0/CPU0:R2#ping 239.255.0.4 c 1
Tue Jan 29 01:02:11.135 MSK
RP/0/0/CPU0:R2#ping 239.255.0.5 c 1
Tue Jan 29 01:02:16.791 MSK
RP/0/0/CPU0:R2#ping 239.255.0.7 c 1
Tue Jan 29 01:02:22.783 MSK
RP/0/0/CPU0:R2#ping 239.255.0.8 c 1
Tue Jan 29 01:02:28.718 MSK
R5:
This system is the Bootstrap Router (BSR)
Next bootstrap message in 00:00:35
Candidate RP: 9.9.0.5(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:08
This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)
Group(s) 224.0.0.0/4
RP 9.9.0.5 (?), v2
R5#ping 239.255.0.2 r 1
R5#ping 239.255.0.3 r 1
R5#ping 239.255.0.4 r 1
R5#ping 239.255.0.5 r 1
61
R5#ping 239.255.0.7 r 1
R5#ping 239.255.0.8 r 1
{--------------------------------------------- AS1009----------------------------------------------------}
R9:
Expires: 00:01:40
Group(s) 224.0.0.0/4
RP 9.9.0.6 (?), v2
R9#ping 239.255.0.1 r 1
R9#ping 239.255.0.6 r 1

R9#ping 239.255.0.9 r 1
R9#ping 239.255.0.10 r 1
R10:
Expires: 00:01:17
Group(s) 224.0.0.0/4
RP 9.9.0.6 (?), v2
62
R10#ping 239.255.0.1 r 1

R10#ping 239.255.0.6 r 1
R10#ping 239.255.0.9 r 1
R10#ping 239.255.0.10 r 1

R1:
Tue Jan 29 01:30:04.096 MSK

Tue Jan 29 01:33:06.772 MSK

224.0.1.39/32* DM perm 0 0.0.0.0
224.0.1.40/32* DM perm 1 0.0.0.0
224.0.0.0/24* NO perm 0 0.0.0.0
232.0.0.0/8* SSM config 0 0.0.0.0
224.0.0.0/4* SM bsr+ 2 9.9.0.6 RPF: Gi0/0/0/1,9.9.16.6
RP/0/0/CPU0:R1#ping 239.255.0.1
Tue Jan 29 01:16:01.998 MSK
RP/0/0/CPU0:R1#ping 239.255.0.6
Tue Jan 29 01:16:07.384 MSK
RP/0/0/CPU0:R1#ping 239.255.0.9
Tue Jan 29 01:16:17.911 MSK
RP/0/0/CPU0:R1#ping 239.255.0.10
Tue Jan 29 01:16:28.735 MSK
63
R6:
This system is the Bootstrap Router (BSR)
Next bootstrap message in 00:00:04
Candidate RP: 9.9.0.6(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:40
R6#sh ip pim rp map

This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)
Group(s) 224.0.0.0/4
RP 9.9.0.6 (?), v2
R6#ping 239.255.0.1 r 1
R6#ping 239.255.0.6 r 1

R6#ping 239.255.0.9 r 1

R6#ping 239.255.0.10 r 1
1.17 IPV4 MSDP
Configure MSDP between AS9 and AS1009 as follows:
- Configure MSDP on R5 and R6. Use R5 and R6 Loopback0 interfaces to establish MSDP peering
- The RPs (R5 and R6) should inform each other when multicast sources become active in their
autonomous systems.
- Ensure that the routers in AS9 can ping multicast group address in AS 1009 using sources of
Loopback 0.
- Ensure that the routers in AS1009 can ping multicast group address in AS 9 using sources of
Loopback 0.
SOLUTION:
R5
ip msdp peer 9.9.0.6 connect-source Loopback0 remote-as 1009

!
R6:
ip msdp peer 9.9.0.5 connect-source Loopback0 remote-as 9
!
64
VALIDATION:
R5:
R5#sh ip msdp summary
MSDP Peer Status Summary
Peer Address AS State Uptime/ Reset SA Peer Name
Downtime Count Count
9.9.0.6 1009 Up 2d05h 0 0 ?
R6:
R6#sh ip msdp sum
MSDP Peer Status Summary
Peer Address AS State Uptime/ Reset SA Peer Name
Downtime Count Count
9.9.0.5 9 Up 2d05h 0 2 ?
R7: Outermost AS9 routers from R10 in AS 1009
R7#ping 239.255.0.10 source 9.9.0.7

Packet sent with a source address of 9.9.0.7
R10: Outermost AS1009 routers from R7 in AS 9
R10#ping 239.255.0.7 source lo0

Packet sent with a source address of 9.9.0.10
1.18 MPLS LDP AUTHENTICATION
- Configure R6 and R10 so, that MPLS LDP session between them is authenticated using MD5
algorithm.
- Use the password of “cisco “.
SOLUTION:
R6:
mpls ldp neighbor 9.9.0.10 password cisco
!
ip access-list standard ACL_LDP_R10
permit 9.9.0.10
!
mpls ldp password required for ACL_LDP_R10
R10:
mpls ldp neighbor 9.9.0.6 password cisco
!
ip access-list standard ACL_LDP_R6
permit 9.9.0.6
!
mpls ldp password required for ACL_LDP_R6
65
VALIDATION:
R6:
R6#sh mpls ldp nei 9.9.0.10 detail

TCP connection: 9.9.0.10.24003 - 9.9.0.6.646; MD5 on
Password: required, neighbor, in use
State: Oper; Msgs sent/rcvd: 87/84; Downstream; Last TIB rev sent 26
Up time: 01:04:02; UID: 3; Peer Id 0
LDP discovery sources:
Ethernet0/2; Src IP addr: 9.9.106.10
holdtime: 15000 ms, hello interval: 5000 ms
Addresses bound to peer LDP Ident:
9.9.0.10 9.9.106.10 9.9.109.10 9.9.120.10
Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estab
{-------------------------output ommitted---------------------------}
R10:
R10#sh mpls ldp neighbor 9.9.0.6 det

TCP connection: 9.9.0.6.646 - 9.9.0.10.24003; MD5 on
Password: required, neighbor, in use
State: Oper; Msgs sent/rcvd: 86/88; Downstream; Last TIB rev sent 24
Up time: 01:05:05; UID: 5; Peer Id 1
LDP discovery sources:
Ethernet0/0; Src IP addr: 9.9.106.6
holdtime: 15000 ms, hello interval: 5000 ms
Addresses bound to peer LDP Ident:
9.9.0.6 9.9.16.6 9.9.106.6 9.9.56.6
Peer holdtime: 180000 ms; KA interval: 60000 ms; Peer state: estab
{-------------------------output ommitted---------------------------}
66
Section 2. Implement, Optimize and Troubleshooting Access/Edge
connection technologies
2.1 MULTILINK PPP
- Configure PPP Multilink between R10 and R20 on the interfaces Serial 2/0 and Serial 2/1, Refer
to CCIE SP Lab 1 IPv4 Diagram for details.
- Configure IS-IS between R10 and R20 on interfaces shown in the table 9
- Ensure that R20 has full IPv4 connectivity with the routers in the AS1009

R10 47.0110. Multilink1 9.9.120.10
R20 47.0120. Loopback0 9.9.0.20
R20 47.0120. Multilink1 9.9.120.20
SOLUTION:
R10: R20:
interface Serial2/0
interface Serial2/0 no ip address
no ip address encapsulation ppp
encapsulation ppp ppp multilink
ppp multilink ppp multilink group 1
ppp multilink group 1 serial restart-delay 0
serial restart-delay 0 !
interface Serial2/1 no ip address
no ip address encapsulation ppp
encapsulation ppp ppp multilink
ppp multilink group 1 serial restart-delay 0
serial restart-delay 0 !
! interface Multilink1
interface Multilink1 ip address 9.9.120.20 255.255.255.0
ip address 9.9.120.10 255.255.255.0 ip router isis
ip router isis no peer neighbor-route
no peer neighbor-route ppp multilink
ppp multilink group 1 isis circuit-type level-2-only
isis circuit-type level-2-only !
end interface Loopback0
! ip address 9.9.0.20 255.255.255.255
router isis ip router isis
net 47.0110.0000.0000.1010.00 isis circuit-type level-2-only
is-type level-2-only !
metric-style wide router isis
log-adjacency-changes all net 47.0120.0000.0000.0120.00
! is-type level-2-only
metric-style wide
log-adjacency-changes all
VALIDATION:
R20#sh ip route
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
67
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
9.0.0.0/8 is variably subnetted, 11 subnets, 2 masks

i L2 9.9.0.1/32 [115/40] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.0.6/32 [115/30] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.0.9/32 [115/30] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.0.10/32 [115/20] via 9.9.120.10, 00:00:51, Multilink1
C 9.9.0.20/32 is directly connected, Loopback0
i L2 9.9.16.0/24 [115/30] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.19.0/24 [115/30] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.106.0/24 [115/20] via 9.9.120.10, 00:00:51, Multilink1
i L2 9.9.109.0/24 [115/20] via 9.9.120.10, 00:00:51, Multilink1
C 9.9.120.0/24 is directly connected, Multilink1
L 9.9.120.20/32 is directly connected, Multilink1
R20#ping 9.9.0.1 r 1

!
Success rate is 100 percent (1/1), round-trip min/avg/max = 16/16/16 ms
R20#ping 9.9.0.6 r 1
!
R20#ping 9.9.0.9 r 1
!
R20#ping 9.9.0.10 r 1
!
68
Section 3. Implement, Optimize and Troubleshooting L3 VPN Technologies
Virtual and forwarding instances (VRFs) on R1, R2, R3, R4, R7, R8, R9, R10, R11, R12, R14, R15, R17 and
R18 have been configured as follows:
- VRF ABC Sites 1 (R4, R8) and 2 (R3, R7) uses the VRf name “ABC” (case sensitive) with route
distinguisher (RD) 9:9 and import and export route targets (RT) 9:9 for IPv4 and IPv6 address
families.
- VRF ABC Site 3 (R9, R10) uses the VRF name “ABC” (case sensitive) with route distinguisher (RD)
1009:9 and import and export route targets (RT) 1009:9 for IPv4 and IPv6 address families.
- VRF XYZ Site 1 (R11, R12) and 2 (R14, R15) uses the VRf name “XYZ” (case sensitive) with route
distinguisher (RD) 112:112 and import and export route targets (RT) 112:112 for IPv4 and IPv6
address families.
- VRF XYZ Site 3 (R17, R18) uses the VRf name “XYZ” (case sensitive) with route distinguisher (RD)
178:178 and import and export route targets (RT) 178:178 for IPv4 and IPv6 address families.
3.1 IBGP VPNV4 TROUBLESHOOTING
R2, R3, R4, R5, R7, R8 have been configured for iBGP VPNv4 within the AS9. R1, R6, R9, R10 have
been configured for iBGP VPNv4 within AS1009:
- R2 acts as a route reflector for iBGP VPNv4 unicast within AS9. An iBGP VPNv4 session should
not be established between R3, R4, R5, R7 and R8.
- R1 acts as a route reflector for iBGP VPNv4 unicast within AS1009. An iBGP VPNv4 session
should not be established between R6, R9 and R10.
- The interface Loopback0 address is used to establish iBGP VPNv4 sessions.
- The interface Loopback1 network should be announced via BGP in the VRF ABC IPv4 unicast
address family.
PROBLEM:
R7 does not have iBGP VPNv4 unicast updates from R2. Fix the problem and ensure that R7 has
iBGP VPNv4 unicast updates of other routers in AS9.
Note! R5 and R6 have no VRF ABC configured
69
CCIE SP Lab1 iBGP VPNv4 Unicast Diagram
R24 SW1 SW2
lo0 lo0 VPNv4 iBGP

.0.9 lo0 .0.2
AS1009 BGP RR .0.1
E0/0 Gi0/0/0/2 Gi0/0/0/0
Gi0/0/0/0
.19.9 19.1 12.1
23.2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 .37.3 E0/2
VPNv4 iBGP S2/0
R9 R1 12.2 R2 VPNv4 iBGP
23.3 R3 .37.7 R7 R21
/3
Gi0/0/0/1
.34.3
E0/1
.35.3
E0/1 Gi0/0/0/1 AS9 BGP RR
/0/0
.109.9 lo0 .78.7 lo0
16.1
Gi0
.0.3 .0.7
P
BG
Gi0/0/0/1
VP
4i
25.2 Nv
Nv
4
iB
VP
G
VPNv4 iBGP
VPNv4 iBGP
AS9
VP
AS1009
Nv
4 iB
GP
lo0
.0.5
Gi0/0/0/1
lo0 lo0 lo0 lo0
.0.10 E0/1 .0.6 E0/1
.34.4
E0/1 E0/2 .0.4 .0.8
.16.6 E0/1
.109.10
.25.5 .35.5 .78.8
Gi0/0/0/0
S2/0 S2/0 48.4 E0/2
.56.6 .56.5 48.8
R10 E0/0 E0/2 R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
.106.10 .106.6 .45.5 45.4 R4
SOLUTION:
AS9:
R2: AS9 VPNv4 Route Reflector R5:
vrf ABC router bgp 9

import route-target neighbor 9.9.0.2 update-source Loopback0
9:9 !
! address-family vpnv4
export route-target neighbor 9.9.0.2 activate
9:9 neighbor 9.9.0.2 send-community extended
! !
router bgp 9
!
address-family vpnv4 unicast
!
neighbor 9.9.0.3
remote-as 9
!
!
!
neighbor 9.9.0.4
remote-as 9
!
!
!
neighbor 9.9.0.5
remote-as 9
!
!
!
neighbor 9.9.0.7
70
remote-as 9
!
!
!
neighbor 9.9.0.8
remote-as 9
!
!
!
vrf ABC
rd 9:9
network 172.9.0.2/32
!
!
!
R3: R4:
vrf ABC
vrf ABC address-family ipv4 unicast
address-family ipv4 unicast import route-target
import route-target 9:9
9:9 !
! export route-target
export route-target 9:9
9:9 !
! !
! !
! router bgp 9
router bgp 9 !
! address-family vpnv4 unicast
address-family vpnv4 unicast !
! neighbor 9.9.0.2
remote-as 9 update-source Loopback0
update-source Loopback0 !
address-family vpnv4 unicast !
! !
! vrf ABC
vrf ABC rd 9:9
rd 9:9 address-family ipv4 unicast
address-family ipv4 unicast network 172.9.0.4/32
network 172.9.0.3/32 !
! !
! !
!
R7: R8:
vrf definition ABC
vrf definition ABC rd 9:9
rd 9:9 !
address-family ipv4 mdt default 239.255.13.27
mdt default 239.255.13.27 route-target export 9:9
route-target export 9:9 route-target import 9:9
route-target import 9:9 exit-address-family
exit-address-family !
! router bgp 9
router bgp 9 neighbor 9.9.0.2 remote-as 9
neighbor 9.9.0.2 remote-as 9 neighbor 9.9.0.2 update-source Loopback0
neighbor 9.9.0.2 update-source Loopback0 !
address-family vpnv4 neighbor 9.9.0.2 activate
neighbor 9.9.0.2 activate neighbor 9.9.0.2 send-community extended
neighbor 9.9.0.2 send-community extended exit-address-family
exit-address-family !
! address-family ipv4 vrf ABC
address-family ipv4 vrf ABC network 172.9.0.8 mask 255.255.255.255
network 172.9.0.7 mask 255.255.255.255 !
!
71
AS1009:
R9: R10:
vrf definition ABC vrf definition ABC

rd 1009:9 rd 1009:9
! !
route-target export 1009:9 route-target export 1009:9
route-target import 1009:9 route-target import 1009:9
! !
vrf forwarding ABC vrf forwarding ABC
! !
! !
address-family vpnv4 address-family vpnv4
neighbor 9.9.0.1 send-community extended neighbor 9.9.0.1 send-community extended
! !
address-family ipv4 vrf ABC address-family ipv4 vrf ABC
! !
R1: AS1009 VPNv4 Route Reflector R6:
vrf ABC router bgp 1009

1009:9 !
export route-target neighbor 9.9.0.1 activate
1009:9 neighbor 9.9.0.1 send-community extended
! !
interface Loopback1
vrf ABC
ipv4 address 172.9.0.1 255.255.255.255
!
router bgp 1009
!
!
neighbor 9.9.0.6
remote-as 1009
!
!
!
neighbor 9.9.0.9
remote-as 1009
!
!
!
neighbor 9.9.0.10
remote-as 1009
!
!
!
vrf ABC
rd 1009:9
network 172.9.0.1/32
!
!
!
72
VALIDATION:
{---------------------------------------------------------AS9-------------------------------------------------}
R2: AS9 VPNv4 Route Reflector

RP/0/0/CPU0:R2#sh bgp vpnv4 unicast vrf ABC
Sat Jan 12 15:06:49.119 MSK

Table ID: 0x0 RD version: 4
Route Distinguisher: 9:9 (default for vrf ABC)
*> 172.9.0.2/32 0.0.0.0 0 32768 i
*>i172.9.0.3/32 9.9.0.3 0 100 0 i
*>i172.9.0.4/32 9.9.0.4 0 100 0 i
*>i172.9.0.7/32 9.9.0.7 0 100 0 i
*>i172.9.0.8/32 9.9.0.8 0 100 0 i
R3:
Sat Jan 12 15:09:49.850 MSK

*>i172.9.0.2/32 9.9.0.2 0 100 0 i
*> 172.9.0.3/32 0.0.0.0 0 32768 i
*>i172.9.0.4/32 9.9.0.4 0 100 0 i
*>i172.9.0.7/32 9.9.0.7 0 100 0 i
*>i172.9.0.8/32 9.9.0.8 0 100 0 i
R4:
Sun Jan 13 12:11:18.552 MSK

*>i172.9.0.2/32 9.9.0.2 0 100 0 i
*>i172.9.0.3/32 9.9.0.3 0 100 0 i
*> 172.9.0.4/32 0.0.0.0 0 32768 i
*>i172.9.0.7/32 9.9.0.7 0 100 0 i
*>i172.9.0.8/32 9.9.0.8 0 100 0 i
R7:
R7#sh ip bgp vpnv4 vrf ABC
73

*>i172.9.0.2/32 9.9.0.2 0 100 0 i
*>i172.9.0.3/32 9.9.0.3 0 100 0 i
*>i172.9.0.4/32 9.9.0.4 0 100 0 i
*> 172.9.0.7/32 0.0.0.0 0 32768 i
*>i172.9.0.8/32 9.9.0.8 0 100 0 i
R8:
R8# sh ip bgp vpnv4 vrf ABC

*>i172.9.0.2/32 9.9.0.2 0 100 0 i
*>i172.9.0.3/32 9.9.0.3 0 100 0 i
*>i172.9.0.4/32 9.9.0.4 0 100 0 i
*>i172.9.0.7/32 9.9.0.7 0 100 0 i
*> 172.9.0.8/32 0.0.0.0 0 32768 i
{---------------------------------------------------------AS1009-------------------------------------------------}
R9:

*>i172.9.0.1/32 9.9.0.1 0 100 0 i
*> 172.9.0.9/32 0.0.0.0 0 32768 i
*>i172.9.0.10/32 9.9.0.10 0 100 0 i
R10:

r>i172.9.0.1/32 9.9.0.1 0 100 0 i
*>i172.9.0.9/32 9.9.0.9 0 100 0 i
*> 172.9.0.10/32 0.0.0.0 0 32768 i
R1: AS1009 VPNv4 Route Reflector

Sun Jan 13 12:37:14.889 MSK
74
*> 172.9.0.1/32 0.0.0.0 0 32768 i
*>i172.9.0.9/32 9.9.0.9 0 100 0 i
*>i172.9.0.10/32 9.9.0.10 0 100 0 i
3.2 IBGP VPNV6 TROUBLESHOOTING
R2, R3 and R8 have been configured for iBGP VPNv6 within the AS9. R1 and R9 have been configured for
iBGP VPNv6 within AS1009:
- R2 estabslishes a direct iBGP VPNv6 sessions with R3 and R8. R2 acts as a route reflector for
iBGP VPNv6 address family in AS9. An iBGP VPNv6 session should not be established between
R3 and R8.
- R1 establishes a direct iBGP VPNv6 session with R9
- The interface Loopback0 address is used to establish iBGP VPNv6 sessions.
- The interface Loopback1 network should be announced via BGP in the VRF ABC IPv6 unicast
address family.
PROBLEM:
R7 does not have R8 Loopback1 network in BGP VPNv6 unicast table. Fix the problem and
ensure that R3 has BGP VPNv6 unicast updates of R8.
CCIE SP Lab1 iBGP VPNv6 Unicast Diagram

R24 SW1
SW2
lo0 lo0
::9 lo0 AS9 VPNv6 BGP RR ::2
::1
E0/0 Gi0/0/0/2 Gi0/0/0/0
Gi0/0/0/0
:19::9 19::1 12::1
:23::2 Gi0/0/0/0
Gi0/0/0/2 Gi0/0/0/2 :37::3 E0/2 S2/0
R9 VPNv6 iBGP R1 :12::2 R2 :23::3 R3 :37::7 R7 R21
VPNv6 iBGP
/3
Gi0/0/0/1
:34::3
E0/1
3
E0/1 Gi0/0/0/1
/0/0
:35::
:109::9 lo0 :78::7 lo0

16::1
Gi0
::3 ::7
Gi0/0/0/1
:25::2
VP
Nv
AS9
AS1009 6
iB
G
P
lo0
::5
Gi0/0/0/1
lo0 lo0 lo0 lo0

E0/1
:34::4
E0/1 ::10 ::6 E0/1

:16::6 E0/1 E0/2 ::4 ::8
:109::10 :78::8
:25::5 :35::5
Gi0/0/0/0
S2/0 S2/0 :48::4 E0/2
:56::6 :56::5 :48::8
R10 E0/0 E0/2
:106::10 :106::6
R6 ppp R5 E0/0 Gi0/0/0/2 R8 R22
:45::5 :45::4 R4
75
SOLUTION:
AS9:
R2: AS9 VPNv6 Route Reflector R5: No VPNv6 configuration
vrf ABC
import route-target
9:9
!
export route-target
9:9
!
!
!
router bgp 9
!
!
neighbor 9.9.0.3
remote-as 9
!
!
!
neighbor 9.9.0.8
remote-as 9
!
!
!
vrf ABC
rd 9:9
!
network 2002:172:9::2/128
!
!
!
R3: R4: No VPNv6 configuration
vrf ABC
import route-target
9:9
!
export route-target
9:9
!
!
!
router bgp 9
!
!
neighbor 9.9.0.2
remote-as 9
!
!
!
vrf ABC
rd 9:9
!
network 2002:172:9::3/128
!
76
R7: No VPNv6 configuration R8:
vrf definition ABC

rd 9:9
!
address-family ipv6
route-target import 9:9
exit-address-family
!
router bgp 9
neighbor 9.9.0.2 update-source Loopback0
!
address-family vpnv6
neighbor 9.9.0.2 send-community extended
exit-address-family
!
address-family ipv6 vrf ABC
network 2002:172:9::8/128
!
!
AS1009:
vrf definition ABC

rd 1009:9
!
address-family ipv6
route-target export 1009:9
exit-address-family
!
router bgp 1009
!
!
exit-address-family
!
network 2002:172:9::9/128
exit-address-family
!
vrf ABC
import route-target
1009:9
!
export route-target
1009:9
!
!
!
router bgp 1009
!
!
neighbor 9.9.0.9
remote-as 1009
!
!
!
vrf ABC
rd 1009:9
77
!
network 2002:172:9::1/128
!
!
VALIDATION:
{---------------------------------------------------------AS9-------------------------------------------------}
R2:
RP/0/0/CPU0:R2#sh bgp vpnv6 uni vrf ABC
Sun Jan 13 14:01:19.584 MSK

*> 2002:172:9::2/128 :: 0 32768 i
*>i2002:172:9::3/128 9.9.0.3 0 100 0 i
*>i2002:172:9::8/128 9.9.0.8 0 100 0 i
R3:
Sun Jan 13 14:03:13.413 MSK

*>i2002:172:9::2/128 9.9.0.2 0 100 0 i
*> 2002:172:9::3/128 :: 0 32768 i
*>i2002:172:9::8/128 9.9.0.8 0 100 0 i
R8:
R8#sh ip bgp vpnv6 uni vrf ABC

*>i2002:172:9::2/128
::FFFF:9.9.0.2 0 100 0 i
*>i2002:172:9::3/128
::FFFF:9.9.0.3 0 100 0 i
*> 2002:172:9::8/128
:: 0 32768 i
78
{---------------------------------------------------------AS1009-------------------------------------------------}
R1:
Sun Jan 13 14:09:05.257 MSK

*> 2002:172:9::1/128 :: 0 32768 i
*>i2002:172:9::9/128 9.9.0.9 0 100 0 i
R8:
R9#sh ip bgp vpnv6 uni vrf ABC


*>i2002:172:9::1/128
::FFFF:9.9.0.1 0 100 0 i
*> 2002:172:9::9/128
:: 0 32768 i
3.3 INTRA AS VPNV4
The ABC Company at Site 1 uses BGP IPv4 to connect to the service provider’s routers R4 and R8.
R11 and R12 locate in AS112.
- Establish BGP IPv4 unicast session between R4 and R11.

- Configure OSPF on R11 and R12 on the interfaces that are shown in the Table 10.
Table 10: OSPF interface in VRF ABC Site 1
Router Interface Area

R11 Loopback0 0
Ethernet 0/2 0
R12 Loopback0 0
Ethernet 0/2 0
- Interfaces that are not listed in the table are not permitted to enable OSPF.
The ABC Company at Site 2 uses BGP IPv4 to connect to the service provider’s routers R3 and R7.
R14 and R15 locate in AS112.

- Configure OSPF on R7, R14 and R15 on the interfaces that are shown in the Table 11.
79
Table 11: OSPF interface in VRF ABC Site 2

R7 Loopback1 0
Ethernet0/0 0
R14 Loopback0 0
Ethernet0/2 0
R15 Loopback0 0
Ethernet0/1 0
Ethernet0/2 0
- Interfaces that are not listed in the table are not permitted to enable OSPF
Ensure that routers of the ABC at Sites 1 and Site 2 can ping each other via IPv4.
Note! There is no explicit requirement to announce the link networks marked in red via BGP but
they are desired to make the full connectivity in VRF ABC.
CCIE SP Lab1 Intra-AS VPNv4 Diagram
lo0
.0.16
XYZ Site 2
IS-IS L2 Second-level customer network
R16 E0/1
E0/0
.146.16 .156.16
vrf XYZ vrf XYZ vrf XYZ vrf XYZ

E0/0 lo1 lo1 E0/0
.146.14 .0.14 .0.15 .156.15
E0/2 E0/2
.145.14.145.15
R14 R15
IPv4 eBGP
E0/1 lo0 lo0 E0/1

.143.14 .0.14 .0.15 .157.15 VPN customer network
AS112 OSPF Area 0 – first two octets 172.9.
Gi0/0/0/4
vrf ABC vrf ABC ABC Site 2

vrf ABC
.143.3
lo1 lo1
.0.3 .0.7 vrf ABC
E0/0
.157.7
Gi0/0/0/0
.37.3 E0/2
R3 .37.7 R7
Gi0/0/0/1
.34.3
E0/1
lo0 .78.7 lo0
.0.3 .0.7
AS9
IS-IS L1
Gi0/0/0/1
lo0 E0/1 lo0

.34.4
.0.4 .0.8
.78.8
Gi0/0/0/0
48.4 E0/2
48.8
R8
R4 vrf ABC
AS112 E0/0 lo2
vrf ABC
Gi0/0/0/3
114.4
vrf ABC vrf ABC .128.8 .0.88

IPv4 eBGP
IPv4 eBGP
lo1 lo1 (for Tunnel) lo0

.0.4 .0.8 172.9.0.22
OSPF Area 0 VPN customer network
lo0 lo0
E0/1 .0.11 .0.12 E0/1 – first two octets 172.9.
.114.11 .128.12
E0/2
ABC Site 1
E0/2
.112.11 .112.12
R11 R12
vrf XYZ vrf XYZ
vrf XYZ lo0 E0/0 vrf XYZ
E0/0
lo1 .0.13 .123.12 lo1
.113.11
.0.11 .0.12
E0/1
E0/0
.113.13
.123.13 XYZ Site 1
IS-IS L2
R13
Second-level customer network – first two octets 192.9.
80
SOLUTION:
ABC Site 1:
R4: R11:
interface Loopback1 interface Ethernet0/1

vrf ABC description Link to R4 Gi0/0/0/3
ipv4 address 172.9.0.4 255.255.255.255 ip address 172.9.114.11 255.255.255.0
! !
interface GigabitEthernet0/0/0/3 interface Loopback0
description Link to R11 E0/1 ip address 172.9.0.11 255.255.255.255
cdp !
vrf ABC interface Ethernet0/2
ipv4 address 172.9.114.4 255.255.255.0 description Link to R12 E0/2
! ip address 172.9.112.11 255.255.255.0
router bgp 9 !
! router bgp 112
vrf ABC neighbor 172.9.114.4 remote-as 9
! !
neighbor 172.9.114.11 address-family ipv4
remote-as 112 network 172.9.114.0 mask 255.255.255.0
address-family ipv4 unicast redistribute ospf 112
route-policy default_policy_pass_all in neighbor 172.9.114.4 activate
route-policy default_policy_pass_all out exit-address-family
as-override !
! router ospf 112
! router-id 172.9.0.11
! redistribute bgp 112 subnets
! network 172.9.0.11 0.0.0.0 area 0
route-policy default_policy_pass_all network 172.9.112.11 0.0.0.0 area 0
pass !
end-policy
!
R8: R12:
interface Loopback1
vrf forwarding ABC interface Ethernet0/1
ip address 172.9.0.8 255.255.255.255 description Link to R8 E0/0
! ip address 172.9.128.12 255.255.255.0
interface Ethernet0/0 !
description Link to R12 E0/1 interface Loopback0
vrf forwarding ABC ip address 172.9.0.12 255.255.255.255
ip address 172.9.128.8 255.255.255.0 !
router bgp 9 description Link to R11 E0/2
! ip address 172.9.112.12 255.255.255.0
address-family ipv4 vrf ABC !
neighbor 172.9.128.12 remote-as 112 router bgp 112
neighbor 172.9.128.12 activate neighbor 172.9.128.8 remote-as 9
neighbor 172.9.128.12 as-override !
exit-address-family address-family ipv4
! network 172.9.128.0 mask 255.255.255.0
redistribute ospf 112
exit-address-family
!
!
router ospf 112
router-id 172.9.0.12
redistribute bgp 112 subnets
network 172.9.0.12 0.0.0.0 area 0
network 172.9.112.12 0.0.0.0 area 0
!
ABC Site 2:
R3: R14:

vrf ABC ip address 172.9.0.14 255.255.255.255
ipv4 address 172.9.0.3 255.255.255.255 !
81
interface GigabitEthernet0/0/0/4 description Link to R3 Gi0/0/0/1
cdp !
vrf ABC interface Ethernet0/2
ipv4 address 172.9.143.3 255.255.255.0 description Link to R15 E0/2
! ip address 172.9.145.14 255.255.255.0
router bgp 9 !
! router ospf 112
vrf ABC router-id 172.9.0.14
rd 9:9 redistribute bgp 112 subnets
! network 172.9.0.14 0.0.0.0 area 0
neighbor 172.9.143.14 network 172.9.145.14 0.0.0.0 area 0
remote-as 112 !
address-family ipv4 unicast router bgp 112
route-policy default_policy_pass_all in neighbor 172.9.143.3 remote-as 9
route-policy default_policy_pass_all out !
as-override address-family ipv4
! network 172.9.143.0 mask 255.255.255.0
! redistribute ospf 112
exit-address-family
!
R7: R15:

ip address 172.9.0.7 255.255.255.255 !
interface Ethernet0/0 description Link to R7 E0/0
vrf forwarding ABC !
ip address 172.9.157.7 255.255.255.0 interface Ethernet0/2
! description Link to R14 E0/2
router ospf 112 vrf ABC ip address 172.9.145.15 255.255.255.0
router-id 172.9.0.7 !
domain-tag 9 router ospf 112
redistribute bgp 112 subnets router-id 172.9.0.15
network 172.9.0.7 0.0.0.0 area 0 network 172.9.0.15 0.0.0.0 area 0
! network 172.9.157.15 0.0.0.0 area 0
router bgp 9 !
!
redistribute ospf 112 vrf ABC
exit-address-family
!
VALIDATION:
R11:
R11#sh ip route
B 172.9.0.2/32 [20/0] via 172.9.114.4, 01:09:55
B 172.9.0.3/32 [20/0] via 172.9.114.4, 01:09:55
B 172.9.0.4/32 [20/0] via 172.9.114.4, 01:09:55
B 172.9.0.7/32 [20/0] via 172.9.114.4, 01:09:55
B 172.9.0.8/32 [20/0] via 172.9.114.4, 01:09:55
O 172.9.0.12/32 [110/11] via 172.9.112.12, 1d05h, Ethernet0/2
B 172.9.0.14/32 [20/0] via 172.9.114.4, 00:08:53
B 172.9.0.15/32 [20/0] via 172.9.114.4, 00:20:09
C 172.9.112.0/24 is directly connected, Ethernet0/2
L 172.9.112.11/32 is directly connected, Ethernet0/2
B 172.9.128.0/24 [20/0] via 172.9.114.4, 01:09:55
B 172.9.143.0/24 [20/0] via 172.9.114.4, 00:20:09
B 172.9.145.0/24 [20/0] via 172.9.114.4, 00:20:09
B 172.9.157.0/24 [20/0] via 172.9.114.4, 00:20:09
82
R11#ping 172.9.0.11 r 1
!
R11#ping 172.9.0.12 r 1
!
R11#ping 172.9.0.14 r 1
!
R11#ping 172.9.0.15 r 1
!
R12:
R12#sh ip route

B 172.9.0.2/32 [20/0] via 172.9.128.8, 1d03h
B 172.9.0.3/32 [20/0] via 172.9.128.8, 1d03h
B 172.9.0.4/32 [20/0] via 172.9.128.8, 1d03h
B 172.9.0.7/32 [20/0] via 172.9.128.8, 1d03h
B 172.9.0.8/32 [20/0] via 172.9.128.8, 1d03h
O 172.9.0.11/32 [110/11] via 172.9.112.11, 1d05h, Ethernet0/2
B 172.9.0.14/32 [20/0] via 172.9.128.8, 00:10:05
B 172.9.0.15/32 [20/0] via 172.9.128.8, 00:21:21
B 172.9.114.0/24 [20/0] via 172.9.128.8, 00:31:21
B 172.9.143.0/24 [20/0] via 172.9.128.8, 00:21:21
B 172.9.145.0/24 [20/0] via 172.9.128.8, 00:21:21
B 172.9.157.0/24 [20/0] via 172.9.128.8, 00:21:21
R12# ping 172.9.0.11 r 1
!
R12# ping 172.9.0.12 r 1
!
R12# ping 172.9.0.14 r 1
!
R12# ping 172.9.0.15 r 1
!
83
R14:
R14#sh ip route
B 172.9.0.2/32 [20/0] via 172.9.143.3, 00:31:24
B 172.9.0.3/32 [20/0] via 172.9.143.3, 00:31:24
B 172.9.0.4/32 [20/0] via 172.9.143.3, 00:31:24
O 172.9.0.7/32 [110/21] via 172.9.145.15, 01:08:35, Ethernet0/2
B 172.9.0.8/32 [20/0] via 172.9.143.3, 00:31:24
B 172.9.0.11/32 [20/0] via 172.9.143.3, 00:31:24
B 172.9.0.12/32 [20/0] via 172.9.143.3, 00:31:24
O 172.9.0.15/32 [110/11] via 172.9.145.15, 1d05h, Ethernet0/2
B 172.9.112.0/24 [20/0] via 172.9.143.3, 00:31:24
B 172.9.114.0/24 [20/0] via 172.9.143.3, 00:31:24
B 172.9.128.0/24 [20/0] via 172.9.143.3, 00:31:24
O 172.9.157.0/24 [110/20] via 172.9.145.15, 01:08:35, Ethernet0/2
R14# ping 172.9.0.11 r 1
!
R14# ping 172.9.0.12 r 1
!
R14# ping 172.9.0.14 r 1
!
R14# ping 172.9.0.15 r 1

!
R15:
R15#sh ip route

O E2 172.9.0.2/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.0.3/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.0.4/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O 172.9.0.7/32 [110/11] via 172.9.157.7, 01:10:18, Ethernet0/1
O E2 172.9.0.8/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.0.11/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.0.12/32 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O 172.9.0.14/32 [110/11] via 172.9.145.14, 1d05h, Ethernet0/2
84
O E2 172.9.112.0/24 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.114.0/24 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.128.0/24 [110/1] via 172.9.145.14, 00:33:07, Ethernet0/2
O E2 172.9.143.0/24 [110/1] via 172.9.145.14, 1d05h, Ethernet0/2
R15#ping 172.9.0.11 r 1
!
R15#ping 172.9.0.12 r 1
!
R15#ping 172.9.0.14 r 1
!
R15#ping 172.9.0.15 r 1
!
3.4 INTRA AS VPNV6
The ABC Company at Site1 uses BGP IPv6 for connection to the SP router R8. Router R12 is located in AS-
112.
 Establish BGP IPv6 unicast session between R8 and R12.

 Configure OSPFv3 on R11 and R12 on the interfaces that are show in the Table 12.
Table 12: OSPFv3 interface in VRF ABC Site 1

R11 Loopback0 0
E0/2 0
R12 Loopback0 0
E0/2 0
 Interfaces that are not listed in the table are not permitted to enable OSPFv3.
The ABC Company at Site2 uses EIGRP for connects to the SP router R3.
 Configure an EIGRP IPv6 on R3, R14 and R15 on the interfaces that are shown in the Table 13.
Table 13: EIGRP IPv6 interface in VRF ABC Site 2
Router Interface AS
R3 Loopback1 100
GE0/0/0/4 100
R14 Loopback0 100
E0/1 100
E0/2
R15 Loopback0 100
E0/2 100
85
 Interfaces that are not listed in the table are not permitted to enable EIGRP.
 Ensure that routers of ABC sites 1 and 2 can ping each over via IPv6.
CCIE SP Lab1 Intra-AS VPNv6 Diagram
Second-level customer network – first two octets 2002:192:9:

lo0
::16
XYZ Site 2
IS-IS L2
E0/0 R16 E0/1
:146::16 :156::16
vrf XYZ vrf XYZ vrf XYZ vrf XYZ

E0/0 lo1 Lo1 E0/0
:146::14 ::14 ::15 :156::15
E0/2 E0/2
:145::14:145::15
R14 R15
lo0
AS112lo0
E0/1 E0/1 VPN customer network
::14 ::15
:143::14 :157::15 – first eight octets
IPv6 EIGRP 2002:172:9:
Gi0/0/0/4
vrf ABC vrf ABC ABC Site 2

vrf ABC
:143::3
lo1 lo1
::3 ::7 vrf ABC
E0/0
:157::7
Gi0/0/0/0
:37::3 E0/2
R3 :37::7 R7 R21
Gi0/0/0/1
:34::3
E0/1
lo0 :78::7 lo0
::3 ::7
– first eight octets

2002:9:9:
AS9 – first eight octets

2002:9:9:
IS-IS L1
Gi0/0/0/1
lo0 lo0
:34::4
E0/1
.0.4 :78::8 ::8
Gi0/0/0/0
:48::4 E0/2
:48::8
R8
R4 vrf ABC
AS112 E0/0
vrf ABC
Gi0/0/0/3
:114::4
vrf ABC vrf ABC :128::8

lo1 lo1
IPv6 eBGP
::4 ::8
OSPFv3 Area 0 VPN customer network
lo0 lo0
::11 ::12 E0/1
– first eight octets
E0/1
:114::11 :128::12 2002:172:9:
E0/2
E0/2 ABC Site 1
:112::11 :112::12
R11 R12
vrf XYZ vrf XYZ
lo0 E0/0 vrf XYZ
E0/0
::13 :123::12 lo1
:113::11
::12
E0/1
E0/0
:113::13
:123::13 XYZ Site 1
IS-IS L2
R13
Second-level customer network – first eight octets 2002:192:9:
86
SOLUTION:
ABC Site 1:
R8: R12:
vrf forwarding ABC ipv6 address 2002:172:9::12/128
ipv6 address 2002:172:9::8/128 ipv6 ospf 112 area 0
! !
vrf forwarding ABC ipv6 address 2002:172:9:128::12/64
ipv6 address 2002:172:9:128::8/64 !
router bgp 9 description Link to R11 E0/2
! ipv6 address 2002:172:9:112::12/64
address-family ipv6 vrf ABC ipv6 ospf 112 area 0
network 2002:172:9::8/128 !
neighbor 2002:172:9:128::12 remote-as 112 ipv6 router ospf 112
neighbor 2002:172:9:128::12 activate router-id 172.9.0.12
neighbor 2002:172:9:128::12 as-override redistribute connected
exit-address-family redistribute bgp 112
! !
router bgp 112
!
address-family ipv6
redistribute connected
network 2002:172:9::12/128
neighbor 2002:172:9:128::8 activate
!
R11:
interface Loopback0
ipv6 address 2002:172:9::11/128
!
description Link to R12 E0/2
ipv6 address 2002:172:9:112::11/64
!
ipv6 router ospf 112
!
ABC Site 2:
R3: R14:
interface Loopback1
vrf ABC ipv6 router eigrp 112
ipv6 address 2002:172:9::3/128 passive-interface Loopback0
! eigrp router-id 172.9.0.14
description Link to R14 E0/1 interface Loopback0
cdp ipv6 address 2002:172:9::14/128
vrf ABC ipv6 eigrp 112
ipv6 address 2002:172:9:143::3/64 !
router bgp 9 description Link to R3 Gi0/0/0/1
! ipv6 address 2002:172:9:143::14/64
vrf ABC ipv6 eigrp 112
! !
network 2002:172:9::3/128 description Link to R15 E0/2
redistribute eigrp 112 ipv6 address 2002:172:9:145::14/64
! ipv6 eigrp 112
87
router eigrp 112 !
vrf ABC
address-family ipv6
default-metric 100000 100 255 1 1500
autonomous-system 112
redistribute bgp 9
interface Loopback1
passive-interface
!
!
!
!
!
R15:
interface Loopback0
ipv6 address 2002:172:9::15/128
* ipv6 eigrp 112
!
ipv6 address 2002:172:9:145::15/64
ipv6 eigrp 112
!
ipv6 router eigrp 112
passive-interface Loopback0
eigrp router-id 172.9.0.15
!
VALIDATION:
R11:
R11#sh ipv6 route
IPv6 Routing Table - default - 13 entries

Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - ND Default, NDp - ND Prefix, DCE - Destination, NDr - Redirect
l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
OE2 2002:172:9::2/128 [110/1]
via FE80::A8BB:CCFF:FE00:7020, Ethernet0/2
OE2 2002:172:9::3/128 [110/1]
OE2 2002:172:9::8/128 [110/1]
LC 2002:172:9::11/128 [0/0]
via Loopback0, receive
O 2002:172:9::12/128 [110/10]
OE2 2002:172:9::14/128 [110/1]
OE2 2002:172:9::15/128 [110/1]
C 2002:172:9:112::/64 [0/0]
via Ethernet0/2, directly connected
L 2002:172:9:112::11/128 [0/0]
via Ethernet0/2, receive
OE2 2002:172:9:128::/64 [110/20]
OE2 2002:172:9:143::/64 [110/1]
OE2 2002:172:9:145::/64 [110/1]
L FF00::/8 [0/0]
via Null0, receive
88
R11#ping 2002:172:9::11 r 1
Sending 1, 100-byte ICMP Echos to 2002:172:9::11, timeout is 2 seconds:
!
R11#ping 2002:172:9::12 r 1
!
R11#ping 2002:172:9::14 r 1
!
R11#ping 2002:172:9::15 r 1
!
R12:
R12#sh ipv6 route

l - LISP
B 2002:172:9::2/128 [20/0]
via FE80::A8BB:CCFF:FE00:6C00, Ethernet0/1
B 2002:172:9::3/128 [20/0]
B 2002:172:9::8/128 [20/0]
O 2002:172:9::11/128 [110/10]
via FE80::A8BB:CCFF:FE00:6F20, Ethernet0/2
LC 2002:172:9::12/128 [0/0]
B 2002:172:9::14/128 [20/0]
B 2002:172:9::15/128 [20/0]
C 2002:172:9:112::/64 [0/0]
L 2002:172:9:112::12/128 [0/0]
C 2002:172:9:128::/64 [0/0]
L 2002:172:9:128::12/128 [0/0]
B 2002:172:9:143::/64 [20/0]
B 2002:172:9:145::/64 [20/0]
L FF00::/8 [0/0]
via Null0, receive
R12#ping 2002:172:9::11 r 1
!
R12#ping 2002:172:9::12 r 1
!
R12#ping 2002:172:9::14 r 1
!
R12#ping 2002:172:9::15 r 1
!
89
R14:
R14#sh ipv6 route

l - LISP
EX 2002:172:9::2/128 [170/332800]
via FE80::E2:72FF:FE46:519F, Ethernet0/1
D 2002:172:9::3/128 [90/409600]
EX 2002:172:9::8/128 [170/332800]
EX 2002:172:9::11/128 [170/332800], tag 112
EX 2002:172:9::12/128 [170/332800], tag 112
LC 2002:172:9::14/128 [0/0]
D 2002:172:9::15/128 [90/409600]
EX 2002:172:9:112::/64 [170/332800], tag 112
EX 2002:172:9:128::/64 [170/332800], tag 112
C 2002:172:9:143::/64 [0/0]
L 2002:172:9:143::14/128 [0/0]
C 2002:172:9:145::/64 [0/0]
L 2002:172:9:145::14/128 [0/0]
L FF00::/8 [0/0]
via Null0, receive
R14#ping 2002:172:9::11 r 1
!
R14#ping 2002:172:9::12 r 1
!
R14#ping 2002:172:9::14 r 1
!
R14#ping 2002:172:9::15 r 1
!
R15:
R15#sh ipv6 route

l - LISP
EX 2002:172:9::2/128 [170/358400]
D 2002:172:9::3/128 [90/435200]
EX 2002:172:9::8/128 [170/358400]
EX 2002:172:9::11/128 [170/358400], tag 112
EX 2002:172:9::12/128 [170/358400], tag 112
90
D 2002:172:9::14/128 [90/409600]
LC 2002:172:9::15/128 [0/0]
EX 2002:172:9:112::/64 [170/358400], tag 112
EX 2002:172:9:128::/64 [170/358400], tag 112
D 2002:172:9:143::/64 [90/307200]
C 2002:172:9:145::/64 [0/0]
L 2002:172:9:145::15/128 [0/0]
L FF00::/8 [0/0]
via Null0, receive
R15#ping 2002:172:9::11 r 1
!
R15#ping 2002:172:9::11 r 1
!
R15#ping 2002:172:9::12 r 1
!
R15#ping 2002:172:9::14 r 1
!
R15#ping 2002:172:9::15 r 1
!
3.5 INTER-AS VPNV4
 Configure R1 and R2 to establish eBGP VPNv4 sessions.

 Other routers in AS-9 and AS-1009 should not exchange EBGP VPNv4 routes between these two
autonomous systems.
 The ABC Company at Site3 uses EIGRP for connection to the SP router R9 and R10.
 Configure EIGRP on R9, R10, R17 and R18 on the interfaces that are shown in the Table 14.
Table 14: EIGRP IPv4 interface in VRF ABC Site 3
Router Interface AS
R9 Loopback1 100
E0/2 100
R10 Loopback1 100
E0/2 100
R17 Loopback0 100
E0/0 100
E0/1 100
R18 Loopback0 100
E0/0 100
E0/1 100
91
 Interfaces that are not listed in the table are not permitted to enable EIGRP
 Only the import RT method can be used to control VPNv4 route distribution.
 Configure accordingly so that routers of ABC at Site 1, 2 and 3 can ping each over via IPv4.
 You are permitted to define static route on R1 and R2.
Note: Configuration of the ABC Sites 1 and 2 have been done in task 3.3
SOLUTION:
ABC Site 3:
R9: AS1009 PE R17: AS1009 CE
description Link to R17 E0/0 interface Ethernet0/0
vrf forwarding ABC description Link to R9 E0/2
! !
ip address 172.9.0.9 255.255.255.255 !
router eigrp 100 description Link to R18 E0/1
! ip address 172.9.178.17 255.255.255.0
default-metric 100000 10 255 1 1500 router eigrp 100
redistribute bgp 1009 network 172.9.0.17 0.0.0.0
network 172.9.0.9 0.0.0.0 network 172.9.178.17 0.0.0.0
network 172.9.197.9 0.0.0.0 network 172.9.197.17 0.0.0.0
autonomous-system 100 !
exit-address-family
!
router bgp 1009
!
exit-address-family
!
network 172.9.0.9 mask 255.255.255.255
redistribute eigrp 100
exit-address-family
!
R10: AS1009 PE R18: AS1009 CE

ip address 172.9.108.10 255.255.255.0 !
interface Loopback1 description Link to R17 E0/1
ip address 172.9.0.10 255.255.255.255 !
router eigrp 100 ip address 172.9.0.18 255.255.255.255
! !
address-family ipv4 vrf ABC router eigrp 100
default-metric 100000 10 255 1 1500 network 172.9.0.18 0.0.0.0
redistribute bgp 1009 network 172.9.108.18 0.0.0.0
network 172.9.0.10 0.0.0.0 network 172.9.178.18 0.0.0.0
network 172.9.108.10 0.0.0.0 !
autonomous-system 100
exit-address-family
!
router bgp 1009
92
!
exit-address-family
!
network 172.9.0.10 mask 255.255.255.255
redistribute eigrp 100
exit-address-family
R1: AS1009 ASBR – R2: AS9 ASBR
R1: AS1009 ASBR R2: AS9 ASBR

vrf ABC
vrf ABC address-family ipv4 unicast
address-family ipv4 unicast import route-target
import route-target 9:9
9:9 1009:9
1009:9 !
! export route-target
export route-target 9:9
1009:9 !
! !
! description Link to R1 Gig0/0/0/0
interface GigabitEthernet0/0/0/0 cdp
description Link to R2 Gi0/0/0/0 ipv4 address 9.9.12.2 255.255.255.0
cdp !
ipv4 address 9.9.12.1 255.255.255.0 router bgp 9
! !
router bgp 1009 address-family vpnv4 unicast
! !
address-family vpnv4 unicast neighbor 9.9.0.3
! remote-as 9
remote-as 1009 !
update-source Loopback0 address-family vpnv4 unicast
! route-reflector-client
address-family vpnv4 unicast next-hop-self
route-reflector-client !
next-hop-self !
! neighbor 9.9.0.4
! remote-as 9
remote-as 1009 !
update-source Loopback0 address-family vpnv4 unicast
address-family vpnv4 unicast next-hop-self
route-reflector-client !
next-hop-self !
! neighbor 9.9.0.7
! remote-as 9
remote-as 9 !
address-family vpnv4 unicast route-reflector-client
route-policy default_policy_pass_all in next-hop-self
route-policy default_policy_pass_all out !
! !
vrf ABC neighbor 9.9.0.8
rd 1009:9 remote-as 9
address-family ipv4 unicast update-source Loopback0
network 172.9.0.1/32 !
! next-hop-self
router static !
9.9.12.2/32 GigabitEthernet0/0/0/0 neighbor 9.9.12.1
! remote-as 1009
! !
route-policy default_policy_pass_all address-family vpnv4 unicast
pass route-policy default_policy_pass_all in
end-policy route-policy default_policy_pass_all out
! !
vrf ABC
rd 9:9
network 172.9.0.2/32
!
93
!
!
router static
9.9.12.1/32 GigabitEthernet0/0/0/2
!
!
pass
end-policy
!
VALIDATION:
Note: Addition of the static route to the far end of the link between R1 and R2 is extremely
important, overwise mpls forwarding table will have no label and no outgoing interface to the far end
of link connecting two ASBRs and moreover, all prefixes from the other AS will have no outgoing
interfaces too.
Please see what happened with mpls forwarding table on R1 with and without static route:
- With static route
RP/0/0/CPU0:R1#sh mpls forwarding

Fri Jan 18 01:30:04.205 MSK
Local Outgoing Prefix Outgoing Next Hop Bytes
Label Label or ID Interface Switched
------ ----------- ------------------ ------------ --------------- ------------
16000 Pop 9.9.0.9/32 Gi0/0/0/2 9.9.19.9 971847
16001 Pop 9.9.0.6/32 Gi0/0/0/1 9.9.16.6 713021
16002 Pop 9.9.109.0/24 Gi0/0/0/2 9.9.19.9 0
16003 Pop 9.9.106.0/24 Gi0/0/0/1 9.9.16.6 0
16004 6001 9.9.0.10/32 Gi0/0/0/1 9.9.16.6 0
9005 9.9.0.10/32 Gi0/0/0/2 9.9.19.9 312582
16005 6005 9.9.0.20/32 Gi0/0/0/1 9.9.16.6 0
9011 9.9.0.20/32 Gi0/0/0/2 9.9.19.9 0
16006 6006 9.9.120.0/24 Gi0/0/0/1 9.9.16.6 0
9012 9.9.120.0/24 Gi0/0/0/2 9.9.19.9 0
16007 Aggregate ABC: Per-VRF Aggr[V] \
ABC 0
ABC 0
16009 9009 172.9.0.9/32[V] 9.9.0.9 0
16010 10009 172.9.0.10/32[V] 9.9.0.10 0
16012 9000 172.9.0.17/32[V] 9.9.0.9 391550
16013 10002 172.9.0.18/32[V] 9.9.0.10 0
16014 10013 172.9.108.0/24[V] 9.9.0.10 0
16015 9001 172.9.178.0/24[V] 9.9.0.9 0
16016 9015 172.9.197.0/24[V] 9.9.0.9 525352
16018 Pop 9.9.12.2/32 Gi0/0/0/0 9.9.12.2 490038
16019 26019 9:9:172.9.0.2/32 Gi0/0/0/0 9.9.12.2 0
16020 26028 9:9:172.9.0.3/32 Gi0/0/0/0 9.9.12.2 0
16021 26030 9:9:172.9.0.4/32 Gi0/0/0/0 9.9.12.2 0
16022 26020 9:9:172.9.0.7/32 Gi0/0/0/0 9.9.12.2 0
16023 26021 9:9:172.9.0.8/32 Gi0/0/0/0 9.9.12.2 0
16024 26022 9:9:172.9.0.11/32 Gi0/0/0/0 9.9.12.2 362312
16025 26023 9:9:172.9.0.12/32 Gi0/0/0/0 9.9.12.2 520
16026 26027 9:9:172.9.0.14/32 Gi0/0/0/0 9.9.12.2 520
16027 26031 9:9:172.9.0.15/32 Gi0/0/0/0 9.9.12.2 520
16028 26024 9:9:172.9.112.0/24 Gi0/0/0/0 9.9.12.2 0
16029 26026 9:9:172.9.114.0/24 Gi0/0/0/0 9.9.12.2 0
16030 26025 9:9:172.9.128.0/24 Gi0/0/0/0 9.9.12.2 0
16031 26032 9:9:172.9.143.0/24 Gi0/0/0/0 9.9.12.2 0
16032 26033 9:9:172.9.145.0/24 Gi0/0/0/0 9.9.12.2 0
16033 26034 9:9:172.9.157.0/24 Gi0/0/0/0 9.9.12.2 0
- Without static route

RP/0/0/CPU0:R1#sh mpls forwarding
Fri Jan 18 01:31:37.387 MSK
------ ----------- ------------------ ------------ --------------- ------------
16000 Pop 9.9.0.9/32 Gi0/0/0/2 9.9.19.9 972778
16001 Pop 9.9.0.6/32 Gi0/0/0/1 9.9.16.6 713558
16002 Pop 9.9.109.0/24 Gi0/0/0/2 9.9.19.9 0
16003 Pop 9.9.106.0/24 Gi0/0/0/1 9.9.16.6 0
16004 6001 9.9.0.10/32 Gi0/0/0/1 9.9.16.6 0
9005 9.9.0.10/32 Gi0/0/0/2 9.9.19.9 312733
16005 6005 9.9.0.20/32 Gi0/0/0/1 9.9.16.6 0
94
9011 9.9.0.20/32 Gi0/0/0/2 9.9.19.9 0
16006 6006 9.9.120.0/24 Gi0/0/0/1 9.9.16.6 0
9012 9.9.120.0/24 Gi0/0/0/2 9.9.19.9 0
ABC 0
ABC 0
16009 9009 172.9.0.9/32[V] 9.9.0.9 0
16010 10009 172.9.0.10/32[V] 9.9.0.10 0
16011 Aggregate 9.9.12.0/24 default 0
16012 9000 172.9.0.17/32[V] 9.9.0.9 392150
16013 10002 172.9.0.18/32[V] 9.9.0.10 0
16014 10013 172.9.108.0/24[V] 9.9.0.10 0
16015 9001 172.9.178.0/24[V] 9.9.0.9 0
16016 9015 172.9.197.0/24[V] 9.9.0.9 460360
16019 26019 9:9:172.9.0.2/32 9.9.12.2 0
16020 26028 9:9:172.9.0.3/32 9.9.12.2 0
16021 26030 9:9:172.9.0.4/32 9.9.12.2 0
16022 26020 9:9:172.9.0.7/32 9.9.12.2 0
16023 26021 9:9:172.9.0.8/32 9.9.12.2 0
16024 26022 9:9:172.9.0.11/32 9.9.12.2 362772
16025 26023 9:9:172.9.0.12/32 9.9.12.2 520
16026 26027 9:9:172.9.0.14/32 9.9.12.2 520
16027 26031 9:9:172.9.0.15/32 9.9.12.2 520
16028 26024 9:9:172.9.112.0/24 9.9.12.2 0
16029 26026 9:9:172.9.114.0/24 9.9.12.2 0
16030 26025 9:9:172.9.128.0/24 9.9.12.2 0
16031 26032 9:9:172.9.143.0/24 9.9.12.2 0
16032 26033 9:9:172.9.145.0/24 9.9.12.2 0
16033 26034 9:9:172.9.157.0/24 9.9.12.2 0
ABC Site 1: (R11 and R12)

R11:
R11#sh ip route
B 172.9.0.1/32 [20/0] via 172.9.114.4, 22:31:23
B 172.9.0.2/32 [20/0] via 172.9.114.4, 22:39:02
B 172.9.0.3/32 [20/0] via 172.9.114.4, 22:38:52
B 172.9.0.4/32 [20/0] via 172.9.114.4, 4d06h
B 172.9.0.7/32 [20/0] via 172.9.114.4, 22:39:02
B 172.9.0.8/32 [20/0] via 172.9.114.4, 22:39:02
B 172.9.0.9/32 [20/0] via 172.9.114.4, 22:31:23
B 172.9.0.10/32 [20/0] via 172.9.114.4, 22:31:23
O 172.9.0.12/32 [110/11] via 172.9.112.12, 5d10h, Ethernet0/2
B 172.9.0.14/32 [20/0] via 172.9.114.4, 22:38:52
B 172.9.0.15/32 [20/0] via 172.9.114.4, 22:38:52
B 172.9.0.17/32 [20/0] via 172.9.114.4, 22:31:23
B 172.9.0.18/32 [20/0] via 172.9.114.4, 22:31:23
B 172.9.108.0/24 [20/0] via 172.9.114.4, 22:31:23
B 172.9.128.0/24 [20/0] via 172.9.114.4, 22:39:02
B 172.9.143.0/24 [20/0] via 172.9.114.4, 22:38:52
B 172.9.145.0/24 [20/0] via 172.9.114.4, 22:38:52
B 172.9.157.0/24 [20/0] via 172.9.114.4, 22:38:52
B 172.9.178.0/24 [20/0] via 172.9.114.4, 22:31:23
B 172.9.197.0/24 [20/0] via 172.9.114.4, 22:31:23
R11#ping 172.9.0.11 r 1
!
R11#ping 172.9.0.12 r 1
!
95
R11#ping 172.9.0.14 r 1
!
R11#ping 172.9.0.15 r 1
!
Success rate is 100 percent (1/1), round-trip min/avg/max = 6
R11#ping 172.9.0.17 r 1
!
R11#ping 172.9.0.18 r 1
!
R12:
R12#sh ip route

B 172.9.0.1/32 [20/0] via 172.9.128.8, 22:38:27
B 172.9.0.2/32 [20/0] via 172.9.128.8, 22:46:22
B 172.9.0.3/32 [20/0] via 172.9.128.8, 22:45:56
B 172.9.0.4/32 [20/0] via 172.9.128.8, 22:46:06
B 172.9.0.7/32 [20/0] via 172.9.128.8, 22:46:22
B 172.9.0.8/32 [20/0] via 172.9.128.8, 2d13h
B 172.9.0.9/32 [20/0] via 172.9.128.8, 22:38:27
B 172.9.0.10/32 [20/0] via 172.9.128.8, 22:38:27
O 172.9.0.11/32 [110/11] via 172.9.112.11, 5d10h, Ethernet0/2
B 172.9.0.14/32 [20/0] via 172.9.128.8, 22:45:56
B 172.9.0.15/32 [20/0] via 172.9.128.8, 22:45:56
B 172.9.0.17/32 [20/0] via 172.9.128.8, 22:38:27
B 172.9.0.18/32 [20/0] via 172.9.128.8, 22:38:27
B 172.9.108.0/24 [20/0] via 172.9.128.8, 22:38:27
B 172.9.114.0/24 [20/0] via 172.9.128.8, 22:46:06
B 172.9.143.0/24 [20/0] via 172.9.128.8, 22:45:56
B 172.9.145.0/24 [20/0] via 172.9.128.8, 22:45:56
B 172.9.157.0/24 [20/0] via 172.9.128.8, 22:45:56
B 172.9.178.0/24 [20/0] via 172.9.128.8, 22:38:27
B 172.9.197.0/24 [20/0] via 172.9.128.8, 22:38:27
R12#ping 172.9.0.11 r 1
!
R12#ping 172.9.0.12 r 1
!
R12#ping 172.9.0.14 r 1
!
96
R12#ping 172.9.0.15 r 1
!
R12#ping 172.9.0.17 r 1
!
R12#ping 172.9.0.18 r 1
!
R14:
R14#sh ip route
B 172.9.0.1/32 [20/0] via 172.9.143.3, 22:42:53
B 172.9.0.2/32 [20/0] via 172.9.143.3, 22:50:22
B 172.9.0.3/32 [20/0] via 172.9.143.3, 4d01h
B 172.9.0.4/32 [20/0] via 172.9.143.3, 22:50:22
O 172.9.0.7/32 [110/21] via 172.9.145.15, 4d01h, Ethernet0/2
B 172.9.0.8/32 [20/0] via 172.9.143.3, 22:50:22
B 172.9.0.9/32 [20/0] via 172.9.143.3, 22:42:53
B 172.9.0.10/32 [20/0] via 172.9.143.3, 22:42:53
B 172.9.0.11/32 [20/0] via 172.9.143.3, 22:50:22
B 172.9.0.12/32 [20/0] via 172.9.143.3, 22:50:22
O 172.9.0.15/32 [110/11] via 172.9.145.15, 4d01h, Ethernet0/2
B 172.9.0.17/32 [20/0] via 172.9.143.3, 22:42:53
B 172.9.0.18/32 [20/0] via 172.9.143.3, 22:42:53
B 172.9.108.0/24 [20/0] via 172.9.143.3, 22:42:53
B 172.9.112.0/24 [20/0] via 172.9.143.3, 22:50:22
B 172.9.114.0/24 [20/0] via 172.9.143.3, 22:50:22
B 172.9.128.0/24 [20/0] via 172.9.143.3, 22:50:22
O 172.9.157.0/24 [110/20] via 172.9.145.15, 4d01h, Ethernet0/2
B 172.9.178.0/24 [20/0] via 172.9.143.3, 22:42:53
B 172.9.197.0/24 [20/0] via 172.9.143.3, 22:42:53
R14#ping 172.9.0.11 r 1
!
R14#ping 172.9.0.12 r 1
!
R14#ping 172.9.0.14 r 1
!
R14#ping 172.9.0.15 r 1
!
97
R14#ping 172.9.0.17 r 1
!
R14#ping 172.9.0.18 r 1
!
R15:
R15#sh ip route

O E2 172.9.0.1/32 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.0.2/32 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.0.4/32 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O 172.9.0.7/32 [110/11] via 172.9.157.7, 4d06h, Ethernet0/1
O E2 172.9.0.8/32 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.0.9/32 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.0.10/32 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.0.11/32 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.0.12/32 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O 172.9.0.14/32 [110/11] via 172.9.145.14, 5d10h, Ethernet0/2
O E2 172.9.0.17/32 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.0.18/32 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.108.0/24 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.112.0/24 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.114.0/24 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.128.0/24 [110/1] via 172.9.145.14, 22:53:17, Ethernet0/2
O E2 172.9.178.0/24 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
O E2 172.9.197.0/24 [110/1] via 172.9.145.14, 22:45:48, Ethernet0/2
R15# ping 172.9.0.11 r 1

!
R15# ping 172.9.0.12 r 1
!
R15# ping 172.9.0.14 r 1
!
R15# ping 172.9.0.15 r 1
!
R15# ping 172.9.0.17 r 1
!
R15# ping 172.9.0.18 r 1
98
!
R17:
R17#sh ip route
D EX 172.9.0.1/32 [170/284160] via 172.9.197.9, 22:58:50, Ethernet0/0
D EX 172.9.0.2/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.3/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.4/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.7/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.8/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D 172.9.0.9/32 [90/409600] via 172.9.197.9, 22:58:50, Ethernet0/0
D 172.9.0.10/32 [90/409600] via 172.9.197.9, 22:58:50, Ethernet0/0
D EX 172.9.0.11/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.12/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.14/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.0.15/32 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D 172.9.0.18/32 [90/409600] via 172.9.178.18, 22:58:50, Ethernet0/1
D 172.9.108.0/24 [90/307200] via 172.9.197.9, 22:58:50, Ethernet0/0
[90/307200] via 172.9.178.18, 22:58:50, Ethernet0/1
D EX 172.9.112.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.114.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.128.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.143.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.145.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
D EX 172.9.157.0/24 [170/284160] via 172.9.197.9, 22:52:45, Ethernet0/0
R17#ping 172.9.0.11 r 1
!
R17#ping 172.9.0.12 r 1
!
R17#ping 172.9.0.14 r 1
!
R17#ping 172.9.0.15 r 1
!
R17#ping 172.9.0.17 r 1
!
R17#ping 172.9.0.18 r 1
!
99
R18:
R18#sh ip route


D EX 172.9.0.1/32 [170/284160] via 172.9.108.10, 23:02:48, Ethernet0/0
D EX 172.9.0.2/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.3/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.4/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.7/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.8/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D 172.9.0.9/32 [90/409600] via 172.9.108.10, 23:02:48, Ethernet0/0
D 172.9.0.10/32 [90/409600] via 172.9.108.10, 23:02:48, Ethernet0/0
D EX 172.9.0.11/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.12/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.14/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.0.15/32 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D 172.9.0.17/32 [90/409600] via 172.9.178.17, 23:02:48, Ethernet0/1
D EX 172.9.112.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.114.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.128.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.143.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.145.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D EX 172.9.157.0/24 [170/284160] via 172.9.108.10, 22:56:43, Ethernet0/0
D 172.9.197.0/24 [90/307200] via 172.9.178.17, 23:02:48, Ethernet0/1
[90/307200] via 172.9.108.10, 23:02:48, Ethernet0/0
R18#ping 172.9.0.11 r 1
!
R18#ping 172.9.0.12 r 1
!
R18#ping 172.9.0.14 r 1
!
R18#ping 172.9.0.15 r 1
!
R18#ping 172.9.0.17 r 1
!
R18#ping 172.9.0.18 r 1
!
100
3.6 INTER-AS VPNV6
 Configure R1 and R2 to establish eBGP VPNv6 sessions.

 Other routers in AS9 and AS1009 should not exchange EBGP VPNv6 routes between these two
autonomous systems.
 The ABC Company at Site3 uses BGP for connection to the SP routers R9, R17 and router R18 are
located in AS178.
 Establish eBGP IPv6 unicast session between R9 and R17
 Establish iBGP IPv6 unicast session between R17 and R18
 Only the import RT method can be used to control VPNv6 route distribution.
 Configure accordingly so that routers of ABC at Site 1, 2 and 3 can ping each over via IPv6.
Note: Configuration of the ABC Sites 1 and 2 has been done in task 3.4.
Congiguration changes made on previous steps 3.4 and 3.5 are highlighted in green, they are
mentioned to keep the understandability of the configuration.
SOLUTION:
ABC Site 3:
R9: R17:
vrf definition ABC interface Ethernet0/0

rd 1009:9 description Link to R9 E0/2
! ipv6 address 2002:172:9:197::17/64
route-target export 1009:9 interface Ethernet0/1
route-target import 1009:9 description Link to R18 E0/1
exit-address-family ipv6 address 2002:172:9:178::17/64
! !
interface Ethernet0/2 interface Loopback0
description Link to R17 E0/0 ipv6 address 2002:172:9::17/128
vrf forwarding ABC end
ipv6 address 2002:172:9:197::9/64 !
! router bgp 178
interface Loopback1 neighbor 2002:172:9:178::18 remote-as 178
vrf forwarding ABC neighbor 2002:172:9:197::9 remote-as 1009
ipv6 address 2002:172:9::9/128 !
router bgp 1009 network 2002:172:9::17/128
! network 2002:172:9:178::/64
address-family vpnv6 network 2002:172:9:197::/64
neighbor 9.9.0.1 activate neighbor 2002:172:9:178::18 activate
neighbor 9.9.0.1 send-community extended neighbor 2002:172:9:178::18 next-hop-self
exit-address-family neighbor 2002:172:9:197::9 activate
neighbor 2002:172:9:197::17 remote-as 178
network 2002:172:9::9/128
exit-address-family
R18:
ipv6 address 2002:172:9:178::18/64
!
interface Loopback0
ipv6 address 2002:172:9::18/128
!
router bgp 178
neighbor 2002:172:9:178::17 remote-as 178
!
address-family ipv6
101
network 2002:172:9::18/128
exit-address-family
!
R1: AS1009 ASBR – R2: AS9 ASBR
R1: AS1009 ASBR R2: AS9 ASBR
vrf ABC vrf ABC

import route-target import route-target
9:9 9:9
1009:9 1009:9
! !
export route-target export route-target
1009:9 9:9
! !
! !
! !
description Link to R2 Gi0/0/0/0 description Link to R1 Gig0/0/0/0
cdp cdp
ipv4 address 9.9.12.1 255.255.255.0 ipv4 address 9.9.12.2 255.255.255.0
! !
! !
address-family vpnv6 unicast address-family vpnv6 unicast
! !
! !
address-family vpnv6 unicast address-family vpnv6 unicast
next-hop-self route-reflector-client
! next-hop-self
! !
neighbor 9.9.12.2 !
remote-as 9 neighbor 9.9.0.8
! remote-as 9
address-family vpnv6 unicast update-source Loopback0
route-policy default_policy_pass_all in !
route-policy default_policy_pass_all out address-family vpnv6 unicast
! next-hop-self
vrf ABC !
rd 1009:9 !
! neighbor 9.9.12.1
address-family ipv6 unicast remote-as 1009
network 2002:172:9::1/128 !
! route-policy default_policy_pass_all in
! route-policy default_policy_pass_all out
!
route-policy default_policy_pass_all !
pass vrf ABC
end-policy rd 9:9
! !
router static address-family ipv6 unicast
address-family ipv4 unicast network 2002:172:9::2/128
9.9.12.2/32 GigabitEthernet0/0/0/0 !
! !
! !
pass
end-policy
!
router static
9.9.0.88/32 tunnel-te28
9.9.12.1/32 GigabitEthernet0/0/0/2
!
!
VALIDATION:
Note: Addition of the static route to the far end of the link between R1 and R2 is extremely
important, overwise mpls forwarding table will have no label and no outgoing interface to the far end
102
of link connecting two ASBRs and moreover, all prefixes from the other AS will have no outgoing
interfaces too.
R8: AS9 PE for ABC Site 1
R8#sh ip bgp vpnv6 unicast vrf ABC


*>i2002:172:9::1/128
::FFFF:9.9.0.2 0 100 0 1009 i
*>i2002:172:9::2/128
::FFFF:9.9.0.2 0 100 0 i
*>i2002:172:9::3/128
::FFFF:9.9.0.3 0 100 0 i
*> 2002:172:9::8/128
:: 0 32768 i
*>i2002:172:9::9/128
::FFFF:9.9.0.2 100 0 1009 i
*> 2002:172:9::11/128
2002:172:9:128::12
10 0 112 ?
*> 2002:172:9::12/128
2002:172:9:128::12
0 0 112 i
*>i2002:172:9::14/128
::FFFF:9.9.0.3 130816 100 0 ?
*>i2002:172:9::15/128
::FFFF:9.9.0.3 409856 100 0 ?
*>i2002:172:9::17/128
::FFFF:9.9.0.2 100 0 1009 178 i
*>i2002:172:9::18/128
::FFFF:9.9.0.2 100 0 1009 178 i
*> 2002:172:9:112::/64
2002:172:9:128::12
0 0 112 ?
r> 2002:172:9:128::/64
2002:172:9:128::12
0 0 112 ?
*>i2002:172:9:143::/64
::FFFF:9.9.0.3 0 100 0 ?
*>i2002:172:9:145::/64
::FFFF:9.9.0.3 281856 100 0 ?
*>i2002:172:9:178::/64
::FFFF:9.9.0.2 100 0 1009 178 i
*>i2002:172:9:197::/64
::FFFF:9.9.0.2 100 0 1009 178 i
R11: ABC Site 1 CE1

R11#sh ipv6 route
l - LISP
OE2 2002:172:9::1/128 [110/1]
OE2 2002:172:9::2/128 [110/1]
OE2 2002:172:9::3/128 [110/1]
OE2 2002:172:9::8/128 [110/1]
OE2 2002:172:9::9/128 [110/1]
LC 2002:172:9::11/128 [0/0]
O 2002:172:9::12/128 [110/10]
OE2 2002:172:9::14/128 [110/1]
103
OE2 2002:172:9::15/128 [110/1]
OE2 2002:172:9::17/128 [110/1]
OE2 2002:172:9::18/128 [110/1]
C 2002:172:9:112::/64 [0/0]
L 2002:172:9:112::11/128 [0/0]
OE2 2002:172:9:128::/64 [110/20]
OE2 2002:172:9:143::/64 [110/1]
OE2 2002:172:9:145::/64 [110/1]
OE2 2002:172:9:178::/64 [110/1]
OE2 2002:172:9:197::/64 [110/1]
L FF00::/8 [0/0]
via Null0, receive
R11#ping 2002:172:9::11 r 1
!
R11#ping 2002:172:9::12 r 1
!
R11#ping 2002:172:9::14 r 1
!
R11#ping 2002:172:9::15 r 1
!
R11#ping 2002:172:9::17 r 1
!
R11#ping 2002:172:9::18 r 1
!
R12: ABC Site 1 CE2
R12#sh ipv6 route

l - LISP
B 2002:172:9::1/128 [20/0]
B 2002:172:9::2/128 [20/0]
B 2002:172:9::3/128 [20/0]
B 2002:172:9::8/128 [20/0]
B 2002:172:9::9/128 [20/0]
O 2002:172:9::11/128 [110/10]
via FE80::A8BB:CCFF:FE00:6F20, Ethernet0/2
LC 2002:172:9::12/128 [0/0]
B 2002:172:9::14/128 [20/0]
104
B 2002:172:9::15/128 [20/0]
B 2002:172:9::17/128 [20/0]
B 2002:172:9::18/128 [20/0]
C 2002:172:9:112::/64 [0/0]
L 2002:172:9:112::12/128 [0/0]
C 2002:172:9:128::/64 [0/0]
L 2002:172:9:128::12/128 [0/0]
B 2002:172:9:143::/64 [20/0]
B 2002:172:9:145::/64 [20/0]
B 2002:172:9:178::/64 [20/0]
B 2002:172:9:197::/64 [20/0]
L FF00::/8 [0/0]
via Null0, receive
R12#ping 2002:172:9::11 r 1
!
R12#ping 2002:172:9::12 r 1
!
R12#ping 2002:172:9::14 r 1
!
R12#ping 2002:172:9::15 r 1
!
R12#ping 2002:172:9::17 r 1
!
R12#ping 2002:172:9::18 r 1
!

Fri Jan 18 14:04:18.475 MSK

*>i2002:172:9::1/128 9.9.0.2 0 100 0 1009 i
*>i2002:172:9::2/128 9.9.0.2 0 100 0 i
*> 2002:172:9::3/128 :: 0 32768 i
*>i2002:172:9::8/128 9.9.0.8 0 100 0 i
*>i2002:172:9::9/128 9.9.0.2 100 0 1009 i
105
*>i2002:172:9::11/128 9.9.0.8 10 100 0 112 ?
*>i2002:172:9::12/128 9.9.0.8 0 100 0 112 i
*> 2002:172:9::14/128 fe80::a8bb:ccff:fe00:7210
130816 32768 ?
*> 2002:172:9::15/128 fe80::a8bb:ccff:fe00:7210
409856 32768 ?
*>i2002:172:9::17/128 9.9.0.2 100 0 1009 178 i
*>i2002:172:9::18/128 9.9.0.2 100 0 1009 178 i
*>i2002:172:9:112::/64
9.9.0.8 0 100 0 112 ?
*>i2002:172:9:128::/64
9.9.0.8 0 100 0 112 ?
*> 2002:172:9:143::/64
:: 0 32768 ?
*> 2002:172:9:145::/64
fe80::a8bb:ccff:fe00:7210
281856 32768 ?
*>i2002:172:9:178::/64
9.9.0.2 100 0 1009 178 i
*>i2002:172:9:197::/64
9.9.0.2 100 0 1009 178 i
R14: ABC Site 2 CE1

R14#sh ipv6 route

l - LISP
EX 2002:172:9::1/128 [170/332800], tag 1009
EX 2002:172:9::2/128 [170/332800]
D 2002:172:9::3/128 [90/409600]
EX 2002:172:9::8/128 [170/332800]
EX 2002:172:9::9/128 [170/332800], tag 1009
EX 2002:172:9::11/128 [170/332800], tag 112
EX 2002:172:9::12/128 [170/332800], tag 112
LC 2002:172:9::14/128 [0/0]
D 2002:172:9::15/128 [90/409600]
EX 2002:172:9::17/128 [170/332800], tag 1009
EX 2002:172:9::18/128 [170/332800], tag 1009
EX 2002:172:9:112::/64 [170/332800], tag 112
EX 2002:172:9:128::/64 [170/332800], tag 112
C 2002:172:9:143::/64 [0/0]
L 2002:172:9:143::14/128 [0/0]
C 2002:172:9:145::/64 [0/0]
L 2002:172:9:145::14/128 [0/0]
EX 2002:172:9:178::/64 [170/332800], tag 1009
EX 2002:172:9:197::/64 [170/332800], tag 1009
L FF00::/8 [0/0]
via Null0, receive
R15: ABC Site 2 CE2

R15#sh ipv6 route
l - LISP
106
EX 2002:172:9::1/128 [170/358400], tag 1009
EX 2002:172:9::2/128 [170/358400]
D 2002:172:9::3/128 [90/435200]
EX 2002:172:9::8/128 [170/358400]
EX 2002:172:9::9/128 [170/358400], tag 1009
EX 2002:172:9::11/128 [170/358400], tag 112
EX 2002:172:9::12/128 [170/358400], tag 112
D 2002:172:9::14/128 [90/409600]
LC 2002:172:9::15/128 [0/0]
EX 2002:172:9::17/128 [170/358400], tag 1009
EX 2002:172:9::18/128 [170/358400], tag 1009
EX 2002:172:9:112::/64 [170/358400], tag 112
EX 2002:172:9:128::/64 [170/358400], tag 112
D 2002:172:9:143::/64 [90/307200]
C 2002:172:9:145::/64 [0/0]
L 2002:172:9:145::15/128 [0/0]
EX 2002:172:9:178::/64 [170/358400], tag 1009
EX 2002:172:9:197::/64 [170/358400], tag 1009
L FF00::/8 [0/0]
via Null0, receive
R15#ping 2002:172:9::11 r 1
!
R15#ping 2002:172:9::12 r 1
!
R15#ping 2002:172:9::14 r 1
!
R15#ping 2002:172:9::15 r 1
!
R15#ping 2002:172:9::17 r 1
!
R15#ping 2002:172:9::18 r 1
!
R9#sh ip bgp vpnv6 unicast vrf ABC

107
*>i2002:172:9::1/128
::FFFF:9.9.0.1 0 100 0 i
*>i2002:172:9::2/128
::FFFF:9.9.0.1 0 100 0 9 i
*>i2002:172:9::3/128
::FFFF:9.9.0.1 100 0 9 i
*>i2002:172:9::8/128
::FFFF:9.9.0.1 100 0 9 i
*> 2002:172:9::9/128
:: 0 32768 i
*>i2002:172:9::11/128
::FFFF:9.9.0.1 100 0 9 112 ?
*>i2002:172:9::12/128
::FFFF:9.9.0.1 100 0 9 112 i
*>i2002:172:9::14/128
::FFFF:9.9.0.1 100 0 9 ?
*>i2002:172:9::15/128
::FFFF:9.9.0.1 100 0 9 ?
*> 2002:172:9::17/128
2002:172:9:197::17
0 0 178 i
*> 2002:172:9::18/128
2002:172:9:197::17
0 178 i
*>i2002:172:9:112::/64
::FFFF:9.9.0.1 100 0 9 112 ?
*>i2002:172:9:128::/64
::FFFF:9.9.0.1 100 0 9 112 ?
*>i2002:172:9:143::/64
::FFFF:9.9.0.1 100 0 9 ?
*>i2002:172:9:145::/64
::FFFF:9.9.0.1 100 0 9 ?
*> 2002:172:9:178::/64
2002:172:9:197::17
0 0 178 i
r> 2002:172:9:197::/64
2002:172:9:197::17
0 0 178 i
R17: ABC Site 3 CE1

R17#sh ipv6 route
l - LISP
B 2002:172:9::1/128 [20/0]
via FE80::A8BB:CCFF:FE00:6D20, Ethernet0/0
B 2002:172:9::2/128 [20/0]
B 2002:172:9::3/128 [20/0]
B 2002:172:9::8/128 [20/0]
B 2002:172:9::9/128 [20/0]
B 2002:172:9::11/128 [20/0]
B 2002:172:9::12/128 [20/0]
B 2002:172:9::14/128 [20/0]
B 2002:172:9::15/128 [20/0]
LC 2002:172:9::17/128 [0/0]
B 2002:172:9::18/128 [200/0]
via 2002:172:9:178::18
B 2002:172:9:112::/64 [20/0]
B 2002:172:9:128::/64 [20/0]
B 2002:172:9:143::/64 [20/0]
B 2002:172:9:145::/64 [20/0]
C 2002:172:9:178::/64 [0/0]
108
L 2002:172:9:178::17/128 [0/0]
C 2002:172:9:197::/64 [0/0]
L 2002:172:9:197::17/128 [0/0]
L FF00::/8 [0/0]
via Null0, receive
R17#ping 2002:172:9::11 r 1
!
R17#ping 2002:172:9::12 r 1
!
R17#ping 2002:172:9::14 r 1
!
R17#ping 2002:172:9::15 r 1
!
R17#ping 2002:172:9::17 r 1
!
R17#ping 2002:172:9::18 r 1
!
R18: ABC Site 3 CE2

R18#sh ipv6 route
l - LISP
B 2002:172:9::1/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::2/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::3/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::8/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::9/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::11/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::12/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::14/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::15/128 [200/0]
via 2002:172:9:178::17
B 2002:172:9::17/128 [200/0]
via 2002:172:9:178::17
LC 2002:172:9::18/128 [0/0]
B 2002:172:9:112::/64 [200/0]
via 2002:172:9:178::17
B 2002:172:9:128::/64 [200/0]
via 2002:172:9:178::17
B 2002:172:9:143::/64 [200/0]
via 2002:172:9:178::17
B 2002:172:9:145::/64 [200/0]
via 2002:172:9:178::17
C 2002:172:9:178::/64 [0/0]
109
L 2002:172:9:178::18/128 [0/0]
B 2002:172:9:197::/64 [200/0]
via 2002:172:9:178::17
L FF00::/8 [0/0]
via Null0, receive
R17#ping 2002:172:9::11 r 1
!
R17#ping 2002:172:9::12 r 1
!
R17#ping 2002:172:9::14 r 1
!
R17#ping 2002:172:9::15 r 1
!
R17#ping 2002:172:9::17 r 1
!
R17#ping 2002:172:9::18 r 1
!
3.7 CARRIER SUPPORTING CARRIER - 1
 VPN ABC Site1 and Site2 is one SP carrier (AS-112) that is distributed in two locations. It requests
support from the AS-9 SP carrier to provide MPLS VPNv4 service.
 Configure R3, R4, R7, R8, R11, R12, R14 and R15 so that AS-112 is able to deliver MPLS VPNv4
service.
 The XYZ Company at Site1 uses IS-IS for connection to the SP routers R11 and R12
 The XYZ Company at Site2 uses IS-IS for connection to the SP routers R14 and R15
 Configure IS-IS on the interfaces that are shown in this Table 15.
Table 15: IS-IS interfaces for CsC-1
Router Area Interface

R11 47.0192.0011 Loopback1
47.0192.0011 E0/0
R12 47.0192.0012 Loopback1
47.0192.0012 E0/0
R13 47.0192.0013 Loopback0
47.0192.0013 E0/0
47.0192.0013 E0/1
R14 47.0192.0014 Loopback1
47.0192.0014 E0/0
R15 47.0192.0015 Loopback1
47.0192.0015 E0/0
110
R16 47.0192.0016 Loopback0
47.0192.0016 E0/0
47.0192.0016 E0/1
 Establish BGP VPNv4 unicast session between R11 and R15.

 Configure accordingly so that routers of XYZ at Sites 1 and 2 can ping each over via IPv4
 You are permitted to define static route on R3 and R4 in the vrf ABC.
SOLUTION:
XYZ Site 1 (R11, R12, R13):
R11: AS112 Site1 PE1 R12: AS112 Site1 PE2
vrf definition XYZ vrf definition XYZ

rd 112:112 rd 112:112
! !
! !
vrf forwarding XYZ vrf forwarding XYZ
! !
! !
mpls bgp forwarding ! configured automatically mpls bgp forwarding ! configured automatically
! after neighbor ! after neighbor
! 172.9.114.4 send-label ! 172.9.128.8 send-label
router ospf 112 router ospf 112
redistribute bgp 112 subnets redistribute bgp 112 subnets
! !
vrf XYZ vrf XYZ
net 47.0192.0011.0000.0000.0011.00 net 47.0192.0012.0000.0000.0012.00
redistribute bgp 112 !
! router bgp 112
neighbor 172.9.0.15 remote-as 112 !
neighbor 172.9.0.15 update-source Loopback0 address-family ipv4
neighbor 172.9.114.4 remote-as 9 network 172.9.128.0 mask 255.255.255.0
! redistribute ospf 112
address-family ipv4 neighbor 172.9.128.8 activate
network 172.9.114.0 mask 255.255.255.0 neighbor 172.9.128.8 send-label
redistribute ospf 112 exit-address-family
neighbor 172.9.114.4 activate !
neighbor 172.9.114.4 send-label
exit-address-family
!
exit-address-family
!
address-family ipv4 vrf XYZ
redistribute connected
redistribute isis level-2
exit-address-family
111
R13: AS112 Site1 CE
interface Loopback0
ip address 192.9.0.13 255.255.255.255
ip router isis
!
description Link R11 E0/0
ip address 192.9.113.13 255.255.255.0
ip router isis
!
ip address 192.9.123.13 255.255.255.0
ip router isis
!
router isis
net 47.0192.0013.0000.0000.0013.00
is-type level-2-only
metric-style wide
!
XYZ Site 2 (R14, R15, R16):
R14: AS112 Site2 PE1 R15: AS112 Site2 PE2
vrf definition XYZ vrf definition XYZ

rd 112:112 rd 112:112
! !
! !
vrf forwarding XYZ description Link to R16 E0/1
ip address 192.9.146.14 255.255.255.0 vrf forwarding XYZ
ip router isis ip address 192.9.156.15 255.255.255.0
isis circuit-type level-2-only ip router isis
description Link to R3 Gi0/0/0/1 interface Ethernet0/1
mpls bgp forwarding! configured automatically ip address 172.9.157.15 255.255.255.0
! after neighbor mpls ip
! 172.9.143.3 send-label !
! description Link to R14 E0/2
interface Ethernet0/2 ip address 172.9.145.15 255.255.255.0
description Link to R15 E0/2 mpls ip
ip address 172.9.145.14 255.255.255.0 !
mpls ip router isis
! vrf XYZ
router ospf 112 net 47.0192.0015.0000.0000.0015.00
router-id 172.9.0.14 is-type level-2-only
redistribute bgp 112 subnets metric-style wide
network 172.9.0.14 0.0.0.0 area 0 log-adjacency-changes all
network 172.9.145.14 0.0.0.0 area 0 redistribute bgp 112
! !
router isis router ospf 112
vrf XYZ router-id 172.9.0.15
net 47.0192.0014.0000.0000.0014.00 network 172.9.0.15 0.0.0.0 area 0
is-type level-2-only network 172.9.145.15 0.0.0.0 area 0
metric-style wide network 172.9.157.15 0.0.0.0 area 0
log-adjacency-changes all !
! router bgp 112
neighbor 172.9.143.3 remote-as 9 neighbor 172.9.0.11 update-source Loopback0
! !
address-family ipv4 address-family vpnv4
network 172.9.143.0 mask 255.255.255.0 neighbor 172.9.0.11 activate
112
redistribute ospf 112 neighbor 172.9.0.11 send-community extended
neighbor 172.9.143.3 activate exit-address-family
neighbor 172.9.143.3 send-label !
exit-address-family address-family ipv4 vrf XYZ
! redistribute connected
! redistribute isis level-2
exit-address-family
!
R16: AS112 Site2 CE
interface Loopback0
ip address 192.9.0.16 255.255.255.255
ip router isis
!
ip address 192.9.146.16 255.255.255.0
ip router isis
!
ip address 192.9.156.16 255.255.255.0
ip router isis
!
router isis
net 47.0192.0016.0000.0000.0016.00
is-type level-2-only
metric-style wide
!
AS9-AS112: (R3 CsC PE1; R4 CsC PE2)
R3: R4:

! !
vrf ABC vrf ABC
rd 9:9 rd 9:9
network 172.9.0.3/32 network 172.9.0.4/32
allocate-label all allocate-label all
! !
address-family ipv4 labeled-unicast address-family ipv4 labeled-unicast
route-policy default_policy_pass_all in route-policy default_policy_pass_all in
route-policy default_policy_pass_all out route-policy default_policy_pass_all out
as-override as-override
send-extended-community-ebgp send-extended-community-ebgp
! !
! !
! !
! !
router static router static
vrf ABC vrf ABC
172.9.143.14/32 GigabitEthernet0/0/0/4 172.9.114.11/32 GigabitEthernet0/0/0/3
! !
! !
! !
VALIDATION:
Note: Addition of the static route to the far end of the links between R3 and R14 and R4 and R11 is
extremely important, overwise mpls forwarding table will have no label and no outgoing interface to
the far end of links connecting CsC-PE and CsC-CE and moreover, all prefixes from the other AS will
have no outgoing interfaces too. It should be done on IOS-XR’s sides of these links (R3 and R4).
113
XYZ Site 1 (R11, R12, R13)
R11:
R11#sh ip bgp vpnv4 vrf XYZ

Route Distinguisher: 112:112 (default for vrf XYZ)
*> 192.9.0.11/32 0.0.0.0 0 32768 ?
*> 192.9.0.12/32 192.9.113.13 30 32768 ?
*> 192.9.0.13/32 192.9.113.13 20 32768 ?
*>i192.9.0.14/32 172.9.0.15 30 100 0 ?
*>i192.9.0.15/32 172.9.0.15 0 100 0 ?
*>i192.9.0.16/32 172.9.0.15 20 100 0 ?
*> 192.9.113.0 0.0.0.0 0 32768 ?
*> 192.9.123.0 192.9.113.13 20 32768 ?
*>i192.9.146.0 172.9.0.15 20 100 0 ?
*>i192.9.156.0 172.9.0.15 0 100 0 ?
R11#ping vrf XYZ 192.9.0.11 r 1

!
R11#ping vrf XYZ 192.9.0.12 r 1
!
R11#ping vrf XYZ 192.9.0.13 r 1
!
R11#ping vrf XYZ 192.9.0.14 r 1

!
R11#ping vrf XYZ 192.9.0.15 r 1

!
R11#ping vrf XYZ 192.9.0.16 r 1

!
R12 has no VPNv4 table, all VRF’s XYZ routes derived from IS-IS, there is no BGP VPNv4 session
between R12 and any other router from AS112.
---------------===========EMPTY===========----------------
R12#sh ip route vrf XYZ

Routing Table: XYZ
114
192.9.0.0/32 is subnetted, 6 subnets
i L2 192.9.0.11 [115/30] via 192.9.123.13, 1d19h, Ethernet0/0
C 192.9.0.12 is directly connected, Loopback1
i L2 192.9.113.0/24 [115/20] via 192.9.123.13, 1d19h, Ethernet0/0
R12#ping vrf XYZ 192.9.0.11 r 1

!
R12#ping vrf XYZ 192.9.0.12 r 1
!
R12#ping vrf XYZ 192.9.0.13 r 1
!
R12#ping vrf XYZ 192.9.0.14 r 1
!
R12#ping vrf XYZ 192.9.0.15 r 1
!
R12#ping vrf XYZ 192.9.0.16 r 1
!
R13:
R13#sh ip route
115
R13#ping 192.9.0.11 r 1
!
R13#ping 192.9.0.12 r 1
!
R13#ping 192.9.0.13 r 1
!
R13#ping 192.9.0.14 r 1
!
R13#ping 192.9.0.15 r 1
!
R13#ping 192.9.0.16 r 1
!
XYZ Site 2 (R14, R15, R16)
R14:
R14 has no VPNv4 table, all VRF’s XYZ routes derived from IS-IS, there is no BGP VPNv4 session
Routing Table: XYZ


R14#ping vrf XYZ 192.9.0.11 r 1

!
116
R14#ping vrf XYZ 192.9.0.12 r 1
!
R14#ping vrf XYZ 192.9.0.13 r 1
!
R14#ping vrf XYZ 192.9.0.14 r 1
!
R14#ping vrf XYZ 192.9.0.15 r 1
!
R14#ping vrf XYZ 192.9.0.16 r 1
!
R15:

*>i192.9.0.11/32 172.9.0.11 0 100 0 ?
*>i192.9.0.12/32 172.9.0.11 30 100 0 ?
*>i192.9.0.13/32 172.9.0.11 20 100 0 ?
*> 192.9.0.14/32 192.9.156.16 30 32768 ?
*> 192.9.0.15/32 0.0.0.0 0 32768 ?
*> 192.9.0.16/32 192.9.156.16 20 32768 ?
*>i192.9.113.0 172.9.0.11 0 100 0 ?
*>i192.9.123.0 172.9.0.11 20 100 0 ?
*> 192.9.146.0 192.9.156.16 20 32768 ?
*> 192.9.156.0 0.0.0.0 0 32768 ?
R15#ping vrf XYZ 192.9.0.11 r 1
!
R15#ping vrf XYZ 192.9.0.12 r 1
!
R15#ping vrf XYZ 192.9.0.13 r 1
!
R15#ping vrf XYZ 192.9.0.14 r 1
!
R15#ping vrf XYZ 192.9.0.15 r 1
!
R15#ping vrf XYZ 192.9.0.16 r 1
!
117
R16:
R16#sh ip route


R16#ping 192.9.0.11 r 1
!
R16#ping 192.9.0.12 r 1
!
R16#ping 192.9.0.13 r 1
!
R16#ping 192.9.0.14 r 1
!
R16#ping 192.9.0.15 r 1
!
R16#ping 192.9.0.16 r 1
!
R4: CsC-PE1
- With static route to the far end of the link between R4 and R11 via Gi0/0/0/3 in vrf ABC
RP/0/0/CPU0:R4#sh mpls forwarding vrf ABC

Sun Jan 20 12:01:07.956 MSK
------ ----------- ------------------ ------------ --------------- ------------
46013 Aggregate No ID Gi0/0/0/3 172.9.114.4 0
46014 36022 172.9.0.14/32[V] 9.9.0.3 0
46015 26019 172.9.0.2/32[V] 9.9.0.2 0
46016 36013 172.9.0.3/32[V] 9.9.0.3 0
118
ABC 0
46018 7020 172.9.0.7/32[V] 9.9.0.7 0
46019 8039 172.9.0.8/32[V] 9.9.0.8 0
46020 Pop 172.9.0.11/32[V] Gi0/0/0/3 172.9.114.11 950149
46021 8026 172.9.0.12/32[V] 9.9.0.8 0
46022 Pop 172.9.112.0/24[V] Gi0/0/0/3 172.9.114.11 0
46023 8002 172.9.128.0/24[V] 9.9.0.8 0
46024 36024 172.9.0.15/32[V] 9.9.0.3 312432
46025 36025 172.9.143.0/24[V] 9.9.0.3 0
46026 36026 172.9.145.0/24[V] 9.9.0.3 0
46027 36027 172.9.157.0/24[V] 9.9.0.3 0
46028 26040 172.9.0.1/32[V] 9.9.0.2 0
46029 26041 172.9.0.9/32[V] 9.9.0.2 0
46030 26042 172.9.0.10/32[V] 9.9.0.2 0
46031 26043 172.9.0.17/32[V] 9.9.0.2 965886
46032 26044 172.9.0.18/32[V] 9.9.0.2 0
46033 26045 172.9.108.0/24[V] 9.9.0.2 0
46034 26046 172.9.178.0/24[V] 9.9.0.2 0
46035 26047 172.9.197.0/24[V] 9.9.0.2 0
46036 Pop 172.9.114.11/32[V] Gi0/0/0/3 172.9.114.11 87495642
- Without static route to the far end of the link between R4 and R11 via Gi0/0/0/3 in vrf ABC

Sun Jan 20 12:03:16.969 MSK
------ ----------- ------------------ ------------ --------------- ------------
46013 Aggregate 172.9.114.0/24[V] ABC 0
46014 36022 172.9.0.14/32[V] 9.9.0.3 0
46015 26019 172.9.0.2/32[V] 9.9.0.2 0
46016 36013 172.9.0.3/32[V] 9.9.0.3 0
ABC 0
46018 7020 172.9.0.7/32[V] 9.9.0.7 0
46019 8039 172.9.0.8/32[V] 9.9.0.8 0
46020 Pop 172.9.0.11/32[V] 172.9.114.11 950873
46021 8026 172.9.0.12/32[V] 9.9.0.8 0
46022 Pop 172.9.112.0/24[V] 172.9.114.11 0
46023 8002 172.9.128.0/24[V] 9.9.0.8 0
46024 36024 172.9.0.15/32[V] 9.9.0.3 312650
46025 36025 172.9.143.0/24[V] 9.9.0.3 0
46026 36026 172.9.145.0/24[V] 9.9.0.3 0
46027 36027 172.9.157.0/24[V] 9.9.0.3 0
46028 26040 172.9.0.1/32[V] 9.9.0.2 0
46029 26041 172.9.0.9/32[V] 9.9.0.2 0
46030 26042 172.9.0.10/32[V] 9.9.0.2 0
46031 26043 172.9.0.17/32[V] 9.9.0.2 966510
46032 26044 172.9.0.18/32[V] 9.9.0.2 0
46033 26045 172.9.108.0/24[V] 9.9.0.2 0
46034 26046 172.9.178.0/24[V] 9.9.0.2 0
46035 26047 172.9.197.0/24[V] 9.9.0.2 0
R3: CsC-PE2
- With static route to the far end of the link between R3 and R14 via Gi0/0/0/4 in vrf ABC
Sun Jan 20 11:53:31.589 MSK
------ ----------- ------------------ ------------ --------------- ------------
36012 26019 172.9.0.2/32[V] 9.9.0.2 0
ABC 1560
36014 7020 172.9.0.7/32[V] 9.9.0.7 0
36015 8039 172.9.0.8/32[V] 9.9.0.8 0
36016 46020 172.9.0.11/32[V] 9.9.0.4 309428
36017 8026 172.9.0.12/32[V] 9.9.0.8 208
36018 46022 172.9.112.0/24[V] 9.9.0.4 0
36019 8002 172.9.128.0/24[V] 9.9.0.8 208
ABC 1248
36021 46013 172.9.114.0/24[V] 9.9.0.4 520
36022 Pop 172.9.0.14/32[V] Gi0/0/0/4 172.9.143.14 0
36023 46017 172.9.0.4/32[V] 9.9.0.4 0
36024 14000 172.9.0.15/32[V] Gi0/0/0/4 172.9.143.14 296839
36025 Aggregate No ID Gi0/0/0/4 172.9.143.3 0
36026 Pop 172.9.145.0/24[V] Gi0/0/0/4 172.9.143.14 0
119
36027 14001 172.9.157.0/24[V] Gi0/0/0/4 172.9.143.14 0
36028 Unlabelled 2002:172:9::14/128[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
300
36029 26040 172.9.0.1/32[V] 9.9.0.2 0
36030 Unlabelled 2002:172:9:145::/64[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
700
36031 Unlabelled 2002:172:9::15/128[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
300
36032 26041 172.9.0.9/32[V] 9.9.0.2 0
36033 26042 172.9.0.10/32[V] 9.9.0.2 0
36034 26043 172.9.0.17/32[V] 9.9.0.2 0
36035 26044 172.9.0.18/32[V] 9.9.0.2 0
36036 26045 172.9.108.0/24[V] 9.9.0.2 0
36037 26046 172.9.178.0/24[V] 9.9.0.2 0
36038 26047 172.9.197.0/24[V] 9.9.0.2 0
36039 Pop 172.9.143.14/32[V] Gi0/0/0/4 172.9.143.14 6567576
- Without static route to the far end of the link between R3 and R14 via Gi0/0/0/4 in vrf ABC
Sun Jan 20 11:54:48.814 MSK

------ ----------- ------------------ ------------ --------------- ------------
36012 26019 172.9.0.2/32[V] 9.9.0.2 0
ABC 1560
36014 7020 172.9.0.7/32[V] 9.9.0.7 0
36015 8039 172.9.0.8/32[V] 9.9.0.8 0
36016 46020 172.9.0.11/32[V] 9.9.0.4 309600
36017 8026 172.9.0.12/32[V] 9.9.0.8 208
36018 46022 172.9.112.0/24[V] 9.9.0.4 0
36019 8002 172.9.128.0/24[V] 9.9.0.8 208
ABC 1248
36021 46013 172.9.114.0/24[V] 9.9.0.4 520
36022 Pop 172.9.0.14/32[V] 172.9.143.14 0
36023 46017 172.9.0.4/32[V] 9.9.0.4 0
36024 14000 172.9.0.15/32[V] 172.9.143.14 296994
36025 Aggregate 172.9.143.0/24[V] ABC 0
36026 Pop 172.9.145.0/24[V] 172.9.143.14 0
36027 14001 172.9.157.0/24[V] 172.9.143.14 0
36028 Unlabelled 2002:172:9::14/128[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
300
36029 26040 172.9.0.1/32[V] 9.9.0.2 0
36030 Unlabelled 2002:172:9:145::/64[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
700
36031 Unlabelled 2002:172:9::15/128[V] \
Gi0/0/0/4 fe80::a8bb:ccff:fe00:7210 \
300
36032 26041 172.9.0.9/32[V] 9.9.0.2 0
36033 26042 172.9.0.10/32[V] 9.9.0.2 0
36034 26043 172.9.0.17/32[V] 9.9.0.2 0
36035 26044 172.9.0.18/32[V] 9.9.0.2 0
36036 26045 172.9.108.0/24[V] 9.9.0.2 0
36037 26046 172.9.178.0/24[V] 9.9.0.2 0
36038 26047 172.9.197.0/24[V] 9.9.0.2 0
3.8 CARRIER SUPPORTING CARRIER - 2
 Configure R9, R10, R17 and R18 so that AS178 is able to deliver MPLS VPNv4 service.
 The XYZ Company at Site3 uses OSPF for connection to the SP routers R17 and R18
 Configure OSPF on the interfaces that are shown in this table.

R17 0 Loopback1
0 E0/2
R18 0 Loopback1
0 E0/2
120
R19 0 Loopback0
0 E0/0
0 E0/1
 Establish BGP VPNv4 unicast session between R11 and R17.

 Only the import RT method can be used to control VPNv4 route distribution
 Ensure that routers on XYZ at Site1, Site2 and Site3 can ping each over via IPv4
SOLUTION:
ABC Site 3 (R17, R18, R19)
R17: AS178 PE1 R18: AS178 PE2

vrf definition XYZ
rd 178:178 vrf definition XYZ
! rd 178:178
route-target export 178:178 address-family ipv4
route-target import 178:178 route-target export 178:178
! !
! !
mpls ip mpls ip
! !
mpls ip mpls ip
! !
description Link to R19 E0/0 description Link to R19 e0/1
! !
router eigrp 100 router eigrp 100
network 172.9.0.17 0.0.0.0 network 172.9.0.18 0.0.0.0
network 172.9.178.17 0.0.0.0 network 172.9.108.18 0.0.0.0 ! Link to R10 vrf ABC
network 172.9.197.17 0.0.0.0 ! Link to R9 vrf ABC network 172.9.178.18 0.0.0.0
! !
router ospf 178 vrf XYZ router ospf 178 vrf XYZ
redistribute bgp 178 subnets domain-tag 178
! !
router bgp 178
neighbor 172.9.0.11 ebgp-multihop 255
!
exit-address-family
!
address-family ipv4 vrf XYZ
exit-address-family
!
121
R19: AS178 CE
interface Loopback0
ip address 192.9.0.19 255.255.255.255
!
description Link to R17 e0/2
ip address 192.9.179.19 255.255.255.0
!
description Link to R18 e0/2
ip address 192.9.189.19 255.255.255.0
!
router ospf 178
passive-interface Loopback0
network 192.9.0.19 0.0.0.0 area 0
network 192.9.179.19 0.0.0.0 area 0
network 192.9.189.19 0.0.0.0 area 0
ABC Site 1 (R11, R12, R13)
R11: ABC Site 1 PE1 R12: ABC Site1 PE2
vrf definition XYZ

rd 112:112 Nothing is required to configure here
!
address-family ipv4
route-target export 112:112
exit-address-family
!
router bgp 112
neighbor 172.9.0.17 ebgp-multihop 255
!
neighbor 172.9.0.17 next-hop-unchanged
exit-address-family
!
AS1009
R9: AS1009 PE (facing to R17) R10: AS1009 PE (facing to R18)

mpls ip mpls ip
Note: Connection between AS1009 and AS178 is done using LDP+IGP, so no BGP configuration
required for it.
122
VALIDATION:
XYZ Site 3 (R17, R18, R19)
R17: XYZ Site 3 AS178 PE1

*> 192.9.0.11/32 172.9.0.11 0 0 112 ?
*> 192.9.0.12/32 172.9.0.11 30 0 112 ?
*> 192.9.0.13/32 172.9.0.11 20 0 112 ?
*> 192.9.0.14/32 172.9.0.15 0 112 ?
*> 192.9.0.15/32 172.9.0.15 0 112 ?
*> 192.9.0.16/32 172.9.0.15 0 112 ?
*> 192.9.0.17/32 0.0.0.0 0 32768 ?
*> 192.9.0.18/32 192.9.179.19 21 32768 ?
*> 192.9.0.19/32 192.9.179.19 11 32768 ?
*> 192.9.113.0 172.9.0.11 0 0 112 ?
*> 192.9.123.0 172.9.0.11 20 0 112 ?
*> 192.9.146.0 172.9.0.15 0 112 ?
*> 192.9.156.0 172.9.0.15 0 112 ?
*> 192.9.179.0 0.0.0.0 0 32768 ?
*> 192.9.189.0 192.9.179.19 20 32768 ?
R17#ping vrf XYZ 192.9.0.11 r 1
!
R17#ping vrf XYZ 192.9.0.12 r 1
!
R17#ping vrf XYZ 192.9.0.13 r 1
!
R17#ping vrf XYZ 192.9.0.14 r 1
!
R17#ping vrf XYZ 192.9.0.15 r 1
!
R17#ping vrf XYZ 192.9.0.16 r 1
!
R17#ping vrf XYZ 192.9.0.17 r 1
!
R17#ping vrf XYZ 192.9.0.18 r 1
!
R17#ping vrf XYZ 192.9.0.19 r 1
!
123
R18 has no VPNv4 table, all VRF’s XYZ routes derived from OSPF, there is no BGP VPNv4 session
Routing Table: XYZ
O E2 192.9.0.11 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.0.12 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.0.13 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.0.14 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.0.15 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.0.16 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O 192.9.0.17 [110/21] via 192.9.189.19, 01:52:31, Ethernet0/2
O 192.9.0.19 [110/11] via 192.9.189.19, 01:52:31, Ethernet0/2
O E2 192.9.113.0/24 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.123.0/24 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.146.0/24 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O E2 192.9.156.0/24 [110/1] via 192.9.189.19, 01:22:46, Ethernet0/2
O 192.9.179.0/24 [110/20] via 192.9.189.19, 01:52:31, Ethernet0/2
R18#ping vrf XYZ 192.9.0.11 r 1
!
R18#ping vrf XYZ 192.9.0.12 r 1

!
R18#ping vrf XYZ 192.9.0.13 r 1

!
R18#ping vrf XYZ 192.9.0.14 r 1

!
R18#ping vrf XYZ 192.9.0.15 r 1

!
R18#ping vrf XYZ 192.9.0.16 r 1

!
R18#ping vrf XYZ 192.9.0.17 r 1

!
R18#ping vrf XYZ 192.9.0.18 r 1
!
124
R18#ping vrf XYZ 192.9.0.19 r 1
!
R19: XYZ Site 3 AS178 CE
R19#sh ip route
O E2 192.9.0.11 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.0.12 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.0.13 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.0.14 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.0.15 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.0.16 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O 192.9.0.17 [110/11] via 192.9.179.17, 01:57:52, Ethernet0/0
O 192.9.0.18 [110/11] via 192.9.189.18, 01:57:37, Ethernet0/1
O E2 192.9.113.0/24 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.123.0/24 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.146.0/24 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
O E2 192.9.156.0/24 [110/1] via 192.9.179.17, 01:27:51, Ethernet0/0
R19#ping 192.9.0.11 r 1
!
R19#ping 192.9.0.12 r 1
!
R19#ping 192.9.0.13 r 1
!
R19#ping 192.9.0.14 r 1
!
R19#ping 192.9.0.15 r 1
!
R19#ping 192.9.0.16 r 1
!
R19#ping 192.9.0.17 r 1
!
R19#ping 192.9.0.18 r 1
!
125
R19#ping 192.9.0.19 r 1
!
XYZ Site 1 (R11, R12, R13)

*> 192.9.0.11/32 0.0.0.0 0 32768 ?
*> 192.9.0.12/32 192.9.113.13 30 32768 ?
*> 192.9.0.13/32 192.9.113.13 20 32768 ?
*>i192.9.0.14/32 172.9.0.15 30 100 0 ?
*>i192.9.0.15/32 172.9.0.15 0 100 0 ?
*>i192.9.0.16/32 172.9.0.15 20 100 0 ?
*> 192.9.0.17/32 172.9.0.17 0 0 178 ?
*> 192.9.0.18/32 172.9.0.17 21 0 178 ?
*> 192.9.0.19/32 172.9.0.17 11 0 178 ?
*> 192.9.113.0 0.0.0.0 0 32768 ?
*> 192.9.123.0 192.9.113.13 20 32768 ?
*>i192.9.146.0 172.9.0.15 20 100 0 ?
*>i192.9.156.0 172.9.0.15 0 100 0 ?
*> 192.9.179.0 172.9.0.17 0 0 178 ?
*> 192.9.189.0 172.9.0.17 20 0 178 ?
R11#ping vrf XYZ 192.9.0.17 r 1

!
R11#ping vrf XYZ 192.9.0.18 r 1
!
R11#ping vrf XYZ 192.9.0.19 r 1
!
Note: Connectivity between XYZ Site 1 and 2 were checked in step 3.7

Note: R12 has no VPNv4 BGP table since there is no VPNv4 sessions with any other routers

Routing Table: XYZ
126

i L2 192.9.0.14 [115/20] via 192.9.123.13, 02:22:48, Ethernet0/0
i L2 192.9.0.15 [115/20] via 192.9.123.13, 02:22:48, Ethernet0/0
i L2 192.9.0.16 [115/20] via 192.9.123.13, 02:22:48, Ethernet0/0
i L2 192.9.0.17 [115/20] via 192.9.123.13, 01:41:28, Ethernet0/0
i L2 192.9.0.18 [115/20] via 192.9.123.13, 01:41:28, Ethernet0/0
i L2 192.9.0.19 [115/20] via 192.9.123.13, 01:41:28, Ethernet0/0
i L2 192.9.146.0/24 [115/20] via 192.9.123.13, 02:22:48, Ethernet0/0
i L2 192.9.156.0/24 [115/20] via 192.9.123.13, 02:22:48, Ethernet0/0
i L2 192.9.179.0/24 [115/20] via 192.9.123.13, 01:41:28, Ethernet0/0
i L2 192.9.189.0/24 [115/20] via 192.9.123.13, 01:41:28, Ethernet0/0
R12#ping vrf XYZ 192.9.0.17 r 1
!
R12#ping vrf XYZ 192.9.0.18 r 1
!
R12#ping vrf XYZ 192.9.0.19 r 1
!

R13#sh ip route
i L2 192.9.0.14 [115/10] via 192.9.113.11, 02:28:04, Ethernet0/0
i L2 192.9.0.15 [115/10] via 192.9.113.11, 02:28:04, Ethernet0/0
i L2 192.9.0.16 [115/10] via 192.9.113.11, 02:28:04, Ethernet0/0
i L2 192.9.0.17 [115/10] via 192.9.113.11, 01:46:44, Ethernet0/0
i L2 192.9.0.18 [115/10] via 192.9.113.11, 01:46:44, Ethernet0/0
i L2 192.9.0.19 [115/10] via 192.9.113.11, 01:46:44, Ethernet0/0
i L2 192.9.146.0/24 [115/10] via 192.9.113.11, 02:28:04, Ethernet0/0
i L2 192.9.156.0/24 [115/10] via 192.9.113.11, 02:28:04, Ethernet0/0
i L2 192.9.179.0/24 [115/10] via 192.9.113.11, 01:46:44, Ethernet0/0
i L2 192.9.189.0/24 [115/10] via 192.9.113.11, 01:46:44, Ethernet0/0
R13#ping 192.9.0.17 r 1
!
R13#ping 192.9.0.18 r 1
!
127
R13#ping 192.9.0.19 r 1
!
XYZ Site 2 (R14, R15, R16)

Note: R14 has no VPNv4 BGP table since there is no VPNv4 sessions with any other routers
Routing Table: XYZ
i L2 192.9.0.11 [115/20] via 192.9.146.16, 02:31:25, Ethernet0/0
i L2 192.9.0.12 [115/20] via 192.9.146.16, 02:31:25, Ethernet0/0
i L2 192.9.0.13 [115/20] via 192.9.146.16, 02:31:25, Ethernet0/0
i L2 192.9.0.17 [115/20] via 192.9.146.16, 01:50:05, Ethernet0/0
i L2 192.9.0.18 [115/20] via 192.9.146.16, 01:50:05, Ethernet0/0
i L2 192.9.0.19 [115/20] via 192.9.146.16, 01:50:05, Ethernet0/0
i L2 192.9.113.0/24 [115/20] via 192.9.146.16, 02:31:25, Ethernet0/0
i L2 192.9.123.0/24 [115/20] via 192.9.146.16, 02:31:25, Ethernet0/0
i L2 192.9.179.0/24 [115/20] via 192.9.146.16, 01:50:05, Ethernet0/0
i L2 192.9.189.0/24 [115/20] via 192.9.146.16, 01:50:05, Ethernet0/0
R14#ping vrf XYZ 192.9.0.17 r 1
!
R14#ping vrf XYZ 192.9.0.18 r 1

!
R14#ping vrf XYZ 192.9.0.19 r 1

!

128
*>i192.9.0.11/32 172.9.0.11 0 100 0 ?
*>i192.9.0.12/32 172.9.0.11 30 100 0 ?
*>i192.9.0.13/32 172.9.0.11 20 100 0 ?
*> 192.9.0.14/32 192.9.156.16 30 32768 ?
*> 192.9.0.15/32 0.0.0.0 0 32768 ?
*> 192.9.0.16/32 192.9.156.16 20 32768 ?
*>i192.9.0.17/32 172.9.0.17 0 100 0 178 ?
*>i192.9.0.18/32 172.9.0.17 21 100 0 178 ?
*>i192.9.0.19/32 172.9.0.17 11 100 0 178 ?
*>i192.9.113.0 172.9.0.11 0 100 0 ?
*>i192.9.123.0 172.9.0.11 20 100 0 ?
*> 192.9.146.0 192.9.156.16 20 32768 ?
*> 192.9.156.0 0.0.0.0 0 32768 ?
*>i192.9.179.0 172.9.0.17 0 100 0 178 ?
*>i192.9.189.0 172.9.0.17 20 100 0 178 ?
R15# ping vrf XYZ 192.9.0.17 r 1
!
R15# ping vrf XYZ 192.9.0.18 r 1
!
R15# ping vrf XYZ 192.9.0.19 r 1
!

R16#sh ip route
i L2 192.9.0.11 [115/10] via 192.9.156.15, 02:43:29, Ethernet0/1
i L2 192.9.0.12 [115/10] via 192.9.156.15, 02:43:29, Ethernet0/1
i L2 192.9.0.13 [115/10] via 192.9.156.15, 02:43:29, Ethernet0/1
i L2 192.9.0.17 [115/10] via 192.9.156.15, 02:02:08, Ethernet0/1
i L2 192.9.0.18 [115/10] via 192.9.156.15, 02:02:08, Ethernet0/1
i L2 192.9.0.19 [115/10] via 192.9.156.15, 02:02:08, Ethernet0/1
i L2 192.9.113.0/24 [115/10] via 192.9.156.15, 02:43:29, Ethernet0/1
i L2 192.9.123.0/24 [115/10] via 192.9.156.15, 02:43:29, Ethernet0/1
i L2 192.9.179.0/24 [115/10] via 192.9.156.15, 02:02:08, Ethernet0/1
i L2 192.9.189.0/24 [115/10] via 192.9.156.15, 02:02:08, Ethernet0/1
R16#ping 192.9.0.17
!!!!!
129
R16#ping 192.9.0.18
!!!!!
R16#ping 192.9.0.19
!!!!!
3.9 INTRA AS MULTICAST VPN
The routers in VPN ABC Site1 and Site2 have been configured PIM-SM on the interfaces shown in the
Table 16.
Table 16: PIM-SM interfaces in VRF ABC Site 1 and 2
Router Interface
R4 Loopback1
GE0/0/0/3
R8 Loopback1
E0/0
R11 Loopback0
E0/1
E0/2
R12 Loopback0
E0/1
E0/2
R3 Loopback1
GE0/0/0/4
R7 Loopback1
E0/0
R14 Loopback0
E0/1
E0/2
R15 Loopback0
E0/1
E0/2
 Statically define the IPv4 address of interface Loopback0 on R11 as the RP.
 Multicast group addresses have been configured on Loopback0 of R11, R12, R14 and R15 (see
Table 17 for details).
Table 17: VRF ABC Loopback interfaces Multicast Group
Router Interface IPv4 Multicast Group

R11 Loopback0 239.255.172.11
R12 Loopback0 239.255.172.12
R13 Loopback0 239.255.172.13
R14 Loopback0 239.255.172.14
R15 Loopback0 239.255.172.15
130
 Configure R3, R4, R7, and R8 so that they support Multicast VPN. Use the 239.255.13.27 address
for vrf ABC mdt default group address.
 Ensure that R11, R12, R14 and R15 can ping these group addresses.
SOLUTION:
AS9 PEs: (R3, R4, R7, R8)
R3: R4:
multicast-routing multicast-routing
! !
mdt source Loopback0 mdt source Loopback0
! !
vrf ABC vrf ABC
enable enable
! !
enable enable
! !
mdt default ipv4 239.255.13.27 mdt default ipv4 239.255.13.27
! !
! !
! !
router pim router pim
! !
vrf ABC vrf ABC
rp-address 172.9.0.11 rp-address 172.9.0.11
enable enable
! !
enable enable
! !
! !
! !
! !
R7: R8:

! !
mdt default 239.255.13.27 mdt default 239.255.13.27
! !
ip multicast-routing vrf ABC ip multicast-routing vrf ABC
! !
! !
! !
ip pim vrf ABC rp-address 172.9.0.11 ip pim vrf ABC rp-address 172.9.0.11
! !
131
AS9 CEs: (R11, R12, R14, R15)
R11: R12:
! !
ip igmp join-group 239.255.172.11 ip pim sparse-mode
ip pim sparse-mode ip igmp join-group 239.255.172.12
! !
! !
! !
! ip pim rp-address 172.9.0.11
ip pim rp-address 172.9.0.11 !
!
R14: R15:
ip multicast-routing
! ip multicast-routing
ip address 172.9.0.14 255.255.255.255 interface Loopback0
ip pim sparse-mode ip address 172.9.0.15 255.255.255.255
ip igmp join-group 239.255.172.14 ip pim sparse-mode
! ip igmp join-group 239.255.172.15
description Link to R3 Gi0/0/0/1 interface Ethernet0/1
ip pim rp-address 172.9.0.11 !
! ip pim rp-address 172.9.0.11
!
VALIDATION:
R11:
PIM Neighbor Table
Address Prio/Mode
172.9.114.4 Ethernet0/1 1d10h/00:01:27 v2 1 / G
R11#ping 239.255.172.11

R11#ping 239.255.172.12
132
R11#ping 239.255.172.14
R11#ping 239.255.172.15

R12:
PIM Neighbor Table
Address Prio/Mode
172.9.128.8 Ethernet0/1 1d10h/00:01:31 v2 1 / S P G
172.9.112.11 Ethernet0/2 1d10h/00:01:30 v2 1 / S P G
R12#ping 239.255.172.11

R12#ping 239.255.172.12

R12#ping 239.255.172.14
R12#ping 239.255.172.15
R14:
PIM Neighbor Table
Address Prio/Mode
172.9.143.3 Ethernet0/1 1d10h/00:01:39 v2 1 / G
R14#ping 239.255.172.11
R14#ping 239.255.172.12
R14#ping 239.255.172.14

R14#ping 239.255.172.15
133


PIM Neighbor Table
Address Prio/Mode
172.9.157.7 Ethernet0/1 1d10h/00:01:16 v2 1 / S P G
172.9.145.14 Ethernet0/2 1d10h/00:01:20 v2 1 / S P G
R15#ping 239.255.172.11
R15#ping 239.255.172.12
R15#ping 239.255.172.14
R15#ping 239.255.172.15

3.10 BGP IPV4 MDT
Configure BGP IPv4 MDT in AS-9 and AS-1009
 R5 act as RR for iBGP IPv4 MDT within AS-9. An iBGP MDT session should NOT be established
between R2, R3, R4, R7 and R8.
 R6 act as RR for iBGP IPv4 MDT within AS-1009. An iBGP MDT session should NOT be established
between R1, R9 and R10.
 The IPv4 addresses of interface Loopback0 is used to establish BGP ipv4 MDT sessions.
 Establish eBGP IPv4 MDT session between R5 and R6.
 Ensure that R1, R6, R9 and R10 have the information about PE source and the default MDT
group of R3, R4, R7 and R8.
SOLUTION:
AS9: (R3, R4, R7, R8, R5 - RR)
R3: R4:
vrf ABC vrf ABC
import route-target import route-target
9:9 9:9
1009:9 1009:9
! !
export route-target export route-target
9:9 9:9
! !
134
! !
import route-target router bgp 9
9:9 !
1009:9 address-family ipv4 mdt
! !
export route-target neighbor 9.9.0.5 ! AS9 Route Reflector
9:9 remote-as 9
! update-source Loopback0
! !
! address-family ipv4 mdt
router bgp 9 !
! !
address-family ipv4 mdt router bgp 9
! !
neighbor 9.9.0.5 ! AS9 Route Reflector address-family ipv4 mdt
remote-as 9 !
update-source Loopback0 neighbor 9.9.0.5 ! AS9 Route Reflector
! remote-as 9
address-family ipv4 mdt update-source Loopback0
! !
multicast-routing !
! multicast-routing
mdt source Loopback0 address-family ipv4
! !
vrf ABC mdt source Loopback0
interface Loopback1 vrf ABC
enable address-family ipv4
enable !
mdt default ipv4 239.255.13.27 enable
! !
! mdt default ipv4 239.255.13.27
! !
router pim !
rpf-vector router pim
vrf ABC rpf-vector
rp-address 172.9.0.11 vrf ABC
interface Loopback1 address-family ipv4
enable rp-address 172.9.0.11
enable !
! enable
! !
! !
!
!
R7: R8:

rd 9:9 rd 9:9
! !
! !
ip multicast rpf proxy vector ip multicast rpf proxy vector
ip multicast vrf ABC rpf proxy rd vector ip multicast vrf ABC rpf proxy rd vector
! !
! !
! !
neighbor 9.9.0.5 remote-as 9 ! AS9 RR neighbor 9.9.0.5 remote-as 9 ! AS9 RR
135
! !
address-family ipv4 mdt address-family ipv4 mdt
! !
R5:
router bgp 9
!
!
address-family ipv4 mdt
neighbor 9.9.0.3 route-reflector-client
exit-address-family
AS1009: (R1, R6-RR, R9, R10)
R9: R10:
rd 1009:9 rd 1009:9
! !
! !
ip multicast rpf proxy vector ip multicast rpf proxy vector
ip multicast vrf ABC rpf proxy rd vector ip multicast vrf ABC rpf proxy rd vector
! !
! !
! !
! !
neighbor 9.9.0.6 remote-as 1009 ! AS1009 RR neighbor 9.9.0.6 remote-as 1009 ! AS1009 RR
! !
address-family ipv4 mdt address-family ipv4 mdt
136
! !
! !
R1: R6:
router bgp 1009
vrf ABC !
9:9 neighbor 9.9.0.9 remote-as 1009
1009:9 neighbor 9.9.0.9 update-source Loopback0
export route-target neighbor 9.9.0.10 update-source Loopback0
1009:9 neighbor 9.9.56.5 remote-as 9
! !
address-family ipv6 unicast neighbor 9.9.0.1 activate
import route-target neighbor 9.9.0.1 route-reflector-client
9:9 neighbor 9.9.0.1 next-hop-self
1009:9 neighbor 9.9.0.9 activate
export route-target neighbor 9.9.0.9 next-hop-self
1009:9 neighbor 9.9.0.10 activate
! neighbor 9.9.0.10 next-hop-self
! neighbor 9.9.56.5 activate
router bgp 1009 neighbor 9.9.56.5 send-community extended
address-family ipv4 mdt !
!
neighbor 9.9.0.6 ! AS1009 RR
remote-as 1009
!
address-family ipv4 mdt
!
!
!
multicast-routing
address-family ipv4
!
mdt source Loopback0
!
vrf ABC
address-family ipv4
interface Loopback1
enable
!
mdt default ipv4 239.255.13.27
!
!
!
router pim
address-family ipv4
rpf-vector
!
vrf ABC
address-family ipv4
rp-address 172.9.0.11
interface Loopback1
!
!
!
VALIDATION:
{----------------------------------------------AS9---------------------------------------------}
R7:
R7#sh ip pim vrf ABC neighbor
PIM Neighbor Table

Address Prio/Mode
137
9.9.0.10 Tunnel1 02:00:31/00:01:41 v2 1 / DR S P G
9.9.0.9 Tunnel1 02:00:32/00:01:43 v2 1 / S P G
9.9.0.1 Tunnel1 02:01:26/00:01:20 v2 1 / G
9.9.0.3 Tunnel1 2d07h/00:01:25 v2 1 / G
9.9.0.4 Tunnel1 2d07h/00:01:42 v2 1 / G
9.9.0.8 Tunnel1 2d07h/00:01:15 v2 1 / S P G
R7#sh bgp ipv4 mdt all
*>i9.9.0.3/32 9.9.0.3 100 0 i
*>i9.9.0.4/32 9.9.0.4 100 0 i
*> 9.9.0.7/32 0.0.0.0 0 ?
*>i9.9.0.8/32 9.9.0.8 0 100 0 ?
Route Distinguisher: 1009:9
*>i9.9.0.1/32 9.9.0.5 0 100 0 1009 i
*>i9.9.0.9/32 9.9.0.5 0 100 0 1009 ?
*>i9.9.0.10/32 9.9.0.5 0 100 0 1009 ?
In the real lab environment it is also required to check the reachability of the VRF’s ABC multicast
groups via ping.
R7#ping vrf ABC 239.255.172.11
R7#ping vrf ABC 239.255.172.12
R7#ping vrf ABC 239.255.172.14

R7#ping vrf ABC 239.255.172.15
R8:
PIM Neighbor Table
Address Prio/Mode
9.9.0.10 Tunnel1 02:16:27/00:01:31 v2 1 / DR S P G
9.9.0.9 Tunnel1 02:16:28/00:01:34 v2 1 / S P G
9.9.0.1 Tunnel1 02:17:22/00:01:28 v2 1 / G
9.9.0.3 Tunnel1 2d08h/00:01:33 v2 1 / G
9.9.0.4 Tunnel1 2d08h/00:01:19 v2 1 / G
9.9.0.7 Tunnel1 2d08h/00:01:36 v2 1 / S P G

*>i9.9.0.3/32 9.9.0.3 100 0 i
*>i9.9.0.4/32 9.9.0.4 100 0 i
*>i9.9.0.7/32 9.9.0.7 0 100 0 ?
*> 9.9.0.8/32 0.0.0.0 0 ?
*>i9.9.0.1/32 9.9.0.5 0 100 0 1009 i
*>i9.9.0.9/32 9.9.0.5 0 100 0 1009 ?
*>i9.9.0.10/32 9.9.0.5 0 100 0 1009 ?
R8#ping vrf ABC 239.255.172.11

R8#ping vrf ABC 239.255.172.12
R8#ping vrf ABC 239.255.172.14
R8#ping vrf ABC 239.255.172.15
138
R3:
RP/0/0/CPU0:R3#sh pim vrf ABC neighbor
Wed Jan 23 23:29:51.600 MSK
PIM neighbors in VRF ABC

9.9.0.1 mdtABC 02:27:01 00:01:20 1
9.9.0.3* mdtABC 2d08h 00:01:25 1
9.9.0.4 mdtABC 2d08h 00:01:42 1
9.9.0.7 mdtABC 2d08h 00:01:17 1 P
9.9.0.8 mdtABC 2d08h 00:01:44 1 P
9.9.0.9 mdtABC 02:26:07 00:01:16 1 P
9.9.0.10 mdtABC 02:26:07 00:01:41 1 (DR) P
172.9.0.3* Loopback1 2d08h 00:01:36 1 (DR) B P
RP/0/0/CPU0:R3#sh bgp ipv4 mdt
Wed Jan 23 23:31:01.238 MSK

*> 9.9.0.3/96 0.0.0.0 0 i
*>i9.9.0.4/96 9.9.0.4 100 0 i
*>i9.9.0.7/96 9.9.0.7 0 100 0 ?
*>i9.9.0.8/96 9.9.0.8 0 100 0 ?
*>i9.9.0.1/96 9.9.0.5 0 100 0 1009 i
*>i9.9.0.9/96 9.9.0.5 0 100 0 1009 ?
*>i9.9.0.10/96 9.9.0.5 0 100 0 1009 ?
R3#ping vrf ABC 239.255.172.11
R3#ping vrf ABC 239.255.172.12

R3#ping vrf ABC 239.255.172.14
R3#ping vrf ABC 239.255.172.15
R4:
Wed Jan 23 23:43:44.121 MSK

9.9.0.1 mdtABC 02:40:54 00:01:30 1
9.9.0.3 mdtABC 2d08h 00:01:35 1
9.9.0.4* mdtABC 2d08h 00:01:22 1
9.9.0.7 mdtABC 2d08h 00:01:40 1 P
9.9.0.8 mdtABC 2d08h 00:01:35 1 P
9.9.0.9 mdtABC 02:40:00 00:01:41 1 P
9.9.0.10 mdtABC 02:40:00 00:01:36 1 (DR) P
172.9.0.4* Loopback1 2d08h 00:01:15 1 (DR) B P

Wed Jan 23 23:44:06.294 MSK
139
*>i9.9.0.3/96 9.9.0.3 100 0 i
*> 9.9.0.4/96 0.0.0.0 0 i
*>i9.9.0.7/96 9.9.0.7 0 100 0 ?
*>i9.9.0.8/96 9.9.0.8 0 100 0 ?
*>i9.9.0.1/96 9.9.0.5 0 100 0 1009 i
*>i9.9.0.9/96 9.9.0.5 0 100 0 1009 ?
*>i9.9.0.10/96 9.9.0.5 0 100 0 1009 ?
{----------------------------------------------AS1009---------------------------------------------}
R9:
PIM Neighbor Table

Address Prio/Mode
9.9.0.7 Tunnel1 00:40:39/00:01:29 v2 1 / S P G
9.9.0.4 Tunnel1 03:55:04/00:01:34 v2 1 / G
9.9.0.8 Tunnel1 03:55:10/00:01:23 v2 1 / S P G
9.9.0.3 Tunnel1 03:55:24/00:01:36 v2 1 / G

*>i9.9.0.3/32 9.9.0.6 0 100 0 9 i
*>i9.9.0.4/32 9.9.0.6 0 100 0 9 i
*>i9.9.0.7/32 9.9.0.6 0 100 0 9 ?
*>i9.9.0.8/32 9.9.0.6 0 100 0 9 ?
*>i9.9.0.1/32 9.9.0.1 100 0 i
*> 9.9.0.9/32 0.0.0.0 0 ?
* i9.9.0.10/32 9.9.0.10 0 100 0 ?
*>i 9.9.0.10 0 100 0 ?
R10:

PIM Neighbor Table
Address Prio/Mode
172.9.108.18 Ethernet0/2 08:13:48/00:01:30 v2 1 / DR S P G
9.9.0.7 Tunnel1 00:41:59/00:01:37 v2 1 / S P G
9.9.0.4 Tunnel1 03:56:25/00:01:44 v2 1 / G
9.9.0.8 Tunnel1 03:56:31/00:01:33 v2 1 / S P G
9.9.0.3 Tunnel1 03:56:45/00:01:16 v2 1 / G
*>i9.9.0.3/32 9.9.0.6 0 100 0 9 i
*>i9.9.0.4/32 9.9.0.6 0 100 0 9 i
*>i9.9.0.7/32 9.9.0.6 0 100 0 9 ?
*>i9.9.0.8/32 9.9.0.6 0 100 0 9 ?
*>i9.9.0.1/32 9.9.0.1 100 0 i
*>i9.9.0.9/32 9.9.0.9 0 100 0 ?
140
*> 9.9.0.10/32 0.0.0.0 0 ?
R1:

Thu Jan 24 01:02:39.292 MSK

172.9.0.1* Loopback1 11:55:25 00:01:27 1 (DR) B P
9.9.0.1* mdtABC 11:54:38 00:01:31 1
9.9.0.3 mdtABC 11:54:20 00:01:18 1
9.9.0.4 mdtABC 03:59:00 00:01:16 1
9.9.0.7 mdtABC 00:45:28 00:01:34 1 P
9.9.0.8 mdtABC 04:00:00 00:01:31 1 P
9.9.0.9 mdtABC 11:54:29 00:01:31 1 P
9.9.0.10 mdtABC 11:54:25 00:01:35 1 (DR) P
Thu Jan 24 01:04:31.525 MSK

*>i9.9.0.3/96 9.9.0.6 0 100 0 9 i
*>i9.9.0.4/96 9.9.0.6 0 100 0 9 i
*>i9.9.0.7/96 9.9.0.6 0 100 0 9 ?
*>i9.9.0.8/96 9.9.0.6 0 100 0 9 ?
*> 9.9.0.1/96 0.0.0.0 0 i
*>i9.9.0.9/96 9.9.0.9 0 100 0 ?
*>i9.9.0.10/96 9.9.0.10 0 100 0 ?
141
Section 4. Implement, Optimize and Troubleshooting L2 VPN Technologies
4.1 PPP OVER MPLS
 R22 and R23 would like to establish PPP connection through AS-9 (see Diagram #1 for details)
 Configure R5 and R8 to support PPP over MPLS
 Configure OSPF on the interfaces that are shown in this table

R22 0 Loopback0
0 S2/0
R23 0 Loopback0
0 S2/0
 Ensure that R22 and R23 have the OSPF routes and can ping each over via IPv4.
SOLUTION:
R22: R23:

! !
description PPP Link to R8 S2/0 description Link to R5 S2/1
no peer neighbor-route no peer neighbor-route
serial restart-delay 0 serial restart-delay 0
! !
router ospf 9 router ospf 9
passive-interface Loopback0 passive-interface Loopback0
! !
R8: R5:

! !
pseudowire-class AToM pseudowire-class AToM
encapsulation mpls encapsulation mpls
! !
no ip address no ip address
xconnect 9.9.0.5 100 encapsulation mpls pw- xconnect 9.9.0.8 100 encapsulation mpls pw-
class AToM class AToM
! !
142
VALIDATION:
R22:
R22#sh ip route

O 172.9.0.23/32 [110/65] via 172.9.223.23, 00:25:17, Serial2/0
C 172.9.223.0/24 is directly connected, Serial2/0
L 172.9.223.22/32 is directly connected, Serial2/0
R22#ping 172.9.0.23
!!!!!
R8:
R8#sh xconnect int s2/0

Legend: XC ST=Xconnect State S1=Segment1 State S2=Segment2 State
UP=Up DN=Down AD=Admin Down IA=Inactive
SB=Standby HS=Hot Standby RV=Recovering NH=No Hardware
XC ST Segment 1 S1 Segment 2 S2
------+---------------------------------+--+---------------------------------+--
UP pri ac Se2/0(PPP) UP mpls 9.9.0.5:100 UP
R5:
R5#sh xconnect int s2/1
------+---------------------------------+--+---------------------------------+--
UP pri ac Se2/1(PPP) UP mpls 9.9.0.8:100 UP
4.2 FRAME RELAY OVER L2TPV3
 R21 and R24 are connected to the SP using Frame-Relay. (See Diagrams #1 and #3 for details).
 Configure L2TPv3 on R7 and R9 to support Frame Relay tunneling.
 Configure RIPv2 and RIPng on the interfaces that are shown in this table.
Router Interface
R21 Loopback0
S2/0
R24 Loopback0
S2/0
 Ensure that R21 and R24 have full IPv4 and IPv6 connectivity.
143
SOLUTION:
R7: R9:
pseudowire-class L2TPV3 pseudowire-class L2TPV3

encapsulation l2tpv3 encapsulation l2tpv3
ip local interface Loopback0 ip local interface Loopback0
! !
description FR Link to R21 S2/0 via R28 S2/0 description FR Link to R24 S2/0 via R28 S2/1
no ip address no ip address
encapsulation frame-relay encapsulation frame-relay
no frame-relay inverse-arp no frame-relay inverse-arp
! !
connect FR-Link Serial2/0 721 l2transport connect FR-Link Serial2/0 924 l2transport
xconnect 9.9.0.9 10 encapsulation l2tpv3 pw- xconnect 9.9.0.7 10 encapsulation l2tpv3 pw-
class L2TPV3 class L2TPV3
! !
R21: R24:
interface Loopback0
ip address 172.9.0.21 255.255.255.255 ipv6 address 2002:172:9::24/128
ipv6 address 2002:172:9::21/128 ipv6 rip RIP enable
ipv6 rip RIP enable !
interface Serial2/0 description FR Link to R9 S2/0 via R28 S2/3
description FR Link to R9 S2/0 via R28 S2/3 ip address 172.9.214.24 255.255.255.0
ip address 172.9.214.21 255.255.255.0 encapsulation frame-relay
encapsulation frame-relay ipv6 address 2002:172:9:214::24/64
ipv6 address 2002:172:9:214::21/64 ipv6 rip RIP enable
ipv6 rip RIP enable serial restart-delay 0
serial restart-delay 0 frame-relay map ipv6 FE80::A8BB:CCFF:FE00:7900
frame-relay map ipv6 FE80::A8BB:CCFF:FE00:7C00 249 broadcast ! R21 (remote) Link-Local Address
217 broadcast ! R24 (remote) Link-Local Address frame-relay map ipv6 2002:172:9:214::21 249
frame-relay map ipv6 2002:172:9:214::24 217 broadcast
broadcast frame-relay map ip 172.9.214.21 249 broadcast
frame-relay map ip 172.9.214.24 217 broadcast no frame-relay inverse-arp
no frame-relay inverse-arp !
! router rip
router rip version 2
version 2 passive-interface default
passive-interface default no passive-interface Serial2/0
no passive-interface Serial2/0 network 172.9.0.0
network 172.9.0.0 no auto-summary
no auto-summary !
! ipv6 router rip RIP
ipv6 router rip RIP !
!
NB! Frame-relay map to remote Link-Local address is important, overwise remote loopback will not be
reachable via IPv6 ping.
VALIDATION:
R9:
R9#show xconnect all
------+---------------------------------+--+---------------------------------+--
UP ac Se2/0:924(FR DLCI) UP l2tp 9.9.0.7:10 UP
144
R7:
R7#sh xconnect all
------+---------------------------------+--+---------------------------------+--
UP ac Se2/0:721(FR DLCI) UP l2tp 9.9.0.9:10 UP
R21:
R21#sh ip route rip
R 172.9.0.24/32 [120/1] via 172.9.214.24, 00:00:00, Serial2/0
R21#sh ipv6 route rip

l - LISP
R 2002:172:9::24/128 [120/2]
via FE80::A8BB:CCFF:FE00:7C00, Serial2/0
R21#ping 172.9.0.24
!!!!!
R21#ping 2002:172:9::24
!!!!!
R24:
R24#sh ip route rip


R 172.9.0.21/32 [120/1] via 172.9.214.21, 00:00:12, Serial2/0
R24#sh ipv6 route rip
145
l - LISP
R 2002:172:9::21/128 [120/2]
via FE80::A8BB:CCFF:FE00:7900, Serial2/0
R24#ping 172.9.0.21

!!!!!
R24#ping 2002:172:9::21
!!!!!
4.3 VPLS
 Define VLAN 101 on SW2 and SW3

 Configure R3 and R4 to support VLAN over VPLS (see Diagram #1 for details)
 Ensure that VLAN 101 is bridged over VPLS. Use Loopback0 IPv4 address to establish neighbor.
 Configure SW3 so that SW3 is always the spanning-tree root for VLAN 101.
SOLUTION:
R3: R4:
interface GigabitEthernet0/0/0/5 description L2 Link to SW3 E0/3
description L2 Link to SW2 E0/2 cdp
cdp l2transport
l2transport !
! !
! l2vpn
l2vpn pw-class AToM
pw-class AToM encapsulation mpls
encapsulation mpls !
! !
! bridge group VPLS
bridge group VPLS bridge-domain VLAN101
bridge-domain VLAN101 interface GigabitEthernet0/0/0/4
! vfi 101
vfi 101 neighbor 9.9.0.3 pw-id 101
neighbor 9.9.0.4 pw-id 101 pw-class AToM
pw-class AToM !
! !
! !
! !
! !
!
SW2: SW3:
vlan 101 spanning-tree vlan 101 priority 0

name SW2-R3 !
! vlan 101
interface Ethernet0/2 name SW3-R4
description Link to R3 Gi0/0/0/5 !
switchport access vlan 101 interface Ethernet0/3
switchport mode access description Link to R4 Gi0/0/0/4
duplex auto switchport access vlan 101
! switchport mode access
duplex auto
!
VALIDATION:
146
R3:
RP/0/0/CPU0:R3#sh l2vpn bridge-domain
Fri Jan 25 01:42:50.523 MSK
Legend: pp = Partially Programmed.
Bridge group: VPLS, bridge-domain: VLAN101, id: 0, state: up, ShgId: 0, MSTi: 0
Aging: 300 s, MAC limit: 4000, Action: none, Notification: syslog
Filter MAC addresses: 0
ACs: 1 (1 up), VFIs: 1, PWs: 1 (1 up), PBBs: 0 (0 up)
List of ACs:
Gi0/0/0/5, state: up, Static MAC addresses: 0
List of Access PWs:
List of VFIs:
VFI 101 (up)
Neighbor 9.9.0.4 pw-id 101, state: up, Static MAC addresses: 0
R4:
RP/0/0/CPU0:R4#sh l2vpn bridge-domain

Fri Jan 25 01:43:41.985 MSK
Legend: pp = Partially Programmed.
Bridge group: VPLS, bridge-domain: VLAN101, id: 0, state: up, ShgId: 0, MSTi: 0
Aging: 300 s, MAC limit: 4000, Action: none, Notification: syslog
Filter MAC addresses: 0
ACs: 1 (1 up), VFIs: 1, PWs: 1 (1 up), PBBs: 0 (0 up)
List of ACs:
Gi0/0/0/4, state: up, Static MAC addresses: 0
List of Access PWs:
List of VFIs:
VFI 101 (up)
Neighbor 9.9.0.3 pw-id 101, state: up, Static MAC addresses: 0
SW3:
SW3#sh spanning-tree vlan 101 | i root
This bridge is the root
147
Section 5. Useful Command Aliases
One of the main factors which slowing down the Lab passing process is the differences between typing
of the same commands in IOS and IOS-XR. Commands do the same for IOS and IOS-XR both but syntax is
different, so you need to be very concentrating on which platform type you issued each specific
command.
- You can create the same alias in both IOS and IOS-XR for commands that do the same but have
different syntax.
- Speed up the typing process using aliases of 3 or 4 characters instead of commands of 3 – 6
words and special symbols like |, ^, etc.
-
Please see below the list of suggested command aliases that were used during writing this document:
IOS IOS-XR
Show Running Configuration
alias configure dsri do sh run | s router isis alias sri sh run router isis (*)
alias exec sri sh run | s router isis
alias configure dsrb do sh run | s router bgp alias srb show run router bgp
alias exec srb sh run | s router bgp
alias configure dsro do sh run | s router ospf alias sri sh run router ospf
alias exec sro sh run | s router ospf
alias configure dsri6 do sh run | s ipv6 router isis (*) shows isis configuration for IPv4 and IPv6
alias exec sri6 sh run | s ipv6 router isis address families in the same time
alias configure dsro6 do sh run | s ipv6 router ospf alias sro6 sh run router ospfv3
alias exec sro6 sh run | s ipv6 router ospf
alias srbv sh run router bgp 9 vrf ABC
alias srn sh run router bgp 9 neighbor

alias srn sh run router bgp 1009 neighbor
Show Operational Data

alias exec sb4s sh ip bgp ipv4 unicast summary alias sb4 sh bgp ipv4 unicast
alias configure dsb4s sh ip bgp ipv4 unicast summary
alias exec sb4 sh ip bgp ipv4 unicast alias sb4s sh bgp ipv4 unicast summary
alias configure dsb4 sh ip bgp ipv4 unicast
alias exec sb6s sh ip bgp ipv6 unicast summary alias sb6 sh bgp ipv6 unicast
alias configure dsb6s sh ip bgp ipv6 unicast summary
alias exec sb6 sh ip bgp ipv6 unicast alias sb6s sh bgp ipv6 unicast summary
alias configure dsb6 sh ip bgp ipv6 unicast
alias exec si4 sh ip int br | ex un alias si4 sh ipv4 int br | ex un

alias configure dsi4 do sh ip int br | ex un
alias exec si6 sh ipv6 int br | ex un alias si6 sh ipv6 int br | ex un

alias configure dsi6 do sh ipv6 int br | ex un
148

SPlab 111

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SPlab 111

Transféré par

Droits d'auteur :

Formats disponibles

CCIE SP Lab 1 Workbook version 1.

1.10 E BGP IPV6 UNICAST T ROUBLESHOOTING ........................................................................................34

1.11 BGP IPV4 UNICAST PATH SELECTION ..............................................................................................37

3.2 IBGP VPN V6 TROUBLESHOOTING ...................................................................................................75

3.3 INTRA AS VPN V4 ..........................................................................................................................79

lo0 vrf XYZ vrf XYZ vrf XYZ vrf XYZ

Core provider network

– first two octets 9.9.

– first two octets 9.9.

1.1 IS-IS FOR IPV4 TROUBLESHOOTING – AS9

Table 1: Preconfigured IPv4 addresses in the Core IGP, AS9

R5#sh isis neighbors

RP/0/0/CPU0:R2#sh isis neighbors

1.2 IS-IS FOR IPV6 TROUBLESHOOTING – AS9

Table 2: Preconfigured IPv6 addresses in the Core IGP, AS9

R5#sh ipv6 route 2002:9:9:78::/64

Routing entry for 2002:9:9:78::/64

Table 3: Preconfigured IPv4 addresses in the Core IGP, AS1009

R10#sh isis neighbors

1.4 OSPF FOR IPV6 TROUBLESHOOTING – AS1009

Table 4: Preconfigured IPv6 addresses in the Core IGP, AS1009

R9#sh ipv6 ospf neighbor

OSPFv3 Router with ID (9.9.0.9) (Process ID 1009)

Neighbor ID Pri State Dead Time Interface ID Interface

R10#sh ipv6 ospf neighbor

OSPFv3 Router with ID (9.9.0.10) (Process ID 1009)

Neighbor ID Pri State Dead Time Interface ID Interface

router ospfv3 1009 interface Ethernet0/1

RP/0/0/CPU0:R1#sh ospfv3 interface gi0/0/0/1

CCIE SP Lab1 iBGP IPv4 Unicast Diagram

lo0 lo0 iBGP

lo0 lo0 lo0 lo0

E0/1 E0/2 .0.4 .0.8

router bgp 1009 router bgp 1009

router bgp 9 router bgp 1009

RP/0/0/CPU0:R2#sh bgp ipv4 uni summary

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Wed Dec 12 17:31:29.753 MSK

R5#sh ip bgp ipv4 uni sum

RP/0/0/CPU0:R3#sh bgp ipv4 unicast summary

Thu Dec 13 23:58:22.355 MSK

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

RP/0/0/CPU0:R3#sh bgp ipv4 unicast

Fri Dec 14 00:01:13.269 MSK

RP/0/0/CPU0:R4#sh bgp ipv4 uni summary

Fri Dec 14 00:06:46.507 MSK

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

RP/0/0/CPU0:R4#sh bgp ipv4 uni

R7#sh ip bgp ipv4 unicast summary

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

R7#sh ip bgp ipv4 unicast

R8#sh ip bgp ipv4 unicast summary

BGP table version is 18, local router ID is 9.9.0.8

R9#sh ip bgp ipv4 unicast summary

Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd

R9#sh ip bgp ipv4 unicast

R10#sh ip bgp ipv4 uni summary

BGP router identifier 9.9.0.10, local AS number 1009

R10#sh ip bgp ipv4 uni

Network Next Hop Metric LocPrf Weight Path

BGP is operating in STANDALONE mode.

Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd