CCIE SP v5

CCIE Service Provider v5 Exam Review
ine.com
Configuring OSPFv2 for ISP-1
ine.com
TASK 1
Ø Configure OSPF on XE-R2, XE-R3, XE-R4, XE-R5, and XE-R6.
Ø Use Process-ID 1 and statically set the router-id to its
respective Loopback 0 Address.
Ø Activate OSPF on all internal links within the ISP-1
infrastructure.
Ø Loopback 0 must also be a part of OSPF Area 0.
Ø All OSPF enabled interfaces must be in Area 0.
OSPF Ø Do not enable OSPF on any links facing the customer or
another ISP.
Ø Once complete, all devices within the ISP-1
infrastructure should have reachability to each other.
OSPF Network Types, Path Cost and
Loopback Network Type in OSPF
ine.com
TASK 2
Ø Change the network type on XE-R2, XE-R3, XE-R4, XE-R5,
and XE-R6 to improve OSPF convergence.
Ø Loopback 0 must show the correct subnet mask in the
routing table.
Ø Traffic between XE-R2’s, XE-R3’s, XE-R5’s, and XE-R6’s
Loopback 0 must transit XE-R4 router.
OSPF
OSPF Authentication and BFD
ine.com
TASK 3
Ø Ensure OSPF reconvergence begins in less than one second,
if the link to XE-R4 fails.
Ø Configure clear text OSPF Authentication between XE-R2
and XE-R5. Use password as cisco.
OSPF and XE-R6. Use password as cisco.
Ø Configure MD5 OSPF Authentication between XE-R4 and XE-
R(2/3/5/6). Use password as cisco.
Configuring IPV6 Addresses in ISP-1
ine.com
TASK 4
Ø Configure all links within the ISP-1 infrastructure with
an IPv6 Address.
Ø Loopback 0 must have IPv6 address as X::X/128, where X is
the router number. For example, IPv6 address for XE-R2’s
Loopback 0 would be 2::2/128.
Ø IPv6 address for link between routers within the ISP-1
infrastructure would be in the format of 2001:P:Q:R::X/64
OSPFv3 ,where “P” is the first octet of the IPv4 address on that
link, “Q” is the second octet of the IPv4 address on that
link, “R” is the third octet of the IPv4 address on that
link, and “X” is the router number. For example, IPv6
address for XE-R2’s link to XE-R5 would be
2001:172:16:25::2/64.
Configuring OSPFv3 in ISP-1
ine.com
TASK 5
Ø Configure OSPFv3 on XE-R2, XE-R3, XE-R4, XE-R5, and XE-
R6.
infrastructure.
OSPFv3 Ø All OSPF enabled interfaces must be in Area 0.
Ø Do not enable OSPF on any links facing the customer or
another ISP.
infrastructure should have reachability to each other.
OSPFv3 Network Types, Path Cost and
Loopback Network Type in OSPF
ine.com
Task 6
routing table.
Ø Traffic between XE-R2’s, XE-R3’s, XE-R5’s, and XE-R6’s
Loopback 0 must transit XE-R4 router.
OSPFv3
OSPFv3 Authentication and BFD
ine.com
TASK 7
Ø Ensure OSPFv3 reconvergence begins in less than one
second, if the link to XE-R4 fails.
Ø Configure OSPFv3 IPsec ESP Encryption and Authentication
between XE-R2 and XE-R4 using the following parameters:
• Use Security Parameter Index (SPI) 1920
• Use ESP with AES 256-bit Encryption and SHA1 Authentication
• For the AES encryption key use
OSPFv3 •
0x0123456789abcdef0123456789abcdef0123456789abcdef0123456789
abcdef
For the SHA authentication key
0x0123456789012345678901234567890123456789
Address-Family Based OSPFv3
ine.com
TASK 8
Ø Configure OSPFv3 (Common Process for IPv4 and IPv6) on
XE-R2, XE-R3, XE-R4, XE-R5, and XE-R6.
infrastructure.
OSPFv3 Ø All OSPF enabled interfaces must be in Area 0.
Ø Do not enable OSPF on any links facing the customer or
another ISP.
infrastructure should have reachability to each other on
their IPv4 addresses and IPv6 addresses.
Ø Ensure BFD still works.
routing table.
Ø All IPv4 and IPv6 traffic from PE’s must transit XE-R4.
Multi-Level ISIS in ISP-2
ine.com
TASK 9
Ø Configure Multi-level ISIS within the ISP-2
infrastructure.
Ø Use the following NET addresses:
• XR-R1 and XR-R2 should use NET addresses as
49.3132.0000.0000.003X.00, where X is the XR router number
• XR-R3 should use NET address as 49.0033.0000.0000.003X.00,
where X is the XR router number
ISIS • XR-R4 and XR-R5 should use NET addresses as

