Lab 2 Questions

CCIE SP Lab 2

Page 1 of 35

CCIE SP Lab 2

Page 2 of 35

CCIE SP Lab 2

Section 1: Implement, Optimize and Troubleshooting Core IP Technology

1.1

OSPF for IPv4 Troubleshooting-1

OSPF for IPv4 routing on the in AS 9 have been configured as shown in this table.

Page 3 of 35

CCIE SP Lab 2

1.2

OSPF for IPv6 Troubleshooting

OSPSF for IPv6 routing on the routers in AS 9 have been configured as shown in this table.

Page 4 of 35

CCIE SP Lab 2

1.3

ISIS for IPv4 Troublshooting-2

IS-IS for IPv4 routing on the routers in AS 1009 have been configured as shown in this table.

On R10, the CLNS Neighbor type to R9 should be L2 only. Fix the problem so that the neighbor type to R9 is L2
Only.

Page 5 of 35

CCIE SP Lab 2

1.4

ISIS for IPv6 Troubleshooting

ISIS for IPv6 routing on the routers in AS 1009 and have been configured as shown in this table.

Page 6 of 35

CCIE SP Lab 2

1.5

IS-IS Level

Configure IS-IS the routers in AS 1009 (Refer to Question 1.3 for routers, interface and area specification).
On AS 1009 routers, configure the interface IS-IS type into Level-2-only. Ensure that these subnets are shown in 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.

Configure ISIS as Point-to-Point network between R1 and R8

Page 7 of 35

CCIE SP Lab 2

1.6

OSPF BFD
Configure OPSF on routers in AS 9 (Refer to Q1.1 for router, interface and area specification).

1.7

Configure OSPF BFD between R5 and R6.

IPv6 Path Cost

R7 is getting R5 Loopback IPv6 via two paths and from R2-R3-R5 configure R3 such that it should prefer the path
first one as primary.

R4-R6-R5

Page 8 of 35

CCIE SP Lab 2

1.8

iBGP IPv4 Unicast Troubleshooting

R2 R3 R4 R5 R7 R6 have been preconfigured to belong to AS9.
R1 R8 R9 R10 have been preconfigured to belong to AS1009.

R2 and R7 act as the route reflector for iBGP IPv4 unicast within AS9. An iBGP ipv4 session should not be
established between R3 R4 R5 R6.

R1 , R8 act as route reflector for IBGP IPv4 unicast within AS1009. An iBGP IPv4 session should not establish
between R9 R10.

The interface loopback0 IP address is used to establish BGP IPv4 session.

All Router loopback0 network is advertised as BGP IPv4 unicast updates.

Page 9 of 35

CCIE SP Lab 2

1.9

iBPG IPv6 Unicast Troubleshooting

R2 R3 R4 R5 R7 R6 have been preconfigured to belong to AS9.
R1 R8 R9 R10 have been preconfigured to belong to AS1009.

R2 act as the route reflector for IBGP IPV6 unicast within AS9. An iBGP IPv6 session should not be
established between R3 R4 R5 R6 R7.

R1 act as route reflector for iBGP IPv6 unicast within AS1009. An IBGP IPV6 session should not establish between
R8 R9 R10.

The interface loopback0 IP address is used to establish BGP IPv6 session.

All Router loopback0 network is advertised as BGP IPv6 unicast updates.

Page 10 of 35

CCIE SP Lab 2

1.10 eBGP IPv4 Unicast

Configure a eBGP IPv4 unicast session between R1 and R2

Configure a eBGP IPv4 unicast session between R7 and R8

After you complete these configurations, Loopback0 network of R2, R3, R4, R5, R6 and R7 should appear on the
routing tables of R1, R8, R9 and R10 as BGP IPv4 routers. Loopback0 network of R1, R8, R9 and R10 should
appear on the routing table of R2, R3, R4, R5, R6, and R7 as BGP IPv4 routers. No other routes should distribute
between AS 9 and AS 1009.

Ensure these loopback can ping each other via IPv4.