49.3435.0000.0000.003X.00, where X is the XR router number
Ø Configure ISIS level assignments as follows:
• XR-R1 and XR-R4 should be configured as a L1/L2 Router
• XR-R2 and XR-R5 should be configured as a L1 Router
• XR-R3 should be configured as a L2 Router
Ø Advertise Loopback 0 without activating ISIS on the
interface.
Ø Ensure ISIS is activated only on the links between XR-R1
and XR-R2, XR-R1 and XR-R3, XR-R3 and XR-R4, XR-R4 and
XR-R5.
Ø Once complete all devices should IPv4 reachability to the
Loopback0.
ISIS Route Leaking
ine.com
Task 10
Ø Configure Route-Leaking in ISIS within the ISP-2
infrastructure.
Ø Achieve the following requirements:
• Create a new Loopback (132.132.132.132/32) on XR-R2 and
advertise this loopback without activating ISIS
• XR-R1 must only leak L2 prefix (35.35.35.35/32) to its L1
neighbor
ISIS • XR-R1 must only leak L1 prefix (132.132.132.132/32) to its

L2 neighbor
Single Level ISIS
ine.com
TASK 11
Ø Remove ISIS from XR-R1, XR-R2, XR-R3, XR-R4, and XR-R5.
Ø Configure Single-level ISIS within the ISP-2
infrastructure.
Ø Use the following NET addresses:
• XR-R1, XR-R2, XR-R3, XR-R4, and XR-R5 should use NET
addresses as 49.3333.0000.0000.003X.00, where X is the XR
router number
ISIS Ø Configure ISIS level assignments as follows:

• XR-R1, XR-R2, XR-R3, XR-R4, and XR-R5 should be configured
as a L2 Router
Ø Advertise Loopback 0 without activating ISIS on the
interface.
Ø Ensure ISIS is activated on all links within the ISP-2
infrastructure.
Ø Do not activate ISIS on links connected to Customer or on
links connected to any other ISP.
Ø Once complete all devices should IPv4 reachability to the
Loopback0.
ISIS Network Type, BFD and Authentication
ine.com
TASK 12
Ø Change the network type on XR-R1, XR-R2, XR-R3, XR-R4,
and XR-R5 to improve ISIS convergence.
Ø Traffic between XR-R1’s, XR-R2’s, XR-R4’s, and XR-R5’s
Loopback 0 must transit XR-R3 router.
Ø Ensure ISIS reconvergence begins in less than one second,
if the link to XR-R3 fails.
Ø Configure clear text OSPF Authentication between XR-R1
ISIS and XR-R2. Use password as cisco.
and XR-R4. Use password as cisco.
Ø Configure MD5 OSPF Authentication between XR-R3 and XR-
R(1/2/4/5). Use password as cisco.
Configuring IPV6 Addresses in ISP-2
ine.com
TASK 13
Ø Configure all links within the ISP-2 infrastructure with
an IPv6 Address.
Ø Loopback 0 must have IPv6 address as 3X::3X/128, where X
is the router number. For example, IPv6 address for XR-
R1’s Loopback 0 would be 31::31/128.
Ø IPv6 address for link between routers within the ISP-2
infrastructure would be in the format of
ISIS 2001:P:Q:R::3X/64,where “P” is the first octet of the
IPv4 address on that link, “Q” is the second octet of the
IPv4 address on that link, “R” is the third octet of the
IPv4 address on that link, and “X” is the router number.
For example, IPv6 address for XR-R1’s link to XR-R2 would
be 2001:10:31:32::31/64.
Configuring ISIS Multi-Topology
ine.com
TASK 14
Ø Configure ISIS to run in Multi-Topology mode on all
routers within the ISP-2 infrastructure.
Ø Ensure IPv4 traffic from XR-R1’s Loopback 0 (31.31.31.31)
to XR-R5’s Loopback 0 (35.35.35.35) prefers the path of
XR-R1 -> XR-R2 -> XR-R3 -> XR-R4 -> XR-R5.
Ø Ensure IPv4 traffic from XR-R5’s Loopback 0 (35.35.35.35)
to XR-R1’s Loopback 0 (31.31.31.31) prefers the path of
ISIS XR-R5 -> XR-R4 -> XR-R3 -> XR-R2 -> XR-R1.
Ø Ensure IPv6 traffic from XR-R1’s Loopback 0 to XR-R5’s
Loopback 0 prefers the path of XR-R1 -> XR-R4 -> XR-R3 ->
XR-R2 -> XR-R5.
Ø Ensure IPv4 traffic from XR-R5’s Loopback 0 to XR-R1’s
Loopback 0 prefers the path of XR-R5 -> XR-R2 -> XR-R3 ->
XR-R4 -> XR-R1.
Configuring ISIS Single-Topology
ine.com
Task 15
Ø Configure ISIS to run in Single-Topology mode on all
Ø Change the network type on XR-R1, XR-R2, XR-R3, XR-R4,
and XR-R5 to improve ISIS convergence for IPv4 and IPv6.
Ø Traffic between XR-R1’s, XR-R2’s, XR-R4’s, and XR-R5’s
Loopback 0 must transit XR-R3 router for IPv4 and IPv6.
Ø Ensure ISIS reconvergence begins in less than one second,
ISIS if the link to XR-R3 fails for both IPv4 and IPv6
traffic.
Configuring MPLS in OSPF
ine.com
TASK 16
Ø Create a new Loopback 1 on XE-R2 (2.0.0.2/32) and on XE-
R6 (6.0.0.6/32). Do not advertise this loopback in any
IGP.
Ø Configure MPLS Label Distribution with LDP on all links
within the ISP-1 infrastructure.
Ø Links connected to Customer or another ISP must not have
LDP enabled.
MPLS Ø Use LDP router-id as Loopback0 on all routers within the
ISP-1 infrastructure, except XE-R2 and XE-R6.
Ø XE-R2 and XE-R6 must use Loopback 1 as the router-id.
Ø Ensure label range for each router if from the range of
X000-X999, where “X” is the router number.
Ø Use may use MPLS LDP Autoconfig in OSPF only on XE-R2
and/or XE-R6.
Configuring MPLS in ISIS
ine.com
TASK 17
Ø Create a new Loopback 1 on XR-R1 (31.0.0.31/32) and on
XR-R5 (35.0.0.35/32). Do not advertise this loopback in
any IGP.
Ø Links connected to Customer or another ISP must not have
LDP enabled.
MPLS Ø Use LDP router-id as Loopback0 on all routers within the
ISP-2 infrastructure, except XR-R1 and XR-R5.
Ø XR-R1 and XR-R5 must use Loopback 1 as the router-id.
Ø Ensure label range for each router if from the range of
3X000-3X999, where “X” is the router number.
Ø Use may use MPLS LDP Auto-config in ISIS only on XR-R1
and/or XR-R5.
Configuring LDP Authentication
ine.com
TASK 18
Ø Configure authentication for the LDP peering’s in ISP-1
as follows:
• XE-R2 and XE-R3 should authenticate their LDP session with
the password “r2r3cisco”.
MPLS
• XE-R2, XE-R3, XE-R5, and XE-R6 should authenticate their LDP
session with XE-R4 with the password set as “C1sc0123”.
• XE-R4 should authenticate their LDP session with the
password option 1 with the password as “C1sc0123”.
• All routers within the ISP-1 infrastructure should require
that every LDP session use authentication.
• All routers within the ISP-1 infrastructure should fallback
to the default password “default” for any unmatched
sessions.
Configuring LDP Authentication on
IOS-XR, LDP and IGP Synchronization,
LDP Session Protection, LDP Filtering
ine.com
TASK 19
Ø Configure LDP and IGP Synchronization with OSPFv2 on all
Ø Configure LDP Session Protection so that if a connected
link between any of the routers within the ISP-1 or ISP-2
infrastructure goes down, a unicast targeted LDP session
remains up.
Ø Configure ISP-1 and ISP-2 to ensure that TTL of packets
MPLS coming from the customer’s network is not copied into the
MPLS label.
Ø Configure LDP filtering so that labels are only allocated
for the Loopback0 networks of XE-R2, XE-R3, XE-R4, XE-R5,
and XE-R6.
Ø Configure LDP filtering so that labels are only allocated
for the Loopback0 networks of XR-R1, XR-R2, XR-R3, XR-R4,
and XR-R5.
Ø Configure authentication for the LDP peering’s in ISP-2:
• XR-R1, XR-R2, XR-R4, and XR-R5 should authenticate their LDP
session with the password “cisco”.
• XR-R3 should fallback to the default password “cisco”.
• All routers within the ISP-2 infrastructure should require that
every LDP session use authentication.
Configuring Segment Routing
ine.com
TASK 20
Ø Configure Segment Routing in ISP-1 and ISP-2
infrastructure as follows:
• Assign Prefix-SIDs based on Loopback0
• Ensure Segment Routing is enabled for IPv4 control plane and
MPLS data plane
• You may set absolute prefix-sid values for ISP-1 routers as
Segment •
1600X, where ”X” is the router number
You may set absolute prefix-sid values for ISP-2 routers as
1603X, where ”X” is the router number
Routing Ø Ensure Segment Routing is preferred over LDP.