Directly connected PPP network, such as 9.9.12.0/24 and 9.9.78.0/24 are NOT permitted to be redistributed into
IGP routing protocols.

Page 11 of 35

CCIE SP Lab 2

1.11 eBGP IPv6 Unicast

Configure a eBGP IPv6 unicast session between R1 and R2

After you complete these configurations, Loopback0 network of R2, R3, R4, R5, R6 and R7 should appear on the
routing tables of R1, R8, R9 and R10 as BGP IPv4 routers. Loopback0 network of R1, R8, R9 and R10 should
appear on the routing table of R2, R3, R4, R5, R6, and R7 as BGP IPv6 routers. No other routes should distribute
between AS 9 and AS 1009.

Ensure these loopback can ping each other via IPv6.

Directly connected PPP network, such as 2002:9:9:12::/64 are NOT permitted to be redistributed into IGP routing
protocols.

Page 12 of 35

CCIE SP Lab 2

1.12 BGP IPv4 Unicast Path selection

Configure R7 to ensure that ipv4 traffic from AS9 destined to AS1009 chooses R7 as primary exit point and R2 as
backup exit point.

Configure R8 to ensure that ipv4 traffic from AS1009 destined to AS9 chooses R8 as primary exit point and R1 as
backup exit point.

Page 13 of 35

CCIE SP Lab 2

1.13 MPLS LDP Troubleshooting

R2, R3, R4, R5, R6 and R7 have been enabled MPLS LDP in AS9 on the interfaces that are shown this table.

R1, R8, R9 and R10 have been enabled MPLS LDP in AS 1009 on the interface that are shown in this table.

Any interface that is NOT listed in the table should NOT enable MPLS.

Page 14 of 35

CCIE SP Lab 2

1.14 MPLS Traffic Engineering:

Set up MPLS traffic engineering tunnel between R6 & R2.

Configure R2 R3 R4 R5 R6 R7 to support MPLS traffic engineering.

Set up MPLS TE tunnel 62 on R6 to reach R2 via R4 R3 R2.
Set up MPLS TE tunnel 26 on R2 to reach R6 via R3 R5 R6.
Ensure that traffic from R6 to the R2 loopback 2 interface chooses tunnel 62.
Ensure that traffic from R2 to the R6 loopback 2 interface chooses tunnel 26.
you are permitted to define static route on R6 and R2 to accomplish this task.
Configure R2 R3 R4 R5 R6 R7 to support a maximum 20 MB reservation on each sub interface.
set up MPLS TE tunnel 62 with a bandwidth 6 and MPLS Tunnel 26 with bandwidth 2 MB.

Page 15 of 35

CCIE SP Lab 2

1.15 MPLS TE Link Protection:

Set up an MPLS traffic engineering tunnel between R6 and R7.

Set up MPLS TE tunnel 67 to reach R7. use dynamic path option.

The TE tunnel 67 will transverse the link of Vlan XX (to be confirmed) between R4-R7.
Setup a backup MPLS TE tunnel 47 on R4 to protect the link of Vlan XX the backup tunnel originates from R4
through R3 and end at R7.
if R4 detect any failure of the link, TE tunnel 67 should switch to this backup tunnel immediately.

Page 16 of 35

CCIE SP Lab 2

1.16 IPv4 PIM-SM Troubleshooting:

IPV4 multicast and PIM sparse mode have been configured in the services provider network AS9 and AS1009 as
follows:

The interfaces that are shown in this table have been configured to PM sparse mode.

Interface that are NOT listed in the table should not enable PIM-SM.
Ensure that R3 should be DR for neighbour session in between R3 and R4.
Page 17 of 35

CCIE SP Lab 2

1.17 IPv4 PIM-SM RP

Configure PIM-SM RP in the service provider network AS9 and AS1009 as follows:

R2 R3 R4 R5 R7 R6 are in the same multicast domain and use the R7 loopback0 ipv4 address as the RP.
Use the BSR method to distribute the RP within AS9.
R1 R8 R9 R10 are in the same multicast domain and use the R8 loopback 0 ipv4 address as the RP within AS1009.
RP information should not leak between the two domain AS9 and AS1009.
Multicast group address have been configured as shown in table 2.
Ensure that routers within AS 9 can ping the group address within AS9.
Ensure that router within AS1009 can ping the group address within AS 1009.

Page 18 of 35

CCIE SP Lab 2

1.18 IPv4 MSDP

Configure MSDP between AS9 and AS1009 as follows:

Configure MSDP on R7 and R8. Use R7 and R8 Loopback 0 interface IPV4 address to establish MSDP peer.
The RPs (R7 and R8) should inform each when multicast sources become active in their autonomous systems.
Ensure that the routes in AS 9 can ping multicast group in AS 1009 using the sources of loopback 0.
Ensure that the routers in AS 1009 can ping multicast group address in AS9 using the sources of loopback 0.

Page 19 of 35

CCIE SP Lab 2

1.19 MPLS LDP Authentication

Configure R1 and R9 so that MPLS LDP session between them is authenticated in MD5 mode.
Use the password of cisco

Page 20 of 35

CCIE SP Lab 2

Section 2: Implement , Optimize and Troubleshooting Access/Edge

connection technologies.

2.1

PPP