Configuring Global BGP Neighborship
ine.com
Task 21
Ø Create two new sub-interfaces on XE-R1 as follows:
• Interface G1.1212, encapsulation as 1212, IP address as
10.1.2.1/24
10.1.3.1/24
Ø Create one new sub-interface on XE-R2 as follows:
10.1.2.2/24
BGP Ø Create one new sub-interface on XE-R3 as follows:

10.1.3.3/24
Ø Create a new loopback 1111 on XE-R1 with IP address as
1.1.1.1/32.
Ø Establish IPv4 E-BGP neighborship between XE-R1 and XE-
R2.
Ø Establish IPv4 E-BGP neighborship between XE-R1 and XE-
R3.
Ø Establish IPv4 I-BGP neighborship between XE-R4 and XE-
R(2/3/5/6)with XE-R4 being the Route Reflector.
Ø Advertise Loopback 1111 in BGP using network statement.
Ø XE-R1 belongs to BGP AS 1.
Ø XE-R2, XE-R3, XE-R4, XE-R5, and XE-R6 belong to AS 2356.
ine.com
TASK 22
Ø Create two new sub-interfaces on XE-R16 as follows:
• Interface G1.16034, encapsulation as 1604 , IP address as
10.16.34.16/24
10.16.35.16/24
Ø Create one new sub-interface on XR-R4 as follows:
• Interface G0/0/0/0.16034, encapsulation as 1604, IP address as
10.16.34.34/24
BGP Ø Create one new sub-interface on XR-R5 as follows:

10.16.35.35/24
Ø Create a new loopback 1616 on XE-R16 with IP address as
16.16.16.16/32.
Ø Establish IPv4 E-BGP neighborship between XE-R16 and XR-
R4.
R5.
Ø Establish IPv4 I-BGP neighborship between XR-R3 and XR-
R(1/2/4/5)with XR-R3 being the Route Reflector.
Ø Advertise Loopback 1616 in BGP using network statement.
Ø XR-R16 belongs to BGP AS 16.
Ø XR-R1, XR-R2, XR-R3, XR-R4, and XR-R5 belong to AS 12345.
and BGP Attributes
ine.com
TASK 23
R1.
R2.
Ø Ensure 1.1.1.1/32 and 16.16.16.16/32 can ping each other.
Ø Ensure XE-R1 uses XE-R2 as the preferred path to reach
16.16.16.16/32. Use the most influential optional
BGP attribute.
Ø Ensure XE-R16 uses XR-R5 as the preferred path to reach
1.1.1.1/32. Use the most influential optional attribute.
Configuring BGP Attributes
ine.com
TASK 24
Ø Remove the previously configured path manipulation
attributes from XE-R1 and XE-R16.
16.16.16.16/32. Use the most influential well-known
attribute.
BGP 1.1.1.1/32. Use the most influential well-known
attribute.
ine.com
TASK 25
attributes from XE-R1 and XE-R16.
attribute.
attribute.
Ø Do not use Local Preference.
Ø Do not configure XE-R1 or XE-R16.
ine.com
TASK 26
attributes
attribute.
attribute.
Ø Do not use Local Preference or AS-Path Prepending.
Ø Do not configure XE-R1 or XE-R16.
ine.com
TASK 27
attributes
16.16.16.16/32. Use an optional non-transitive attribute.
1.1.1.1/32. Use an optional non-transitive attribute.
BGP Ø Do not use Local Preference or AS-Path Prepending or
Origin.
Ø Ensure the optional non-transitive attribute is used by
XE-R1, even if the BGP update from another ISP.
Configuring VRF’s and PE-CE Routing
Protocol
ine.com
TASK 28
Ø XE-R1 has two pre-configured VRF’s – “RED” and “BLUE”.
Ø XE-R1 would be servicing as Customer End router.
Ø XE-R2 and XE-R3 has two pre-configured VRF’s – “RED” and
“BLUE”.
Ø XE-R2 and XE-R3 would be servicing as Provider End
router.
Ø Use the following parameters for your VRF “RED”
L3VPN configuration:
•
•
Route Distinguisher : 1:1213
Route Targets : 1:1213
Ø Use the following parameters for your VRF “BLUE”
configuration:
• Route Distinguisher : 1:2131
• Route Targets : 1:2131
Ø Establish OSPF Area 0 adjacency between XE-R1 and XE-R2
in VRF “RED”. XE-R2 must use Process-ID as 123
in VRF “RED”. XE-R3 must use Process-ID as 123
Ø Establish E-BGP neighborship between XE-R1 and XE-R2 in
VRF “BLUE”
Configuring VRF’s and PE-CE Routing
Protocol
ine.com
TASK 29
Ø XE-R16 has two pre-configured VRF’s – “RED” and “BLUE”.
Ø XE-R16 would be servicing as Customer End router.
Ø XR-R4 and XR-R5 has two pre-configured VRF’s – “RED” and
“BLUE”.
Ø XR-R4 and XR-R5 would be servicing as Provider End
router.
•
•
configuration:
Ø Establish OSPF Area 0 adjacency between XE-R16 and XR-R4
in VRF “RED”. XR-R4 must use Process-ID as 3416
Ø Establish OSPF Area 0 adjacency between XE-R16 and XR-R5
in VRF “RED”. XR-R5 must use Process-ID as 3416
Ø Establish E-BGP neighborship between XE-R16 and XR-R4 in
VRF “BLUE”
Ø Establish E-BGP neighborship between XE-R16 and XR-R5 in
Configuring VPNv4 Neighborship
ine.com
Task 30
Ø Establish VPNv4 I-BGP neighborship between XE-R4 and XE-
R(2/3/5/6)with XE-R4 being the Route Reflector.
Ø Establish VPNv4 I-BGP neighborship between XR-R3 and XR-
R(1/2/4/5)with XR-R3 being the Route Reflector.
L3VPN
Inter-AS Option A
ine.com
TASK 31
Ø Provider End router XE-R6 need to establish connectivity
with ISP-3 to allow connectivity between VRF “RED” hosted
by ISP-1 and VRF “RED” hosted by ISP-3.
Ø Provider End router XE-R6 need to establish connectivity
with ISP-3 to allow connectivity between VRF “BLUE”
hosted by ISP-1 and VRF “BLUE” hosted by ISP-3.
•
•
configuration:
in VRF “RED” and between XE-R6 and XE-R7 in VRF “RED”.
VRF “BLUE” and between XE-R7 and XE-R8 in VRF “BLUE”.
Ø XE-R7 belongs to BGP AS 7 and XE-R8 belongs to BGP AS 1.
Ø Ensure ping from 1.1.1.1 to 8.8.8.8 and vice-versa in VRF
“RED” and VRF “BLUE” works.
OSPF Sham-Link and Domain-ID
ine.com
TASK 32
using the backdoor link (10.1.8.0/24) in VRF “RED”.
Ø Ensure that Customer “RED” always transits ISP-1 to reach
each other and uses the backdoor only if the links to
ISP-1 is down.
Ø You may create a new Loopbacks to achieve this
requirement.
L3VPN Ø Ensure Domain-ID matches between the PE routers.
Inter-AS Option B
ine.com
TASK 33
Ø Provider End router XR-R5 need to establish connectivity
with ISP-4 to allow connectivity between VRF “WHITE”
hosted by ISP-2 and VRF “WHITE” hosted by ISP-4.
Ø Use the following parameters for your VRF “WHITE”
configuration:
L3VPN Ø Establish E-BGP neighborship between XE-R20 and XE-R21 in