Configure PPP link between R10 and R20 on interface of serial 2/0 (Refer to Diagram #1 for the connection).
Configure IS-IS Level-1 between R9 and R20 on the interface that are shown in this table.

Ensure that R20 has full IPv4 and IPv6 connection with the routers in AS 1009.

Page 21 of 35

CCIE SP Lab 2

Section 3: Implement, Optimize and troubleshoot L3VPN Technologies.

Virtual routing and forwarding instances (VRFs) on R1 R2, R3 , R4, R5, R6, R9 R10, R11, R12, R13, R14 have
been configured as follows:

VRF ABC Site1 users the VRF name ABC (case-sensitive) with route distinguisher (RD) 9:9 and import and export
route target 9:9 for IPv4 and IPv6 address family.

VRF ABC Site2 users the VRF name ABC (case-sensitive) with route distinguisher (RD) 9:9 and import and export
route target 9:9 for IPv4 and IPv6 address family.

VRF ABC Site3 users the VRF name ABC (case-sensitive) with route distinguisher (RD) 1009:9 and import and
export route target 1009:9 for IPv4 and IPv6 address family.

VRF XYZ Site 1 and Site 2 use the VRF name XYZ (case-sensitive) with RD 112:112 and import and export route
target 112:112 for IPv4 address family.

VRF XYZ Site 3 use the VRF name XYZ (case-sensitive) with RD 1109:1109 and import and export route target
1109:1109 for IPv4 address family.

Page 22 of 35

CCIE SP Lab 2

3.1

iBGP VPNv4 Troubleshooting

R2 R3 R4 R5 R6 R7 have been configured IBGP vpnv4 within AS9.
R1 R8 R9 R10 have been configured IBGP vpnv4 within AS1009.

R7 acts as a route reflector for iBGP vpnv4 unicast within AS9. An IBGP VPNV4 session should not be established
between R3 R4 R5 R6 R2.
R8 acts as a route reflector for iBGP vpnv4 unicast within AS9. An IBGP VPNV4 session should not be established
between R1 R9 R10.
The interface Loopback 0 IP address is used to established BGP VPNV4 sessions.
The interface Loopback 1 network is put into VRF ABC IPV4 unicast address family.

Page 23 of 35

CCIE SP Lab 2

3.2

iBGP VPNv6 Troubleshooting

R2 R3 R6 have been configured IBGP vpnv6 within AS9.
R1 R10 have been configured IBGP vpnv6 within AS1009.

R2 establishes a direct iBGP VPNv6 session with R3 and R6. R2 acts as a route reflector for iBGP VPNV6
information in AS9. An IBGP VPNV6 session should not be established between R3 & R6.

R1 establishes a direct iBGP VPNv6 session with R10 ONLY. R1 acts as a route reflector for iBGP VPNV6
information in AS1009.

The interface Loopback 0 IP address is used to establish iBGP IPV6 session.

The interface Loopback 1 network is put into VRF ABC IPV6 unicast address family.
There are some fault in the scenario find out and fix them.

Page 24 of 35

CCIE SP Lab 2

3.3

Intra AS VPNv4

The ABC company at Site 1 used BGP IPV4 to connect to the service provider router R4 & R6. R13 R14 locate in
AS109.

Establish BGP IPV4 unicast session between R4 and R13. Establish BGP IPV4 unicast session between R6 & R14.

Configure OSPF on R13 and R14 on the interface that are shown in the table.

Interface that are not listed in the table are not permitted to enable OSPF.

The ABC Company Site 2 used BGP IPV4 and OSPF to connect to service provider routers R3-R11 IPV4 BGP and
R12 - R5 OSPF IPV4. R11 and R12 locate in AS109.

Establish BGP IPV4 unicast session between R3 and R11.

Configure OSPF on R5 , R12 and R11 on the interfaces that are shown in this table.

Router
R5
R12
R11

Interface
Loopback 1
Ethe 1/0
Loopback 0
Ethe 1/1
Ethe 1/0
Loopback 0
Ethe 1/1

Area
0
0
0
0
0
0
0

Interfaces that are not listed in the table are not permitted to enable the OSPF. Ensure that the routers of ABC at
site 1 and site 2 can ping each other via IPV4.

Page 25 of 35

CCIE SP Lab 2

3.4

Intra AS VPNv6

The ABC company at Site 1 used BGP IPV6 to connect to the service provider router R4 & R6. R13 R14 locate in
AS109.

Establish BGP IPV6 unicast session between R6 & R14.

Configure OSPFV3 on R13 and R14 on the interface that are shown in the table.

Router
R13
R14

Interface
Loopback 0
Ethe 1/1
Loopback 0
Ethe 1/1

Area
0
0
0
0

Interface that are not listed in the table are not permitted to enable OSPF.

The ABC Company Site 2 used BGP IPV6 and EIGRP to connect to service provider routers R3-R11 IPV6 BGP and
R11 - R12 EIGRPV6.

Establish BGP IPV6 unicast session between R3 and R11.

Configure EIGRPV6 on R11 , R12 on the interfaces that are shown in this table.

Router
R12
R11

Interface
Loopback 0
Ethe 1/1
Loopback 0
Ethe 1/1

Area
0
0
0
0

Interfaces that are not listed in the table are not permitted to enable the EIGRP.

Ensure that the routers of ABC at site 1 and site 2 can ping each other via IPV6.

Page 26 of 35

CCIE SP Lab 2

3.5

Inter AS VPNv4

Configure R7 and R8 to establish eBGP VPNv4 sessions.

Other router in AS9 and AS 1009 should not exchange the EBGP VPNV4 information between these two AS.

The ABC company at Site 3 uses EIGRP to connect to the service provider routers R9 R10.

Configure EIGRP on R9 R10 and R16 R15 on the interfaces that are shown in the table.

Router
R9 / R10
R16

R15

Interface
Loopback 0
Ethe 1/0
Loopback 0
Ethe 1/0
Ethe 1/1
Loopback 0
Ethe 1/0
Ethe 1/1

Area
100
100
100
100
100
100
100
100

Interfaces that are not listed in the table are not permitted to enable EIGRP.

Only the import route-target method can be used to control VPNV4 route distribution.

configure accordingly so that router of ABC at Site1, Site 2 and Site 3 can ping each via IPV4.

you are permitted to define a static route on R1 and R2.

Page 27 of 35

CCIE SP Lab 2

3.6

Inter AS VPNV6

Configure R1 and R2 to establish e-BGP VPNv6 sessions.

Other router in AS9 and AS 1009 should not exchange the EBGP VPNV6 information between these two AS.

The ABC company at Site 3 uses BGP to connect to the service provider routers R9 R10. Router R16, R15 locate in
AS1109

Establish BGP IPV6 unicast session between R15 R16.

Establish BGP IPV6 unicast session between R16 and R10.

Only the import route target method can be used to control VPNv6 route distribution.

Configure accordingly so that routers of ABC at site 1, 2 , 3 can ping each other via ipv6.

Page 28 of 35

CCIE SP Lab 2

3.7

Carrier Supporting Carrier -1

VPN ABC site 1 and site 2 is one service provider carrier (AS109) that is distributed in two locations. it requests
support from AS 9 service provider carriers to provide MPLS VPNV4 services.

Configure R3 R4 R5 R6 R11 R12 R14 R13 so that AS 109 is able to deliver MPLS VPNV4 services.

The XYZ company at site 1 uses RIP version 2 to connect to the service provider router R13 and R14.

The XYZ company at site 2 uses RIP version 2 to connect to the service provider router R11 and R12.

Page 29 of 35

CCIE SP Lab 2

3.8

Carrier Supporting Carrier -2

The XYZ company at site 3 uses OSPF to connect to the service provider R15 and R16.
Configure RIP v-2 on the interfaces that are shown in this table.
Router
R11
R12
R17

R13
R14
R18

Interface
Loopback 1
Ethe 0/0
Loopback 1
Ethe 0/0
Loopback 1
Ethe 0/0
Ethe 0/1
Loopback 1
Ethe 0/0
Loopback 1
Ethe 0/0
Loopback 1
Ethe 0/0
Ethe 0/1

Establish BGP VPNv4 unicast session between R13 , R12 and R13 to R16.
Configure accordingly so that routers of XYZ at Site 1 and Site 2 can Ping each other via IPV4.
you are permitted to define static route on R3 & R4 VRF ABC.
First Enable MPLS Supports on interfaces which are in IGP.

Page 30 of 35

CCIE SP Lab 2

3.9

Intra AS Multicast VPN

The router in VPN ABC site 1 and site 2 have been configured PIM SM on the interface show in the table there
are some fault find out and fix them. (Table of interconnect).
Statically define the IPV4 address of interface Loopback 0 on R11 as the RP.
Multicast group address have been configured on Loopback 0 of R11 R12 R13 R14.
Configure R3,R4,R5, R6 so that they support multicast VPN. USE 239.255.13.100 for VRF ABC mdt default group
address.
Establish that R11 R12 R13 R14 can ping each these group address

Page 31 of 35

CCIE SP Lab 2

Section 4. Implement, Optimize and troubleshoot L2VPN Technologies

4.1

HDLC over MPLS

R22 and R23 would like to establish HDLC connection through AS 9.

Configure R7 and R6 to support HDLC over MPLS.
configure OSPF for IPV4 and IPV6 on the interfaces that are shown in this table.

Router
R22
R23

Interface
Loopback 0
S 2/0
Loopback 0
S 2/0

Area
0
0
0
0

Ensure that R22 and R23 have the OSPF IPV4 and IPV6 routes and can ping each other via IPV4 and IPV6

Page 32 of 35

CCIE SP Lab 2

4.2

Frame Relay & PPP over L2TPV3

R21 and R24 connect to the service provider by FR and PPP respectively.
configure L2TPV3 on R5 and R10 to support FR and PPP using interworking IP. Configure OSPF IPV4 on the
interfaces that are show in this table.
Router
R21
R24

Interface
Loopback 0
S 2/0
Loopback 0
S 2/0

Area
0
0
0
0

Ensure that R21 and R24 have full IPV4 connectivity.

Page 33 of 35

CCIE SP Lab 2

4.3

VPLS

Define Vlan 123 on SW2 and SW3.

Configure R3 and R4 to support Vlan over VPLS. Ensure that Vlan 123 is bridged over VPLS. Use Loopback 0
IPV4 address to establish neighbor.
Configure SW3 so that SW3 becomes the SPT root for vlan 123.
VPLS is configured b/w R2 & R4.

Page 34 of 35