VRF “WHITE”.
Ø XE-R20 belongs to BGP AS 20 and XE-R21 belongs to BGP AS
21.
Ø Ensure ping from 21.21.21.21 to 19.19.19.19 and vice-
versa in VRF “WHITE” works.
Ø The link between ISP-2 and ISP-4 is in the global table.
Ø You may establish VPNv4 neighborship between ISP-2 and
ISP-4. But ensure ISP-2 and ISP-4 do not establish IPv4
BGP neighborship.
Ø PE-CE routing protocol between XR-R5 and XE-R19 must be
OSPF Area 0.
Inter-AS Option C
ine.com
TASK 34
Ø VRF “RED” must form OSPF Area 0 adjacency with PE
routers. Use Process-ID as 116.
Ø VRF “BLUE” must establish E-BGP neighborship with PE
Routers. XE-R1 belongs to AS 1. XE-R16 Belongs to AS 16.
Ø To establish connectivity for “RED” and “BLUE”, ISP-1 and
ISP-2 have decided to use the link between XE-R5 and XR-
R1. Shut the link between XE-R6 and XR-R2.
L3VPN Ø As a solution they have decided to establish VPNv4
neighborship between ISP-1 route reflector XE-R4 and ISP-
2 route reflector XR-R3.
Ø ISP-1 and ISP-2 have decided to redistribute appropriate
routes in to their respective IGP.
Ø Ensure ping from 1.1.1.1 to 16.16.16.16 and vice-versa in
VRF “RED” and VRF “BLUE” works.
Inter-AS Option C with i-BGP + Label
ine.com
TASK 35
Ø ISP-1 and ISP-2 need to provide redundant connectivity to
their customer “RED” sites and customer “BLUE” sites.
Ø To establish redundant connectivity for “RED” and “BLUE”,
ISP-1 and ISP-2 have decided to use the link between XE-
R6 and XR-R2.
Ø Also as a solution, ISP-1 has decided to NOT redistribute
appropriate routes in to their respective IGP, instead
L3VPN use IPv4 BGP.
Ø Also as a solution, ISP-2 has decided to redistribute
appropriate routes in to their respective IGP.
Ø Ensure ping from 1.1.1.1 to 16.16.16.16 and vice-versa in
VRF “RED” and VRF “BLUE” works.
Ø Ping between customers must work even if the link between
XE-R5 and XR-R1 fails.
Carrier Supporting Carrier – Part 1
ine.com
TASK 36
Ø Links connected to Customer or another ISP must not have LDP
enabled. Use LDP router-id as Loopback0.
Ø Ensure label range for each router is from the range of
X000-X999, where “X” is the router number.
Ø Use the following parameters for your VRF “GREEN”
•
•
Ø Use the following parameters for your VRF “YELLOW”
configuration:
and between XR-R4 and XE-R17 in VRF “GREEN”.
Ø Establish E-BGP neighborship between XE-R11 and XE-R13 and
between XR-R4 and XE-R18 in VRF “YELLOW”.
Ø XE-R13 belongs to BGP AS 13. XE-R18 belongs to AS 18
Carrier Supporting Carrier – Part 2
ine.com
TASK 37
Ø ISP2 and ISP-5 need to provide connectivity to their
customer “GREEN” sites and customer “YELLOW” sites.
Ø To establish connectivity for “GREEN” and “YELLOW”, ISP-2
and ISP-5 have decided to use the ISP-1 as a transit.
Ø You may create another VRF of your choice to achieve this
requirement.
Ø Establish I-BGP VPNv4 neighborship between XE-R9 and XE-
L3VPN R11.
Ø Configure OSPF Area 0 in ISP-5 infrastructure.
Ø Advertise all links within the ISP-5 infrastructure.
Ø Do not activate OSPF on links connecting to another
customer or another ISP.
versa in VRF “GREEN” works.
versa in VRF “YELLOW” works.
Central Services
ine.com
TASK 38
Ø Ensure XE-R1 VRF “RED” can ping networks belonging to
site ”GREEN”.
Ø Ensure XE-R1 VRF “BLUE” can ping 13.13.13.13 from
1.1.1.1.
L3VPN
Configuring 6PE
ine.com
TASK 39
Ø ISP-2 has acquired a new customer.
Ø Customer has requested IPv4 and IPv6 connectivity to its
remote site.
Ø Configure XE-R22 with an IPv6 address set as
(2001:10:22:31::22/64) on its G1.2231.
Ø Configure XR-R1 with an IPv6 address set as
(2001:10:22:31::31/64) on its G0/0/0/0.2231.
L3VPN Ø Configure XR-R6 with an IPv6 address set as
(2001:10:35:36::36/64) on its G0/0/0/0.3536.
(2001:10:35:36::35/64) on its G0/0/0/0.3536.
Ø XE-R22 is in BGP AS 2236.
Ø XR-R6 is in BGP AS 2236
Ø Establish E-BGP connectivity between customer and ISP-2
respective PE’s.
versa works.
Configuring 6VPE
ine.com
TASK 40
Ø ISP-2 has acquired a new customer “BLACK”.
Ø Customer “BLACK” has requested IPv4 and IPv6 connectivity
to its remote site.
Ø Configure XE-R22 with an IPv6 address set as
(2001:10:31:22::22/64) on its G1.3122.
(2001:10:31:22::31/64) on its G0/0/0/0.3122.
L3VPN Ø Configure XR-R6 with an IPv6 address set as
(2001:10:36:35::36/64) on its G0/0/0/0.3635.
(2001:10:36:35::35/64) on its G0/0/0/0.3635.
Ø XE-R22 is in BGP AS 2236.
Ø XR-R6 is in BGP AS 2236
Ø Establish E-BGP connectivity between customer and ISP-2
respective PE’s.
versa in VRF “BLACK” works.
Configuring MPLS L2VPN – Port Based
Point-to-Point Service
ine.com
TASK 41
Ø ISP-1 has acquired a new customer.
Ø Customer has requested IPv4 connectivity to its remote
site.
Ø However the customer wants a transparent connectivity to
its remote site.
Ø Configure OSPF Area 0 on XE-R14 and XE-R15. Advertise all
its interfaces in OSPF.
L2VPN Ø ISP-1 has decided to create a pseudowire between its PE’s
to meet the customer requirement.
ATOM
Ø Ensure XE-R14 and XE-R15 can establish OSPF adjacency
with each other.
versa works.
Configuring MPLS L2VPN – VPLS –
Multipoint Service
ine.com
TASK 42
Ø Customer (XE-R14 and XE-R15) has requested IPv4
connectivity to each other and its future remote sites.
Ø More sites are going to be added in the future to PE XE-
R2 and PE XE-R6.
Ø ISP-1 has decided to modify previous point-to-point
xconnects and extend multipoint connectivity over its
MPLS network.
L2VPN Ø Ensure XE-R14 and XE-R15 can establish OSPF adjacency
with each other.
VPLS
versa works.
Configuring MPLS L2VPN – H-VPLS –
Multipoint Service
ine.com
TASK 43
Ø Customer (XE-R14 and XE-R15) has requested IPv4
connectivity to each other and its future remote sites.
Ø More sites are going to be added in the future to PE XE-
R2 and PE XE-R6.
Ø ISP-1 has decided to extend multipoint connectivity over
its MPLS network.
Ø Configure XE-R4 as the HUB and XE-R(2/3/5/6) as spokes.
L2VPN Ø Ensure XE-R14 and XE-R15 can establish OSPF adjacency
with each other.
H-VPLS
versa works.
Configuring MPLS Traffic Engineering
with Dynamic Path – Part 1
ine.com
TASK 44
Ø Configure the core of the ISP-1 to support MPLS TE
tunnels as follows:
• Enable MPLS TE support for the OSPF area 0 core.
• Set the OSPF MPLS TE Router-ID to be the Loopback0 interfaces.
• Enable support for RSVP and MPLS TE on all transit interfaces
running OSPF in the core.
Ø Configure an MPLS TE tunnel from XE-R2 to XE-R(5/6) as
follows:
MPLS •
•
•
Unnumber the tunnel to XE-R2’s Loopback0 interface.
Set the tunnel destination as XE-R(5/6)’s Loopback0 interface.
Set the tunnel’s path option to dynamic.
TE Ø Configure an MPLS TE tunnel from XE-R3 to XE-R(5/6) as

follows:
• Unnumber the tunnel to XE-R3’s Loopback0 interface.
• Set the tunnel destination as XE-R(5/6)’s Loopback0 interface.
• Set the tunnel’s path option to dynamic.
ine.com
TASK 45
follows:
follows:
MPLS
TE
ine.com
TASK 46
Ø Configure the core of the ISP-2 to support MPLS TE
tunnels as follows:
• Enable MPLS TE support for the ISIS level 2 core.
• Set the ISIS MPLS TE Router-ID to be the Loopback0 interfaces.
• Enable support for RSVP and MPLS TE on all transit interfaces
running ISIS in the core.
Ø Configure an MPLS TE tunnel from XR-R1 to XR-R(4/5) as
follows:
MPLS •
•
•
Unnumber the tunnel to XR-R1’s Loopback0 interface.
Set the tunnel destination as XR-R(4/5)’s Loopback0 interface.
Set the tunnel’s path option to dynamic.
TE Ø Configure an MPLS TE tunnel from XR-R2 to XR-R(4/5) as

follows:
• Unnumber the tunnel to XR-R2’s Loopback0 interface.
• Set the tunnel destination as XR-R(4/5)’s Loopback0 interface.
ine.com
TASK 47
follows:
follows:
MPLS
TE
with Explicit Path – Part 1
ine.com
TASK 48
Ø Modify the MPLS TE in the core of the ISP-1
as follows:
• Set the tunnel’s path option to explicitly follow
the path from XE-R2 to XE-R4 to XE-R(5/6).
the path from XE-R3 to XE-R4 to XE-R(5/6).
MPLS • Set
the
the tunnel’s path option
path from XE-R5 to XE-R4
to
to
explicitly
XE-R(2/3).
follow

TE the path from XE-R6 to XE-R4 to XE-R(2/3).
with Explicit Path – Part 2
ine.com
TASK 49
Ø Modify the MPLS TE in the core of the ISP-2 as follows:
• Set the tunnel’s path option to explicitly follow the path from
XR-R1 to XR-R3 to XR-R(4/5).
• Configure Forwarding Adjacency on the tunnel so that the ISIS core
can use it for dynamic routing.
MPLS •
Set the tunnel’s path option to explicitly follow the path from
TE
with Bandwidth Reservation and Fast-
Reroute
ine.com
TASK 50
Ø Customers have requested ISP-1 and ISP-2 for
bandwidth reservation. Configure ISP-1 and ISP-2
as follows:
• Configure all routers in the core so that 750Mbps
can be reserved via RSVP on any of their interfaces.
• Links between “XE-R2 and XE-R5”, “XE-R3 and XE-R6”,
MPLS •
“XR-R1 and XR-R4”, and “XR-R2 and XR-R5” can reserve
a maximum of 100Mbps and per flow of 50Mbps.
Ensure all tunnels reserve a bandwidth of 50Mbps.
TE • XE-R2’s TE tunnel to XE-R5 should be Fast Rerouted
if the link between XE-R4 and XE-R5 is down.

CCIE SP v5

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CCIE SP v5

Uploaded by

Copyright:

Available Formats

CCIE Service Provider v5 Exam Review

ISIS • XR-R4 and XR-R5 should use NET addresses as

ISIS • XR-R1 must only leak L1 prefix (132.132.132.132/32) to its

ISIS Ø Configure ISIS level assignments as follows:

Routing Ø Ensure Segment Routing is preferred over LDP.

BGP Ø Create one new sub-interface on XE-R3 as follows:

BGP Ø Create one new sub-interface on XR-R5 as follows:

L3VPN Ø Establish E-BGP neighborship between XE-R20 and XE-R21 in

TE Ø Configure an MPLS TE tunnel from XE-R3 to XE-R(5/6) as

TE Ø Configure an MPLS TE tunnel from XR-R2 to XR-R(4/5) as

• Set the tunnel’s path option to explicitly follow

You might also like