Professional Documents
Culture Documents
Authored By:
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring OSPF
R1 R2
L0 1.1.1.1/8 L0 2.2.2.2/8
L0 192.1.100.0/24
R3
R4
R1
R2
R3
Task 1
Configure OSPF on a Broadcast Multi-Access(BMA) Ethernet network in Area 0.
Advertise all networks on all routers. Hard Code the Router-id based on the
following:
R1 – 11.11.11.11
R2 – 22.22.22.22
R3 – 33.33.33.33
R4 – 44.44.44.44
R1 R2
Task 2
Configure the routers such that R1 becomes the DR and R2 as the BDR on the
100 Network.
R1 R2
Note: Issue the Clear ip ospf process command to reset the OSPF process for
the change to take effect.
R1 Area 0
192.1.12.0/24
R2
3
R3 192.1.23.0/24
Area 10
192.1.34.0/24
R4
192.1.45.0/24
Area 20
R5
R1
R2
R3
R4
R5
Task 1
Run OSPF as your Routing Protocol on all Routers and the Switch. Advertise
the networks in the following areas:
R1
router ospf 1
router-id 1.1.1.1
network 1.0.0.0 0.255.255.255 area 0
network 192.1.12.0 0.0.0.255 area 0
R2
router ospf 1
router-id 2.2.2.2
network 2.0.0.0 0.255.255.255 area 0
network 192.1.12.0 0.0.0.255 area 0
network 192.1.23.0 0.0.0.255 area 10
area 10 virtual-link 4.4.4.4
R3
router ospf 1
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 10 of 311
router-id 3.3.3.3
network 3.0.0.0 0.255.255.255 area 10
network 192.1.23.0 0.0.0.255 area 10
network 192.1.34.0 0.0.0.255 area 10
R4
router ospf 1
router-id 4.4.4.4
network 4.0.0.0 0.255.255.255 area 100
network 192.1.34.0 0.0.0.255 area 10
network 192.1.45.0 0.0.0.255 area 100
area 10 virtual-link 2.2.2.2
R5
router ospf 1
router-id 5.5.5.5
network 5.0.0.0 0.255.255.255 area 100
network 192.1.45.0 0.0.0.255 area 100
Task 1
Configure the most secure authentication on all routers in Area's 0 and Area
100. Use a key of 1 and a key-string ccie.
R1
interface F 0/0
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ccie
R2
interface F 0/0
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ccie
!
router ospf 1
area 10 virtual-link 4.4.4.4 authentication message-digest
area 10 virtual-link 4.4.4.4 message-digest-key 1 md5 ccie
R4
interface F 0/1
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ccie
!
router ospf 1
area 10 virtual-link 2.2.2.2 authentication message-digest
area 10 virtual-link 2.2.2.2 message-digest-key 1 md5 ccie
R5
interface F 0/0
ip ospf authentication message-digest
ip ospf message-digest-key 1 md5 ccie
Task 2
Configure text authentication on all routers in 10. Use a key-string cisco.
R2
interface F 0/1
ip ospf authentication
ip ospf authentication-key cisco
interface F 0/0
ip ospf authentication
ip ospf authentication-key cisco
!
interface F 0/1
ip ospf authentication
ip ospf authentication-key cisco
R4
interface F 0/0
ip ospf authentication
ip ospf authentication-key cisco
R1
R2
3
OSPF
Area 0 192.1.23.0/24 192.1.34.0/24
R3 R4
192.1.35.0/24
192.1.46.0/24
OSPF OSPF
R5 Area 10 Area 20
R6
192.1.67.0/24
R7
RIPv2
192.1.78.0/24
R8
R2
R3
R4
R5
R7
R8
Task 1
Run EIGRP as your Routing Protocol on R1 & R2. Advertise all interfaces on
R1under EIGRP. Advertise the 22.0.0.0/8 and 192.1.12.0/24 networks under
EIGRP on R2.
R1
R2
router ospf 1
router-id 2.2.2.2
network 2.0.0.0 0.255.255.255 area 0
network 192.1.23.0 0.0.0.255 area 0
network 192.1.24.0 0.0.0.255 area 0
!
Int Loopback 0
Ip ospf network point-to-point
R3
router ospf 1
router-id 3.3.3.3
network 3.0.0.0 0.255.255.255 area 0
network 33.0.0.0 0.255.255.255 area 10
network 192.1.23.0 0.0.0.255 area 0
network 192.1.35.0 0.0.0.255 area 10
!
!
Int Loopback 0
Ip ospf network point-to-point
!
Int Loopback 1
Ip ospf network point-to-point
R4
router ospf 1
router-id 4.4.4.4
network 4.0.0.0 0.255.255.255 area 0
network 44.0.0.0 0.255.255.255 area 20
network 192.1.24.0 0.0.0.255 area 0
network 192.1.46.0 0.0.0.255 area 20
router ospf 1
router-id 5.5.5.5
network 5.0.0.0 0.255.255.255 area 10
network 55.0.0.0 0.255.255.255 area 10
network 192.1.35.0 0.0.0.255 area 10
!
Int Loopback 0
Ip ospf network point-to-point
!
Int Loopback 1
Ip ospf network point-to-point
R6
router ospf 1
router-id 6.6.6.6
network 6.0.0.0 0.255.255.255 area 20
network 66.0.0.0 0.255.255.255 area 20
network 192.1.46.0 0.0.0.255 area 20
network 192.1.67.0 0.0.0.255 area 20
!
!
Int Loopback 0
Ip ospf network point-to-point
!
Int Loopback 1
Ip ospf network point-to-point
R7
router ospf 1
router-id 7.7.7.7
network 7.0.0.0 0.255.255.255 area 20
network 192.1.67.0 0.0.0.255 area 20
!
Int Loopback 0
Ip ospf network point-to-point
R7 R8
Task 4
Configure Redistribution on the appropriate routers such that all networks are
reachable.
R2
Router rip
Redistribute ospf 1 metric 1
!
Router ospf 1
Redistribute rip subnets
Task 5
Create the following Loopbacks on R5:
Advertise these newly created loopbacks in OSPF. Make sure it uses the
Interface mask in the advertisement.
interface Loopback101
ip address 205.1.4.1 255.255.255.0
ip ospf network point-to-point
!
interface Loopback102
ip address 205.1.5.1 255.255.255.0
ip ospf network point-to-point
!
interface Loopback103
ip address 205.1.6.1 255.255.255.0
ip ospf network point-to-point
!
interface Loopback104
ip address 205.1.7.1 255.255.255.0
ip ospf network point-to-point
!
router ospf 1
network 205.1.4.0 0.0.0.255 area 10
network 205.1.5.0 0.0.0.255 area 10
network 205.1.6.0 0.0.0.255 area 10
network 205.1.7.0 0.0.0.255 area 10
Task 6
Summarize the 205.1.X.0 networks such that only the summary route is sent
out of Area 10.
R3
router ospf 1
area 10 range 205.1.4.0 255.255.252.0
Task 7
Create the following Loopbacks on R1:
interface Loopback101
ip address 201.1.4.1 255.255.255.0
!
interface Loopback102
ip address 201.1.5.1 255.255.255.0
!
interface Loopback103
ip address 201.1.6.1 255.255.255.0
!
interface Loopback104
ip address 201.1.7.1 255.255.255.0
!
router eigrp 100
network 201.1.4.0
network 201.1.5.0
network 201.1.6.0
network 201.1.7.0
Task 8
Summarize the 201.1.X.0 networks such that only the summary route is sent
into the OSPF Domain
R2
router ospf 1
summary-address 201.1.4.0 255.255.252.0
Task 9
Configure LSA Filtering such that network 66.0.0.0/8 is not allowed to leave
Area 20.
R2
Task 1
Configure Area 10 such that it does not receive any External Routes. It should
maintain connectivity to the External Routes. (Stub Area)
R3
Router ospf 1
Area 10 stub
R5
Router ospf 1
Area 10 stub
Note: The ABR will block the External Routes from EIGRP & RIPv2
from reaching R5. Instead R3 will inject a default route instead.
This is a Stub Area. Verify it on R5 by checking the Routing table.
Task 2
This step is a continuation of Task 1. Configure Area 10 Also blocks Inter-Area
routes maintaining reachability to them. (Totally Stubby Area)
R3
Router ospf 1
Area 10 stub no-summary
Note: The ABR will block the Inter-Area Routes from getting
propagating into Area 10(R5). Instead R3 will inject a default route
instead. This is a Totally Stubby Area. Verify it on R5 by checking
the Routing table.
Task 3
Configure Area 20 such that it does not receive any external routes from the
backbone. The External routes from RIPv2 should continue to be received in
Area 20 and propagated into the Backbone. (NSSA Area)
R4
Router ospf 1
Area 20 nssa
R6
Router ospf 1
Area 20 nssa
Note: The ABR will block the External routes from the Backbone
(EIGRP). Area 20 will continue to receive the external routes from
RIPv2 as N routes. These routes will continue to be propagated
towards the backbone. The ABR will convert the N routes into E
routes as it propagates it into the Backbone. You will receive
reachability to the External Routes from the Backbone as the ABR
does not inject a default route in this configuration.
Task 4
This step is a continuation of Task 3. Configure Area 20 such that the previous
requirement is maintained but Area 20 should have reachability to the external
routes from the backbone (EIGRP Routes). (NSSA-Stub Area)
R3
Router ospf 1
Area 10 stub default-information-originate
Note: This builds on the NSSA area by regaining reachability to the
Backbone external routes. This is done by having the ABR injecting
the default route into Area 20.
Task 5
Configure Area 20 such that the Inter-Area routes are also blocked in addition
to the external routes from the backbone. (NSSA-Totally Stubby Area)
R3
Router ospf 1
Area 10 stub no-summary
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring IS-IS
R1 R2
192.1.12.0/24
192.1.23.0/24
192.1.34.0/24
R4 R3
R1
R2
R3
R4
Task 1
Configure IS-IS on all 4 routers in a single Area 49.0000. User
XXXX.XXX.XXXX as the System ID. Advertise all the Loopbacks in IS-IS. Make
sure that the Routers only establish L1 Adjacencies with each other.
R1 R2
Task 2
Make sure the R1 and R3 are the DIS for their respective Multi-Access
Segments.
R2 R4
Task 3
Configure the Hello between R2 and R3 to be 5 seconds with a dead timer of 15
seconds
R2 R3
Task 4
Configure all the Routers such that MPLS-TE is supported on them.
R1 R2
Task 1
Configure MD5 authentication for the Link between R1 & R2. Use ccie as the
key-string with a key-id of 1.
R1
Task 2
Configure Text authentication for the Link between R3 & R4. Use ccie as the
key-string with a key-id of 1.
R3
49.0010 R1 R2
R5
49.000
R6
49.0020 R4 R3
R1
R2
R3
R5
R6
Task 1
Configure IS-IS on all 6 routers in the appropriate areas based on the Diagram.
User XXXX.XXX.XXXX as the System ID. Advertise all the Loopbacks in IS-IS.
R1 R2
Task 2
Make R5 and R6 are L1 routers only. Configure R1 & R4 to accommodate this
configuration.
R1 R4
R2 R3
Task 1
Configure Area's 49.0010 & 49.0020 to receive all routes from all areas.
R1
(Builds on Lab 4)
Task 1
Configure Area 49.0010 such that all the 201.1.X.0 routes are summarized out
of the area.
R2
router isis
summary-address 201.1.4.0 255.255.252.0
Task 2
Configure Area 49.0020 such that all the 201.1.X.0 routes are summarized out
of the area.
R2
router isis
summary-address 204.1.4.0 255.255.252.0
OSPF Area 0 R1
R5
R2
R3
RIPv2 R4
R1
R2
R3
R5
R6
Task 1
Configure IS-IS on the appropriate routers based on the Diagram. Use
XXXX.XXX.XXXX as the System ID. Advertise all the Loopbacks in IS-IS.
Establish a L2 Adjacency only.
R2 R3
Task 2
Configure OSPF between R1, R2 & R5 based on the diagram. Advertise all the
networks on R1 and R5 in OSPF. Only enable the link between R1 & R2 under
R1 R2
Router OSPF 1
Router-id 1.1.1.1
Network 192.1.15.0 0.0.0.255 area 0
Network 5.0.0.0 0.255.255.255 area 0
!
Int loo 0
Ip ospf network point-to-point
Task 3
Configure RIPv2 between R3, R4 & R6 based on the diagram. Advertise all the
networks on R4 and R6 in RIPv2. Only enable the link between R3 & R4 under
RIPv2 on R3.
R3 R4
Router RIP
No auto-summary
Version 2
Network 192.1.46.0
Network 6.0.0.0
Task 4
Configuring Mutual redistribution between IS-IS & OSPF.
R2
Router isis
Redistribute ospf 1
!
Router ospf 1
Redistribute isis subnets
Task 5
Configuring Mutual redistribution between IS-IS & RIPv2.
R3
Router isis
Redistribute rip
!
Router rip
Redistribute isis metric 1
R2
Task 7
Re-configure the redistribution between OSPF & IS-IS such that the 204.1.4.0
networks are not injected into OSPF.
R3
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020
Configuring BGP
Loopback 0 R1 R2
Loopback 0
F 0/0 F 0/0
Loopback 1 Loopback 1
S 0/0
Loopback 0 Loopback 0
F 0/0 F 0/0
R4 R3
AS 1 AS 2
R2
R1
R4
R3
AS 4 AS 3
R1
R2
R3
R4
Task 1
Configure a BGP neighbor relationship between R1 and R2. R1 should be in AS
1 and R2 should be in AS 2. Advertise the loopback networks in BGP. Hard-
code the Router ID for the BGP routers as 11.11.11.11 for R1 and 22.22.22.22
for R2.
R1 R2
Task 2
Configure a BGP neighbor relationship between R2 and R3. R2 should already
be configured in AS 2 and R3 should be in AS 3. Advertise the loopback
network of R3 in BGP. Hard-code the Router ID for R3 as 33.33.33.33
R2 R3
Task 3
Configure a BGP neighbor relationship between R3 and R4. R3 should already
be configured in AS 3 and R4 should be in AS 4. Advertise the loopback
network of R4 in BGP. Hard-code the Router ID for R4 as 44.44.44.44.
Establish the neighbor relationship based on Loopback 0 addresses. You are
allowed to create a static route on each router to accomplish this task.
R3 R4
Task 1
Configure MD5 Authentication between R1 and R2 using a password of cciers.
R1 R2
Task 2
Configure MD5 Authentication between R2 and R3 using a password of
cciesec.
R2 R3
Task 3
Configure MD5 Authentication between R3 and R4 using a password of cciers.
R3 R4
R1 192.1.12.0/24 R2 L0 2.2.2.2/8
L0 1.1.1.1/8 S 0/0(.1)
S 0/0
(.2)
L1 12.1.0.1/16
F 0/0 (.2)
R5 192.1.23.0/24
L0 4.4.4.4/8 L1 13.1.0.1/16
R4 R3
R3
AS 5
AS 1
AS 234
R1 R2 R4 R5
R1
R2
R3
R4
R5
Task 1
Configure a neighbor relationship between R1 and R2 based on the Logical
diagram. Advertise the Loopback networks on both Routers. Hard-code the
Router ID for the BGP routers as 11.11.11.11 for R1 and 22.22.22.22 for R2.
Task 2
Configure EIGRP in AS 234 as the routing protocol within AS 234. Only
advertise the internal physical link in EIGRP on R2, R3 and R4. Do not
advertise the 192.1.12.0 and the 192.1.45.0 networks in EIGRP.
R2 R3
Task 3
Configure neighbor relationships between R2 and R3 and another one between
R3 and R4. Do not configure a neighbor relationship between R2 and R4.
Advertise the Loopback networks under BGP. Make sure routes from R1 can
get propagated to R3 and R4. Do not use a Confederation to accomplish this.
R2
Task 4
Configure a neighbor relationship between R4 and R5 based on the Logical
diagram. Advertise the Loopback network on R5 in BGP. Hard-code the Router
ID for R5 as 55.55.55.55.
R4 R5
Task 1
Create the following Loopbacks on R2
Loopback 1 – 192.2.1.1/24
Loopback 2 – 192.2.2.1/24
Loopback 3 – 192.2.3.1/24
Loopback 4 – 192.2.4.1/24
Loopback 5 – 192.2.5.1/24
Loopback 6 – 192.2.6.1/24
Loopback 7 – 192.2.7.1/24
Loopback 8 – 192.2.8.1/24
R2
interface Loopback1
ip address 192.2.1.1 255.255.255.0
!
interface Loopback2
ip address 192.2.2.1 255.255.255.0
!
interface Loopback3
ip address 192.2.3.1 255.255.255.0
!
interface Loopback4
ip address 192.2.4.1 255.255.255.0
!
interface Loopback5
ip address 192.2.5.1 255.255.255.0
!
interface Loopback6
ip address 192.2.6.1 255.255.255.0
!
interface Loopback7
ip address 192.2.7.1 255.255.255.0
!
interface Loopback8
ip address 192.2.8.1 255.255.255.0
R2
Task 3
Configure R2 such that it blocks all the 192.2.X.0 routes that have an odd
number in the third octet from propagating outside the local AS. Use the
distribute-list command to accomplish this task.
R2
Task 4
Configure R4 such that it blocks all the 192.2.X.0 routes that have an even
number in the third octet from coming in. Make sure that even if in the future
that a neighbor relationship is established between R2 and R4 these routes
don’t come into R4. Use the distribute-list command to accomplish this task.
R4
Task 1
Create the following Loopbacks on R3
Loopback 1 – 150.3.16.1/20
Loopback 2 – 150.3.36.1/22
Loopback 3 – 150.3.40.1/22
Loopback 4 – 150.3.50.1/23
Loopback 5 – 150.3.65.1/24
Loopback 6 – 150.13.0.1/16
Loopback 7 – 150.14.64.1/18
R3
interface Loopback1
ip address 150.3.16.1 255.255.240.0
!
interface Loopback2
ip address 150.3.36.1 255.255.252.0
!
interface Loopback3
ip address 150.3.40.1 255.255.252.0
!
interface Loopback4
ip address 150.3.50.1 255.255.254.0
!
interface Loopback5
ip address 150.3.65.1 255.255.255.0
!
interface Loopback6
ip address 150.13.0.1 255.255.0.0
!
interface Loopback7
ip address 150.14.64.1 255.255.192.0
Task 2
Advertise the newly created routes in BGP using the Network command.
R3
Task 3
Configure R2 such that it blocks all the 150.X.X.0 routes that have a subnet
mask between 17 and 23 bits.
R2
R1 192.1.12.0/24 R2 L0 2.2.2.2/8
L0 1.1.1.1/8 S 0/0(.1)
S 0/0
(.2)
L1 12.1.0.1/16
F 0/0 (.2)
R5 192.1.23.0/24
L0 4.4.4.4/8 L1 13.1.0.1/16
R4 R3
R3
AS 5
AS 1
AS 234
R1 R2 R4 R5
R2
R3
R4
R5
Task 1
Configure a neighbor relationship between R1 and R2 based on the Logical
diagram. Advertise the Loopback networks on both Routers. Hard-code the
Router ID for the BGP routers as 11.11.11.11 for R1 and 22.22.22.22 for R2.
R1 R2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 56 of 311
Router BGP 1 Router BGP 234
bgp router-id 11.11.11.11 bgp router-id 22.22.22.22
Network 1.0.0.0 Network 2.0.0.0
Neighbor 192.1.12.2 remote-as 234 Network 12.1.0.0 mask 255.255.0.0
Neighbor 192.1.12.1 remote-as 1
Task 2
Configure EIGRP in AS 234 as the routing protocol within AS 234. Only
advertise the internal physical link in EIGRP on R2, R3 and R4. Do not
advertise the 192.1.12.0 and the 192.1.45.0 networks in EIGRP.
R2 R3
Task 3
Configure neighbor relationships between R2 and R3 and another one between
R3 and R4. Do not configure a neighbor relationship between R2 and R4.
Advertise the Loopback networks under BGP. Make sure routes from R1 can
get propagated to R3 and R4. Do not use a Confederation to accomplish this.
R2
Task 4
Configure a neighbor relationship between R4 and R5 based on the Logical
diagram. Advertise the Loopback network on R5 in BGP. Hard-code the Router
ID for R5 as 55.55.55.55.
R4 R5
Task 5
Configure BGP such that AS 5 does not use AS 234 as a transit AS.
Configuration should be done in AS 5.
R5
Task 6
Configure BGP such that AS 1 does not use AS 234 to get AS 5 routes.
Configuration should be done in AS 234. You are only allowed a single line in
the AS-path filter.
R2
Task 1
Create the following Loopbacks on R3 and advertise them under BGP:
Loopback 1 – 203.1.4.1/24
Loopback 2 – 203.1.5.1/24
Loopback 3 – 203.1.6.1/24
Loopback 4 – 203.1.7.1/24
R3
interface Loopback1
ip address 203.1.4.1 255.255.255.0
!
interface Loopback2
ip address 203.1.5.1 255.255.255.0
!
interface Loopback3
ip address 203.1.6.1 255.255.255.0
!
interface Loopback4
ip address 203.1.7.1 255.255.255.0
!
Router BGP 234
Network 203.1.4.0
Network 203.1.5.0
Network 203.1.6.0
Network 203.1.7.0
Task 2
Configure Route Aggregation on R3 such that these routes are summarized as
a single route. Only the Summary route should be send to R3’s neighbors.
R3
Task 3
Create the following Loopbacks on R4 and advertise them under BGP:
R4
interface Loopback1
ip address 204.1.4.1 255.255.255.0
!
interface Loopback2
ip address 204.1.5.1 255.255.255.0
!
interface Loopback3
ip address 204.1.6.1 255.255.255.0
!
interface Loopback4
ip address 204.1.7.1 255.255.255.0
!
Router BGP 234
Network 204.1.4.0
Network 204.1.5.0
Network 204.1.6.0
Network 204.1.7.0
Task 4
Configure Route Aggregation on R4 such that these routes are summarized as
a single route. Only the Summary route should be send to R4’s neighbor. The
routes should not be seen as suppressed on R4. Use the minimum number of
lines in your filtering mechanism.
R4
Task 5
Create the following Loopbacks on R2 and advertise them under BGP:
R2
interface Loopback1
ip address 202.1.4.1 255.255.255.0
!
interface Loopback2
ip address 202.1.5.1 255.255.255.0
!
interface Loopback3
ip address 202.1.6.1 255.255.255.0
!
interface Loopback4
ip address 202.1.7.1 255.255.255.0
!
Router BGP 234
Network 202.1.4.0
Network 202.1.5.0
Network 202.1.6.0
Network 202.1.7.0
Task 6
Configure Route Aggregation on R2 such that these routes are summarized as
a single route. Only the Summary route and the 202.1.5.0 route should be
send to R2’s neighbor.
R2
Loopback 0 R1 R2
Loopback 0
F 0/0 F 0/0
Loopback 1 Loopback 1
S 0/0
Loopback 0 Loopback 0
F 0/0 F 0/0
R4 R3
R2
AS 65002
AS 4
AS 123
R1 R3 R4
AS 65003
AS 65001
R1
R2
R3
R4
Task 1
Configure RIP V2 as the routing protocol between R1, R2 and R3. Only
advertise the R1-R2 and R2-R3 links in RIP on the appropriate routers.
R1 R2
Router RIP
Task 2
Configure AS 65001, AS 65002 and AS 65003 are Sub Autonomous Systems of
a Larger AS 123 using Confederations. Advertise the Loopback 0 networks
under BGP in AS 65001, AS 65002 and AS 65003. Configure a Neighbor
relationship between AS 65001 and AS 65002 and another Neighbor
relationship between AS 65002 and AS 65003.
R1 R2
Task 3
Configure a neighbor relationship between R3 and R4. R4 is in AS 4. It peers
with R3 in the confederation AS 123. Advertise the loopback 0 interface under
BGP in AS 4.
R3
Router BGP 4
Network 4.0.0.0
Neighbor 192.1.34.3 remote-as 123
Loopback 0 R1 R2
Loopback 0
F 0/0 F 0/0
Loopback 1 Loopback 1
S 0/0 S 0/0
Loopback 0 Loopback 0
F 0/0 F 0/0
R4 R3
R2
AS 1
AS 234
R3
R1
R4
R1
R2
R3
R4
Task 1
Run RIP V2 as the IGP in AS 234. Advertise the directly connected links under
RIP. Do not advertise the external links (192.1.12.0, 192.1.14.0) or the
Loopbacks in RIP.
R2 R3
Task 2
Configure the routers under BGP based on the Logical diagram. Configure the
Neighbor relationships also based on the Logical diagram. Advertise Loopback
0 Networks on all routers under BGP. Make sure the 1.0.0.0 gets put into the
routing table of R3. Also make sure that Routes from R2 are getting propagated
to R4 and vice versa.
R1 R2
R2
Task 1
Configure AS 234 such that all traffic destined for AS 1 should go through R2
in the outbound direction.Use Local-Preference Attribute to accomplish this.
R2
Task 1
Configure AS 234 such that all traffic originating from R4 and destined for AS1
should go directly from R4 to R1 instead of using R2. Make sure this
configuration does not affect the traffic flow for the rest of the AS.
R4
Task 2
Configure AS 1 such that all traffic destined for network 3.0.0.0 should go thru
R2. It is taking the R1-R4 route because of the MED attribute set in Lab 9. Use
the Weight attribute to accomplish this task.
R1
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring IPv6
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 3 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Task 1
Enable IPv6 routing on R1,R2, R3 and R4. Assign IPv6 addresses to the F 0/0
interface of the routers as follows:
✓ R1 – FD00:192:1:12::1 /64
✓ R2 – FD00:192:1:12::2 /64
✓ R3 – FD00:192:1:34::3 /64
✓ R4 – FD00:192:1:34::4 /64
R1 R2
✓ R1 – Loopback0 – FD00:1:1:1::1/64
✓ R2 – Loopback0 – FD00:2:2:2::2/64
✓ R3 – Loopback0 – FD00:3:3:3::3/64
✓ R4 – Loopback0 – FD00:4:4:4::4/64
R1
Interface Loopback 0
Ipv6 address FD00:1:1:1::1/64
R2
Interface Loopback 0
ipv6 address FD00:2:2:2::2/64
R3
Interface Loopback 0
Ipv6 address FD00:3:3:3::3/64
R4
Interface Loopback 0
ipv6 address FD00:4:4:4::4/64
Task 3
Configure the Serial Link between R2 and R3 using the folloing IPV6 addresses:
✓ R2 – FD00:192:1:23::2/64
✓ R3 – FD00:192:1:23::3/64
R2
Interface S0/0
ipv6 address FD00:192:1:23::2/64
no shut
R3
Interface S0/0
ipv6 address FD00:192:1:23::3/64
no shut
Task 4
✓ R1 – F 0/0, Loopback 0
✓ R2 – F 0/0, Loopback 0, S 0/0
✓ R3 – F 0/0, Loopback 0, S 0/0
✓ R4 – F 0/0, Loopback 0
R1 R2
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 3 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Task 1
Disable RIP NG on all routers on all interfaces.
R1 R2
✓ R1 – 1.1.1.1
✓ R2 – 2.2.2.2
✓ R3 – 3.3.3.3
✓ R4 – 4.4.4.4
R1 R2
Task 3
Authenticate the EIGRP Neighbor relationships using MD5 authentication. Use
Cisco as the Key with a key-id of 100.
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 3 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Task 1
Disable EIGRP on all routers on all interfaces. Disable the protocol on the
router as well.
R1 R2
Task 2
Configure the routers in OSPFv3 area 0 and advertise their directly connected
interfaces in this area. Configure the OSPF Router-id’s as follows:
✓ R1 – 1.1.1.1
✓ R2 – 2.2.2.2
✓ R3 – 3.3.3.3
✓ R4 – 4.4.4.4
R1 R2
Task 3
Ensure that the loopback interfaces are advertised with their correct mask.
R3 R4
Task 4
Authenticate & encrypt the OSPF neighbor relationships between R1 and R2
using the following parameters:
➢ Encryption
o IPSec
o SPI : 1234
o Encryption Scheme : 3des
o Key : 123456789ABC123456789ABC123456789ABC123456789ABC
➢ Authentication
o MD5
o Key : 12345678123456781234567812345678
R1
Interface F 0/0
ipv6 ospf encryption ipsec spi 1234 esp 3des
123456789ABC123456789ABC123456789ABC123456789ABC md5
12345678123456781234567812345678
R2
Interface F 0/0
ipv6 ospf encryption ipsec spi 1234 esp 3des
123456789ABC123456789ABC123456789ABC123456789ABC md5
12345678123456781234567812345678
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 3 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
FD00:192:1:23::/64
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Task 1
Disable OSPF on all routers on all interfaces. Disable the protocol on the router
as well.
R1 R2
Task 2
Configure the routers in IS-IS area 49.0000 and advertise their directly
connected interfaces in this area. Use xxxx.xxxx.xxxx as the system ID. Make
sure that the neighbor establish a Level-1 adjacency only.
R1 R2
Task 3
Authenticate the IS-IS neighbor relationships between R1 and R2 using MD5
authentication. Use a Key of 1 and a key string of cisco.
Loppback 0 R1 R2 Loppback 0
FD00:1:1:1::1/64 F 0/0 F 0/0 3 FD00:2.2.2::2/64
FD00:192:1:12::/64
S 0/0
192.1.23.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
Task 1
Enable IPv6 routing on R1,R2, R3 and R4. Assign IPv6 addresses to the F 0/0
interface of the routers as follows:
✓ R1 – FD00:192:1:12::1 /64
✓ R2 – FD00:192:1:12::2 /64
✓ R3 – FD00:192:1:34::3 /64
✓ R4 – FD00:192:1:34::4 /64
R1 R2
Task 2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 84 of 311
Configure the Loopback0 interface on all routers as follows:
✓ R1 – Loopback0 – FD00:1:1:1::1/64
✓ R2 – Loopback0 – FD00:2:2:2::2/64
✓ R3 – Loopback0 – FD00:3:3:3::3/64
✓ R4 – Loopback0 – FD00:4:4:4::4/64
R1
Interface Loopback 0
Ipv6 address FD00:1:1:1::1/64
R2
Interface Loopback 0
ipv6 address FD00:2:2:2::2/64
R3
Interface Loopback 0
Ipv6 address FD00:3:3:3::3/64
R4
Interface Loopback 0
ipv6 address FD00:4:4:4::4/64
Task 3
Configure RIPng on all routers to route all loopbacks. Enable RIPng under the
following interfaces:
✓ R1 – F 0/0, Loopback 0
✓ R2 – F 0/0, Loopback 0
✓ R3 – F 0/0, Loopback 0
✓ R4 – F 0/0, Loopback 0
R1 R2
R3 R4
Task 4
Configure the Serial Link between R2 and R3 using the folloing IPv4 addresses:
✓ R2 – 192.1.23.2/24
✓ R3 – 192.1.23.3/24
R2
Interface S0/0
ip address 192.1.23.2 255.255.255.0
clock rate 1000000
no shut
R3
Interface S0/0
Ip address 192.1.23.3 255.255.255.0
no shut
Task 5
Create a Tunnel between R2 and R3 Assign it an IPv6 address of
FD00:192:1:23::/64. Set the Tunnel Mode to IPv6. Enable RIPng on the Tunnel
Interface to connect the 2 discontiguous RIP networks.
R2 R3
AS 100 R1
2000:192:1:12::/64
R2
AS 200
FC00:192:1:23::/64 FC00:192:1:23::/64
R3 R4
2000:192:1:35::/64 2000:192:1:46::/64
R5 R6
AS 500 AS 600
R1
R3
R4
R5
R6
R2 R3
Router isis
Net 49.0000.4444.4444.4444.00
Is-type level-1
!
Interface Loopback10
ipv6 router isis
!
Interface F 0/0
ipv6 router isis
Task 2
Configure iBGP in AS 200. Configure the neighbor relationships between R2 -
R3 & R2 - R4. Do not configure a neighbor relationship between R2 & R4. Set
the relationship with redundancy in mind. Advertise Loopback 0 networks
under BGP on these routers. Make sure that routes from R3 will get propagated
towards R4 and vice-versa.
R2
R4
R2
R3
R4
Task 1
Configure a eBGP neighbor relationship between AS 100 & AS 200. Make sure
that the routes from AS 100 gets propagated towards R3 & R4. All Loopback 0
Routes from AS 100 should be reachable from AS 200 and vice-versa.
R1
Task 2
Configure a eBGP neighbor relationship between AS 200 & AS 500. Make sure
that the routes from AS 100 gets propagated towards AS 500 and vice-versa.
All Loopback 0 Routes from AS 100 should be reachable from AS 500 and vice-
versa.
R3
Task 3
Configure a eBGP neighbor relationship between AS 200 & AS 600. Make sure
that the routes from AS 100 & AS 500 gets propagated towards AS 600 and
vice-versa. All Loopback 0 Routes from AS 100 & AS 500 should be reachable
from AS 600 and vice-versa.
R4
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring BFD
R1
OSPF Area 0
R2
BGP 100
R4
R5
R3
R1
R2
R3
R5
Task 1
Configure OSPF between R1 & R2 based on the diagram. Advertise all the
Loopback networks on R1 and R2 in OSPF. Set the Router ID's based on the
X.X.X.X format (X is the Router Number). Make sure the loopbacks are
advertised with the Interface masks.
R1 R2
Task 2
Configure BGP between R2 & R3 in AS 100. Mutually redistribute OSPF & BGP
on R2. Make sure OSPF routes are reachable from R3.
R2 R3
R3 R4
Task 4
Configure IS-IS between R4 & R5 based on the diagram. Use XXXX.XXX.XXXX
as the System ID. Advertise all the Loopbacks on R5 in IS-IS. Establish a L2
Adjacency only. Mutually Redistribute EIGRP & IS-IS on R4.
R4 R5
Task 1
Configure BFD between R1 & R2. Use .5 secs for the Interval and Min_rx
parameters. Set the hold time at 1.5 secs. Enable OSPF to use BFD for
convergence & re-convergence
R1
Interface F 0/0
bfd interval 500 min_rx 500 multiplier 3
!
Router ospf 1
bfd all-interfaces
R2
Interface F 0/0
bfd interval 500 min_rx 500 multiplier 3
!
Router ospf 1
bfd all-interfaces
Task 2
Configure BFD between R2 & R3. Use .5 secs for the Interval and Min_rx
parameters. Set the hold time at 1.5 secs. Enable BGP to use BFD for
convergence & re-convergence
R2
Interface S 0/0
bfd interval 500 min_rx 500 multiplier 3
!
router bgp 100
neighbor 192.1.23.3 fall-over bfd
R3
Interface S 0/0
bfd interval 500 min_rx 500 multiplier 3
!
router bgp 100
Task 3
Configure BFD between R3 & R4. Use .5 secs for the Interval and Min_rx
parameters. Set the hold time at 1.5 secs. Enable EIGRP to use BFD for
convergence & re-convergence
R3
Interface F 0/0
bfd interval 500 min_rx 500 multiplier 3
!
Router eigrp 100
bfd interface F 0/0
R4
Interface F 0/0
bfd interval 500 min_rx 500 multiplier 3
!
Router eigrp 100
bfd interface F 0/0
Task 4
Configure BFD between R4 & R5. Use .5 secs for the Interval and Min_rx
parameters. Set the hold time at 1.5 secs. Enable IS-IS to use BFD for
convergence & re-convergence
R4
Interface F 0/1
bfd interval 500 min_rx 500 multiplier 3
!
Router isis
bfd all-interfaces
R5
Interface F 0/1
bfd interval 500 min_rx 500 multiplier 3
!
Router isis
bfd all-interfaces
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Multicast Routing
R2
R1 3
192.1.12.0/24
R1
R2
Task 1
Configure PIM dense mode on the routers.
R1 R2
Ip multicast-routing Ip multicast-routing
Task 2
R1 R2
R2
R1 3
192.1.12.0/24
R1
R2
Task 1
Configure EIGRP in AS 100 on both routers and advertise your directly
connected interfaces.
R1 R2
Task 2
Configure R1 to be the RP for all groups. Use the most reliable interface.
R1 R2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 103 of 311
Interface loopback0 Ip multicast-routing
Ip pim sparse-mode
Ip pim rp-address 1.1.1.1
Ip multicast-routing
Int F 0/0
Ip pim rp-address 1.1.1.1 Ip pim sparse-mode
Int Loopback 0
Ip pim sparse-mode
Task 3
Have Loopback 0 to join the multicast group 224.12.3.53
R2
Int Loopback 0
Ip igmp join-group 224.12.3.53
R1 R2
Lo 0 F 0/0 F 0/0 3 Lo 0
192.1.12.0/24 F 0/1
192.1.23.0/24
F 0/1
192.1.34.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
R1
R2
R3
Task 1
Configure EIGRP 100 on all routers and advertise all the directly connected
networks.
R1 R2
Task 2
Configure R1 to be the RP for Multicast groups 224.1.1.1 – 2, and R4 to be the
RP for the groups 224.4.4.1 – 2. These two RPs should use their Loopback 0
interface for this purpose.
R1 R2
Ip multicast-routing Ip multicast-routing
! !
Ip pim rp-address 1.1.1.1 10 Ip pim rp-address 1.1.1.1 10
Ip pim rp-address 4.4.4.4 20 Ip pim rp-address 4.4.4.4 20
! !
Access-list 10 permit 224.1.1.1 Access-list 10 permit 224.1.1.1
Access-list 10 permit 224.1.1.2 Access-list 10 permit 224.1.1.2
! !
Access-list 20 permit 224.4.4.1 Access-list 20 permit 224.4.4.1
Access-list 20 permit 224.4.4.2 Access-list 20 permit 224.4.4.2
R3 R4
Task 3
Configure R1 Loopback 0 and R4 loopback to to join the following Multicast
groups:
R1 R4
Task 4
Configure PIM on the physical and loopback interfaces in such a way that all
routers have access to all the multicast groups, including the ones that are not
configured for RP’s.
R1 R2
R1 R2
Lo 0 F 0/0 F 0/0 3 Lo 0
192.1.12.0/24 F 0/1
192.1.23.0/24
F 0/1
192.1.34.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
R1
R2
R3
Task 1
Configure EIGRP 100 on all routers and advertise all the directly connected
networks.
R1 R2
Task 2
Configure IP Multicast Sparse Mode on all interface on all Routers. Configure
R2 Loopback0 to be the RP for multicast groups 224.3.3.1 and 224.3.3.2 only.
Ensure that is sends its RP-announcements every 10 seconds with a TTL of 5.
Do not configure any Static RP on any router. R1 should join the multicast
groups 224.3.3.1 and 224.3.3.2 on the F 0/0 interface. All multicast routers
should be able to ping all R3 multicast routes.
R2
Interface loopback 0
Ip pim sparse-mode
Ip multicast-routing
Ip pim autorp listener
!
access-list 1 permit 224.3.3.1
access-list 1 permit 224.3.3.2
!
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 109 of 311
Ip pim send-rp-announce loopback0 scope 5 group-list 1 interval 10
Ip pim send-rp-discovery scope 5
!
Interface F 0/1
Ip pim sparse-mode
!
Interface F 0/0
Ip pim sparse-mode
R1 R3
Ip multicast-routing Ip multicast-routing
Ip pim autorp listener Ip pim autorp listener
! !
Interface loopback 0 Interface F 0/1
Ip pim sparse-mode Ip pim sparse-mode
! !
Interface F 0/0 Interface F 0/0
Ip pim sparse-mode Ip pim sparse-mode
Ip igmp join-group 224.3.3.1 !
Ip igmp join-group 224.3.3.2 Interface Loopback0
Ip pim sparse-mode
R4
Ip multicast-routing
Ip pim autorp listener
!
Interface loopback 0
Ip pim sparse-mode
!
Interface F 0/0
Ip pim sparse-mode
R1 R2
Lo 0 F 0/0 F 0/0 3 Lo 0
192.1.12.0/24 F 0/1
192.1.23.0/24
F 0/1
192.1.34.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
R1
R2
R3
Task 1
Configure EIGRP in AS 100 on all routers and advertise all the directly
connected networks.
R1 R2
Task 2
Configure IP Multicast Sparse Mode on all interfaces on all routers. Configure
R2 Loopback0 to be the RP for multicast groups 224.3.3.1 and 224.3.3.2 only
using BSR. Ensure that is sends its RP-announcements every 10 seconds.
R2
Interface loopback 0
Ip pim sparse-mode
Ip multicast-routing
!
access-list 1 permit 224.3.3.1
access-list 1 permit 224.3.3.2
!
ip pim rp-candidate Loopback0 group-list 1 interval 10
!
Interface F 0/1
Ip pim sparse-mode
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 112 of 311
!
Interface F 0/0
Ip pim sparse-mode
R1 R3
Ip multicast-routing Ip multicast-routing
! !
Interface F 0/0 Interface F 0/1
Ip pim sparse-mode Ip pim sparse-mode
! !
Interface Loopback 0 Interface F 0/0
Ip pim sparse-mode Ip pim sparse-mode
!
Interface Loopback0
Ip pim sparse-mode
R4
Ip multicast-routing
!
Interface F 0/0
Ip pim sparse-mode
!
Interface Loopback 0
Ip pim sparse-mode
Task 3
Configure R3 as the BSR-Candidate router using Loopback 0 interface.
R3
Ip multicast-routing
!
ip pim bsr-candidate Loopback0
Task 4
R1 should join the multicast groups 224.3.3.1 and 224.3.3.2 on the Loopback
0 interface. All multicast routers should be able to ping all R3 multicast routes.
R1
Ip multicast-routing
!
Int loopback 0
Ip igmp join-group 224.3.31
R1 R2
Lo 0 F 0/0 F 0/0 3 Lo 0
192.1.12.0/24 F 0/1
192.1.23.0/24
F 0/1
192.1.34.0/24
Lo 0 F 0/0 F 0/0 Lo 0
R4 R3
R1
R2
R3
R4
Task 1
Configure EIGRP 100 on all routers and advertise all the directly connected
networks.
R1 R2
Task 2
Configure R1 & R2 to use R2 to be the RP. Configure R1 to join 224.55.55.55 &
224.66.66.66 on the Loopback 0 interface.
R1 R2
Ip multicast-routing Ip multicast-routing
! !
Ip pim rp-address 2.2.2.2 Ip pim rp-address 2.2.2.2
!
Interface Loopback 0
Ip igmp join-group 224.55.55.55
Ip igmp join-group 224.66.66.66
R3 R4
Ip multicast-routing Ip multicast-routing
! !
Ip pim rp-address 3.3.3.3 Ip pim rp-address 3.3.3.3
!
Interface Loopback 0
Ip igmp join-group 224.55.55.55
Ip igmp join-group 224.66.66.66
Task 4
Configure PIM on the physical and loopback interfaces on all routers. If you
ping 224.55.55.55 or 224.66.66.66 from R1, you should only receive a reply
from R1.
R1 R2
R2
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring MPLS Unicast Routing
R2 R3
F 0/1 F 0//0
192.1.23.0/24
F 0/0 F 0/1
192.1.12.0/24 192.1.34.0/24
SP Core
AS 12353
F 0/0
OSPF Area 0 F 0/0
R1 R4
S 0/0 S 0/1 S 0/0 S 0/1
R5 R6 R7 R8
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4). Use x.x.x.x as the
router-id, where x is the Router number. Advertise all links in OSPF except for
the Serial Links on R1 & R4. Loopback 0’s should appear with a /8 mask in
the routing table.
R1 R2
R1 R4
Task 3
Configure MPLS on all the physical links in the SP Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface. The Labels should be assigned from the range X00 –
X99, where X is the router number.
R1 R2
Task 1
All LDP neighbor relationships should be authenticated using a password of
ccie12353.
R1
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring Intra-AS MPLS VPNs
R2 R3
F 0/1 F 0//0
192.1.23.0/24
F 0/0 F 0/1
192.1.12.0/24 192.1.34.0/24
SP Core
AS 12353
F 0/0
OSPF Area 0 F 0/0
R1 R4
S 0/0 S 0/1 S 0/0 S 0/1
R5 R6 R7 R8
Note:
Save the Configs on all the routers. Don’t save the configs during the labs. At
the completion of this lab, reload the routers without saving. This will allow
you to do the next lab based on the same topology.
R1
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
Task 3
Configure a static route on R1 in the CUST-A vrf to reach the 10.5.5.0 on R5.
Inject this route into BGP such that it should be reachable from CUST-A VRF
on R4. Configure a default Route on R5 towards R1.
R1
Task 4
Configure a static route on R4 in the CUST-A vrf to reach the 10.8.8.0 on R8.
Inject this route into BGP such that it should be reachable from CUST-A VRF
on R1. Configure a default Route on R8 towards R4.
R4
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C2 sites on R1 and R4.
R1 R4
Task 6
Configure a static route on R1 in the CUST-B vrf to reach the 10.6.6.0 on R6.
Inject this route into BGP such that it should be reachable from CUST-B VRF
on R4. Configure a default Route on R6 towards R1.
Task 7
Configure a static route on R4 in the CUST-B vrf to reach the 10.7.7.0 on R7.
Inject this route into BGP such that it should be reachable from CUST-B VRF
on R1. Configure a default Route on R7 towards R4.
R4
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
Note:
Save the Configs on all the routers. Don’t save the configs during the labs. At
the completion of this lab, reload the routers without saving. This will allow
you to do the next lab based on the same topology.
Task 1
Configure a VPNv4 neighbor relationship between R1 and R4. Make sure to
send the extended community attribute.
R1
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
R1
Router RIP
!
Address-family ipv4 vrf CUST-A
Version 2
No auto-summary
Network 192.1.15.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute rip
R5
Router RIP
Version 2
No auto-summary
Network 192.1.15.0
Network 10.0.0.0
Task 4
Configure RIPv2 as the Routing Protocol between R4 and R8-vrf CUST-A.
Advertise all the routes on R8 in RIP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-A on R1 has
reachability to routes learned from R8.
R4
Router RIP
!
Address-family ipv4 vrf CUST-A
Version 2
No auto-summary
Network 192.1.48.0
Redistribute BGP 12353 metric 1
!
Router RIP
Version 2
No auto-summary
Network 192.1.48.0
Network 10.0.0.0
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C2 sites on R1 and R4.
R1 R4
Task 6
Configure RIPv2 as the Routing Protocol between R6 and R1-vrf CUST-B.
Advertise all the routes on R6 in RIP. Advertise the VRF link in RIP on R1
under the appropriate address family. Make sure the VRF CUST-B on R4 has
reachability to routes learned from R6.
R1
Router RIP
!
Address-family ipv4 vrf CUST-B
Version 2
No auto-summary
Network 192.1.16.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
Router RIP
Version 2
No auto-summary
Network 192.1.16.0
Network 10.0.0.0
Task 7
Configure RIPv2 as the Routing Protocol between R7 and R4-vrf CUST-B.
Advertise all the routes on R7 in RIP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-B on R1 has
reachability to routes learned from R7.
R4
Router RIP
!
Address-family ipv4 vrf CUST-B
Version 2
No auto-summary
Network 192.1.47.0
Redistribute BGP 12353 metric 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Redistribute rip
R7
Router RIP
Version 2
No auto-summary
Network 192.1.47.0
Network 10.0.0.0
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
Note:
Save the Configs on all the routers. Don’t save the configs during the labs. At
the completion of this lab, reload the routers without saving. This will allow
you to do the next lab based on the same topology.
Task 1
Configure a VPNv4 neighbor relationship between R1 and R4. Make sure to
send the extended
R1
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
R1
Task 4
Configure EIGRP 100 as the Routing Protocol between R4 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in RIP on R4
under the appropriate address family. Make sure the VRF CUST-A on R1 has
reachability to routes learned from R8.
R4
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C2 sites on R1 and R4.
R1 R4
Task 6
Configure EIGRP 200 as the Routing Protocol between R6 and R1-vrf CUST-B.
Advertise all the routes on R6 in EIGRP 200. Advertise the VRF link in EIGRP
on R1 under the appropriate address family. Make sure the VRF CUST-B on R4
has reachability to routes learned from R6.
R1
Task 7
Configure RIPv2 as the Routing Protocol between R7 and R4-vrf CUST-B.
Advertise all the routes on R7 in RIP. Advertise the VRF link in EIGRP on R4
under the appropriate address family. Make sure the VRF CUST-B on R1 has
reachability to routes learned from R7.
R4
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
Note:
Save the Configs on all the routers. Don’t save the configs during the labs. At
the completion of this lab, reload the routers without saving. This will allow
you to do the next lab based on the same topology.
Task 1
Configure a VPNv4 neighbor relationship between R1 and R4. Make sure to
send the extended community attribute.
R1
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
R1
Task 4
Cust-A is running BGP in AS 100. Advertise all the routes on R8 in BGP.
Configure R4-R8 neighbor relationship in the appropriate address family. Make
sure the VRF CUST-A on R1 has reachability to routes learned from R8.
R4
Task 5
Configure a VRF CUST-B with a RD value of 1:200 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C2 sites on R1 and R4.
Task 6
Cust-B is running BGP in AS 200. Advertise all the routes on R6 in BGP.
Configure R1-R6 neighbor relationship in the appropriate address family. Make
sure the VRF CUST-A on R4 has reachability to routes learned from R6.
R1
Task 7
Cust-B is running BGP in AS 200. Advertise all the routes on R7 in BGP.
Configure R4-R7 neighbor relationship in the appropriate address family. Make
sure the VRF CUST-A on R4 has reachability to routes learned from R7.
R4
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
(Builds on Lab 4)
Note:
Save the Configs on all the routers. Don’t save the configs during the labs. At
the completion of this lab, reload the routers without saving. This will allow
you to do the next lab based on the same topology.
Task 1
Configure a VPNv4 neighbor relationship between R1 and R4. Make sure to
send the extended community attribute.
R1
Task 2
Configure a VRF CUST-A with a RD value of 1:100 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
R1
Router ospf 1
Network 192.1.15.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
Task 4
Configure OSPF using process ID of 8 on R4 as the Routing Protocol between
R8 and R4-vrf CUST-A. Advertise all the routes on R8 in OSPF. Advertise the
VRF link in OSPF on R4 under the appropriate address family. Make sure the
VRF CUST-A on R1 has reachability to routes learned from R8.
R4
Router ospf 1
Network 192.1.48.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
R1 R4
Task 6
Configure OSPF using process ID of 3 on R1 as the Routing Protocol between
R6 and R1-vrf CUST-B. Advertise all the routes on R6 in OSPF. Advertise the
VRF link in OSPF on R1 under the appropriate address family. Make sure the
VRF CUST-B on R4 has reachability to routes learned from R6.
R1
Router ospf 1
Network 192.1.16.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
Task 7
Configure OSPF using process ID of 3 on R4 as the Routing Protocol between
R7 and R4-vrf CUST-B. Advertise all the routes on R7 in OSPF. Advertise the
VRF link in OSPF on R4 under the appropriate address family. Make sure the
VRF CUST-B on R1 has reachability to routes learned from R7.
R4
Router ospf 1
Network 192.1.47.0 0.0.0.255 area 0
Network 10.0.0.0 0.255.255.255 area 0
NOTE:
For the CUST-A VRF, the OSPF routes form the other site appears as O E2
(External) routes. This is due to the fact that PE Routers are using different
Process ID for the Address Family OSPF process.
For the CUST-B VRF, the OSPF routes form the other site appears as O IA
(Inter-Area) routes. This is due to the fact that PE Routers are using the same
process ID (3). The MPLS network is treated as the OSPF Super-Backbone.
Task 1
Configure a Domain-id under OSPF for CUST-A VRF on R1 and R4 as 0.0.0.25
to ensure that OSPF routes are injected as O IA routes on the PE and
Customer Routers.
R1
NOTE:
For the CUST-A VRF, the OSPF routes from the other site now appear as O IA
routes.
(Builds on Lab 6)
Task 1
Configure a Link between R6 and R7 as 192.1.67.0/24. Advertise this link in
OSPF. Use S 0/1 on both routers to connect.
R6 R4
Task 2
Configure a new loopback each on R1 and R4. This newly created loopback
should be part of vrf CUST-B. Advertise this loopback under BGP for the CUST-
B vrf. The Loopback information is as follows:
• R1 – Loopback 67 – 10.67.67.1/32
• R4 – Loopback 67 – 10.67.67.4/32
R1
Interface Loopback 67
Ip vrf forwarding CUST-B
Ip address 10.67.67.1 255.255.255.255
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Network 10.67.67.1 mask 255.255.255.255
R4
Interface Loopback 67
Ip vrf forwarding CUST-B
Ip address 10.67.67.4 255.255.255.255
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-B
Task 3
Traffic between C2-Site1 and C2-Site2 should be using the new link (Back
door). You would like the traffic to go thru the MPLS link instead. Configure a
Sham-Link between R1 and R4 based on the new Loopbacks created in the
previous step.
R1 R4
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
(Builds on Lab 7)
Task 1
Configure a VPNv4 neighbor relationship between R1 and R4. Make sure to
send the extended community attribute.
R1
Task 2
Configure a VRF CUST-A with a RD value of 100:1 on R1. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connects to Cust A-Site1 on R1.
R1
ip vrf CUST-A
rd 100:1
route-target both 100:1
!
Interface S 0/0
Ip vrf forwarding CUST-A
Ip address 192.1.15.1 255.255.255.0
Task 3
Configure a VRF CUST-B with a RD value of 100:2 on R1. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connects to Cust B-Site1 on R1.
ip vrf CUST-B
rd 100:2
route-target both 100:2
!
Interface S0/1
Ip vrf forwarding CUST-B
Ip address 192.1.16.1 255.255.255.0
Task 4
Configure a VRF CUST-C with a RD value of 100:3 on R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connects to Cust C-Site1 on R4.
R4
ip vrf CUST-C
rd 100:3
route-target both 100:3
!
Interface S 0/0
Ip vrf forwarding CUST-C
Ip address 192.1.47.4 255.255.255.0
Task 5
Configure a VRF CUST-D with a RD value of 100:4 on R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connects to Cust D-Site1 on R4.
R4
ip vrf CUST-D
rd 100:4
route-target both 100:4
!
Interface S 0/1
Ip vrf forwarding CUST-D
Ip address 192.1.48.4 255.255.255.0
Task 6
Configure EIGRP 100 as the PE-CE Routing Protocol between all CE’s and PE’s.
Advertise all the routes on CE’s in EIGRP. Advertise the VRF link in EIGRP on
R1
Task 7
Configure an Extranet such that Cust D Site1 receives routes from all the other
Customer sites (Cust A, Cust B and Cust C). All sites should be able to connect
to CUST-D Site1.
R1
IP VRF CUST-A
Route-target import 100:4
!
IP VRF CUST-B
Route-target import 100:4
R4
Task 1
Configure the following loopbacks on R5, R6 and R8 and advertise them into
EIGRP:
R5
➢ Loopback 11 – 192.168.51.5/24
➢ Loopback 12 – 192.168.52.5/24
➢ Loopback 13 – 192.168.53.5/24
➢ Loopback 14 – 192.168.54.5/24
R6
➢ Loopback 11 – 192.168.61.5/24
➢ Loopback 12 – 192.168.62.5/24
➢ Loopback 13 – 192.168.63.5/24
➢ Loopback 14 – 192.168.64.5/24
R7
➢ Loopback 11 – 192.168.71.5/24
➢ Loopback 12 – 192.168.72.5/24
➢ Loopback 13 – 192.168.73.5/24
➢ Loopback 14 – 192.168.74.5/24
R5 R6
Interface Loopback 11
Ip address 192.168.71.7 255.255.255.0
!
Interface Loopback 12
Ip address 192.168.72.7 255.255.255.0
!
Interface Loopback 13
Ip address 192.168.73.7 255.255.255.0
!
Interface Loopback 14
Ip address 192.168.74.7 255.255.255.0
!
Router EIGRP 100
Network 192.168.71.0
Network 192.168.72.0
Network 192.168.73.0
Network 192.168.74.0
Task 2
The newly created networks on Customer A and B should only be propagated
between Customer A, B and C. These networks should not be send to
Customer D. Use an Export-map with a Route-target of 100:123 on the PE
routers to accomplish this task.
R1
ip vrf CUST-C
route-target import 100:123
Task 3
The newly created networks on Customer C should be propagated between
Customer A, B and D. Use an Export-map with a Route-target of 1:123 on the
PE routers to accomplish this task. Use the additive keyword.
R4
Task 1
Customer A is receiving all the 192.168.X.0 networks from Customer B and C
sites. Configure R1 such that CUST-A VRF only receives the routes from the
192.168.X.0 range that have an odd number in the third octet. Use an import
map to accomplish this task.
R1
Task 2
Customer C is receiving all the 192.168.X.0 networks from Customer A and B
sites. Configure R4 such that CUST-C VRF only receives the routes from the
192.168.X.0 range that have an even number in the third octet. Use an import
map to accomplish this task.
R4
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring Inter-AS MPLS VPNs
R2
F 0/0 F 0/1
192.1.12.0/24 192.1.23.0/24
F 0/0 F 0/0
R1
SP Core R3
S 0/0 S 0/1 AS 12353 S 0/0 S 0/1
OSPF Area 0
C1-Site1 R4 C1-Site2 R5
F 0/0 F 0/1 F 0/0 F 0/1
192.1.59.0/24
192.1.46.0/24 192.1.47.0/24 192.1.58.0/24
F 0/0 F 0/0
F 0/0 F 0/0
R6 R7 R9
R8
R1
R2
R3
R4
R5
R7
R8
R9
Task 1
Configure OSPF between all the SP routers (R1, R2, R3). OSPF process should
use Loopback0 on each router as the router-id. Advertise all internal SP links
in OSPF. Loopback 0’s should appear with a /8 mask in the routing table.
R1 R2
Interface Loopback 0
Ip ospf network point-to-point
!
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 160 of 311
Router ospf 1
Router-id 3.3.3.3
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.23.3 0.0.0.0 area 0
Task 2
Configure BGP between R1 and R3 in AS 12353. Use the most reliable interface
to form the neighbour relationship between them
R1 R3
Task 3
Configure MPLS on all the physical links in the SP Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface.
R1 R2
Task 4
Configure a VPNv4 neighbor relationship between R1 and R3. Set the next-hop-
self attribute on the IPv4 neighbor relationship.
R1 R3
Task 5
Customer A has 2 Sites. Each site contains 2 Departments (Sales an Finance).
The customer wants to segregate the 2 departments by using 2 MPLS VPNs.
Configure the 2 links on the PE Routers towards the CE Routers as 2 separate
VPNs.
R1 R3
Task 5
Configure CE Routers to connect the SALES Department Link to the SALES
VPN and the FINANCE department to the FINANCE VPN by using VRF on the
CE Routers. R6 and R8 are in the SALES Department. R7 and R9 are in the
FINANCE Department.
R4 R5
Task 6
Configure EIGRP in AS 100 as the routing protocol between the SALES
Routers. Run EIGRP in AS 100 under the VRF CUST-A-SALES on the PE
Routers. Perform Mutual redistribution between BGP and EIGRP under the
address-family to propagate the routes between the Customer Sites.
R1
Task 7
Configure EIGRP in AS 200 as the routing protocol between the FINANCE
Routers. Run EIGRP in AS 200 under the VRF CUST-A-FIN on the PE Routers.
Perform Mutual redistribution between BGP and EIGRP under the address-
family to propagate the routes between the Customer Sites.
192.1.34.0/24
R5
R2 R3 R4
192.1.45.0/24
192.1.23.0/24
F 0/1 F 0/0 F 0/0 F 0/1
F 0/0 F 0/0
192.1.56.0/24
192.1.12.0/24
F 0/1
AS 456
F 0/0 AS 123
OSPF Area 0 R6
OSPF Area 0
R1 F 0/1
F 0/1
192.1.17.0/24 192.1.68.0/24
F 0/0
F 0/0
R8
R7
C1-Site2
C1-Site1
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF between all the SP routers in AS 123 (R1, R2, R3) and AS 456
(R1, R2, R3). Hard code the Router-ID’s. Advertise all links in OSPF except the
Links between CE-PE’s and the ASBR’s (R3-R4) in the respective AS’s.
R1 R2
R1 R2
Note:
Save the Configs on all the routers. Don’t save the configs during the labs.
At the completion of this lab, reload the routers without saving. This will
allow you to do the next lab based on the same topology.
R1 R3
Task 4
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 123.
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 456.
R1 R3
Task 5
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your Import &
export Route-target. Assign this VRF to the links that connect to C1 sites on R1
and R6.
R1 R6
Task 6
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Task 7
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Task 8
Configure a VRF AS456 with a RD value of 123:1 on R3. Use the RD values for
your import & export Route-targets. Configure a VRF AS123 with a RD value of
456:1 on R4. Use the RD values for your import & export Route-targets. Assign
this VRF to the links that connects R3 & R4.
R3 R4
Task 9
Configure EIGRP 100 as the Routing Protocol between R3-R4 inside the VRF.
Inject all the BGP learned routes in the VRF into EIGRP on both Routers. Inject
the EIGRP routes into MP-BGP.
R3
Task 10
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
Task 1
Configure BGP between R1 and R3 in AS 123. Configure BGP between R4 and
R6 in AS 456. Use the most reliable interface to form the neighbour
relationship between them.
R1 R3
Task 2
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 123.
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 456.
R1 R3
Task 3
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your export
Route-target. On R1, use 456:1 as the import route-target. On R6, use 123:1 as
the import route-target. Assign this VRF to the links that connect to C1 sites
on R1 and R6.
R1 R6
Task 4
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Task 5
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Task 6
Configure a MP-eBGP neighbor relationship between the ASBR’s (R3 and R4).
The ASBR’s should learn the routes from their internal PE routers and
propagate these routes to the ASBR in the other AS. Make sure that the ASBR’s
change the next-hop attribute to themselves when propagating the external
VPNv4 routes. Make sure the ASBR’s learn the routes from the internal ASBR’s
although they do not have a VRF that have route-targets defined.
R3
Task 7
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
Task 1
Configure BGP between R1 and R3 in AS 123. Configure BGP between R4 and
R6 in AS 456. Use the most reliable interface to form the neighbour
relationship between them.
R1 R3
Task 2
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 123.
Configure a VPNv4 neighbor relationship between R1 and R3 in AS 456.
R1 R3
Task 3
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your export
Route-target. On R1, use 456:1 as the import route-target. On R6, use 123:1 as
the import route-target. Assign this VRF to the links that connect to C1 sites
on R1 and R6.
R1 R6
Task 4
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Task 5
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Task 6
Configure a MP-eBGP neighbor relationship between the ASBR’s (R3 and R4).
The ASBR’s should learn the routes from their internal PE routers and
propagate these routes to the ASBR in the other AS. ASBR’s should not change
the next-hop attribute on the route that it propagates towards it’s MP-iBGP
neighbors. Make sure the ASBR’s learn the routes from the internal ASBR’s
although they do not have a VRF that have route-targets defined.
R3
Task 7
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
Task 1
Configure BGP between R3 and R4 to connect AS 123 and 456.
R3 R4
Task 2
You will be configuring a MP-eBGP relationship between the PE Routers (R1
and R6). In order to establish the relationship, the loopback 0 networks of R1
and R6 have to be advertised to the other AS. Redistribute the Loopbacks into
BGP on the ASBR’s and then back from BGP into the IGP to accomplish this.
Limit the redistribution to the Loopback networks only. Also, have BGP send
labels for each eBGP route it sends to its neighbor.
R3
Task 3
Configure a MP-eBGP neighbor relationship between R1 and R6. Configure the
neighbor relationship based on Loopback 0 interface. This interface was
propagated to the other AS in the previous step.
R1 R6
Task 4
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your export
Route-target. On R1, use 456:1 as the import route-target. On R6, use 123:1 as
the import route-target. Assign this VRF to the links that connect to C1 sites
on R1 and R6.
R1 R6
Task 5
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Task 6
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Task 7
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
NOTE:
Reload the Routers without saving the configs. This will setup the topology for
the next lab.
Task 1
Configure BGP between R3 and R4 to connect AS 123 and 456.
R3 R4
Task 2
You will be configuring a MP-eBGP relationship between the RR Routers (R2
and R5). In order to establish the relationship, the loopback 0 networks of R2
and R5 have to be advertised to the other AS. In addition to the RR
relationship, you would like to separate the Data plane from the Control Plane
by keeping the next-hop address pointing towards the PE Routers (R1 and R6).
Redistribute the Loopbacks into BGP on the ASBR’s and then back from BGP
into the IGP to accomplish this. Limit the redistribution to the Loopback
networks only. Also, have BGP send labels for each eBGP route it sends to its
neighbor.
R3
Task 3
Configure a MP-BGP neighbor relationship between R1 and R2 in AS 123.
Configure the neighbor relationship based on Loopback 0 interface. Configure a
MP-BGP neighbor relationship between R5 and R6 in AS 456. Configure the
neighbor relationship based on Loopback 0 interface. Make sure the RR learns
the routes from the PE routers although they do not have a VRF that have
route-targets defined.
R1 R2
Task 3
Configure a MP-eBGP neighbor relationship between the RR’s, R2 and R5.
Configure the neighbor relationship based on Loopback 0 interface. This
interface was propagated to the other AS in the previous step. RR should leave
the next-hop of the routes pointing towards the PE Routers to segregate the
Control plane from the Date plane.
R2 R5
Task 4
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your export
Route-target. On R1, use 456:1 as the import route-target. On R6, use 123:1 as
the import route-target. Assign this VRF to the links that connect to C1 sites
on R1 and R6.
R1 R6
Task 5
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Task 6
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Task 7
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
AS 12 AS 56
OSPF Area 0 OSPF Area 0
R3 R4
192.1.23.0/24 192.1.45.0/24
F 0/1 F 0/0 F 0/1 F 0/0
R5
R2 F 0/0 192.1.34.0/24 F 0/1
192.1.56.0/24
192.1.12.0/24 AS 34
F 0/0
Non-VPN
F 0/0 Transit AS R6
R1 F 0/1
F 0/1
192.1.17.0/24 192.1.68.0/24
F 0/0
F 0/0
R8
R7
C1-Site2
C1-Site1
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF as the IGP within the AS’s.. Hard code the Router-ID’s.
Advertise all links within the AS in OSPF. Do not advertise the Inter-AS links in
OSPF.
R1 R2
R1 R2
Task 3
Configure eBGP between the 3 AS’s. Connect AS 12 to AS 34 via the R2-R3
link. Connect AS 34 to AS 56 via the R4-R5 link. Also, configure a iBGP
neighbor relationship between R3 and R4 in AS 34. Configure the iBGP
neighbor relationship based on the Loopback 0 interfaces. Change the next-hop
to self
R2 R3
Task 4
You will be configuring a MP-eBGP relationship between PE Routers, R1 and
R6. In order to establish the relationship, the loopback 0 networks of R1 and
R6 need to be reachable to each other. Accomplish this by advertising the
Loopbacks to the eBGP peers. These routes should have an end-to-end LSP.
R2
Router BGP 34
Neighbor 192.1.23.2 send-label
Neighbor 4.4.4.4 send-label
R4
Router BGP 34
Neighbor 192.1.45.5 send-label
Neighbor 3.3.3.3 send-label
Task 5
Configure a MP-BGP neighbor relationship between R1 and R6. Configure the
neighbor relationship based on Loopback 0 interface.
R1 R6
Task 6
Configure a VRF CUST-A with a RD value of 123:1 on R1. Configure a VRF
CUST-A with a RD value of 456:1 on R6. Use the RD values for your export
Route-target. On R1, use 456:1 as the import route-target. On R6, use 123:1 as
the import route-target. Assign this VRF to the links that connect to C1 sites
on R1 and R6.
R1 R6
Task 7
Configure EIGRP 100 as the Routing Protocol between R7 and R1-vrf CUST-A.
Advertise all the routes on R7 in EIGRP. Advertise the VRF link in EIGRP 100
on R1 under the appropriate address family. Inject the EIGRP routes into MP-
BGP.
R1
Router EIGRP 12
!
Address-family ipv4 vrf CUST-A
Autonomous-system 17
No auto-summary
Network 192.1.17.0
!
Router BGP 12
!
Address-family ipv4 vrf CUST-A
Redistribute eigrp 17
R7
Router EIGRP 17
No auto-summary
Network 192.1.17.0
Network 10.0.0.0
Task 8
Configure EIGRP 100 as the Routing Protocol between R6 and R8-vrf CUST-A.
Advertise all the routes on R8 in EIGRP. Advertise the VRF link in EIGRP on R6
under the appropriate address family. Inject the EIGRP routes into MP-BGP.
R6
Router EIGRP 56
!
Address-family ipv4 vrf CUST-A
Router EIGRP 68
No auto-summary
Network 192.1.68.0
Network 10.0.0.0
Task 9
You should see the routes from the Other Site in the CUST VRF’s on R1 and R6
respectively. Inject these routes towards the CE Routers.
R1
Router EIGRP 12
!
Address-family ipv4 vrf CUST-A
Redistribute bgp 12 metric 1 1 1 1 1
R6
Router EIGRP 56
!
Address-family ipv4 vrf CUST-A
Redistribute bgp 56 metric 1 1 1 1 1
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Carrier Supporting Carrier (CSC)
AS 1256 AS 1256
Customer Customer
Carrier R3 R4 Carrier
192.1.23.0/24 192.1.45.0/24
F 0/1 F 0/0 F 0/1 F 0/0
R5
R2 F 0/0 F 0/1
192.1.34.0/24
192.1.56.0/24
192.1.12.0/24 AS 34
F 0/0
Backbone
F 0/0
Carrier R6
R1 F 0/1
F 0/1
192.1.17.0/24 192.1.68.0/24
F 0/0
F 0/0
CUST-A CUST-A R8
R7 AS 65001 AS 65002
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF as the IGP within the AS’s.. Hard code the Router-ID’s.
Advertise all links within the AS in OSPF. Do not advertise the Inter-AS links in
OSPF.
R1 R2
Task 2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 204 of 311
Configure MPLS on all the physical links in the Backbone AS, including the
links R2-R3 and R4-R5 link.
R2
Mpls ip
!
Interface F 0/1
Mpls ip
mpls ldp discovery transport-address interface
R3
Mpls ip
!
Interface F 0/1
Mpls ip
mpls ldp discovery transport-address interface
Task 3
R1 R2
Task 4
Configure a MP-BGP neighbor relationship between R3 and R4. Configure the
neighbor relationship based on Loopback 0 interface. This will carry routes for
the Customer Carrier inside an MPLS VPN.
R3 R6
Task 5
Configure a VRF CSC-A with a RD value of 34:1 on R3 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to the Backbone Carrier to the Customer Carrier on
the appropriate routers.
R3 R4
Task 6
Configure eBGP between the Customer Carrier CE Routers (R1,R6) and
Customer Routers (R7,R8). Advertise the Local Loopback network into BGP on
the Customer Routers.
R1
Task 7
Configure OSPF as the PE-CE routing protocol between Backbone PE’s and
Customer Carrier PE’s. Run OSPF under the address family for the VRF CSC-A
on the Backbone PE’s. Configure the Backbone PE’s to propagate the Customer
Carrier Routers to each other thru MPLS VPN.
R2
Router ospf 1
Network 192.1.23.0 0.0.0.255 area 0
R3
Router ospf 1
Network 192.1.45.5 0.0.0.0 area 0
Task 8
Configure an iBGP neighbor relationship between R2 and R5 using the
Backbone Carrier to connect.
R2
AS 1256 AS 1256
Customer Customer
Carrier R3 R4 Carrier
192.1.23.0/24 192.1.45.0/24
F 0/1 F 0/0 F 0/1 F 0/0
R5
R2 F 0/0 F 0/1
192.1.34.0/24
192.1.56.0/24
192.1.12.0/24 AS 34
F 0/0
Backbone
F 0/0
Carrier R6
R1 F 0/1
F 0/1
192.1.17.0/24 192.1.68.0/24
F 0/0
F 0/0
CUST-A CUST-A R8
R7 AS 65001 AS 65002
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF as the IGP within the AS’s.. Hard code the Router-ID’s.
Advertise all links within the AS in OSPF. Do not advertise the Inter-AS links in
OSPF.
R1 R2
Task 2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 211 of 311
Configure MPLS on all the physical links in the Backbone and Customer
Carrier AS, including the links R2-R3 and R4-R5 link.
R1
Task 3
Configure iBGP between the BGP routers within the Backbone AS. Configure
the neighbour relationship based on the loopback interface.
R3 R4
Task 4
Configure a MP-BGP neighbor relationship between R3 and R4. Configure the
neighbor relationship based on Loopback 0 interface. This will carry routes for
the Customer Carrier inside an MPLS VPN.
Task 5
Configure a VRF CSC-A with a RD value of 34:1 on R3 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to the Backbone Carrier to the Customer Carrier on
the appropriate routers.
R3 R4
Task 6
Configure eBGP between the Customer Carrier CE Routers (R1,R6) and
Customer Routers (R7,R8). Advertise the Local Loopback network into BGP on
the Customer Routers.
R1
Task 7
Configure OSPF as the PE-CE routing protocol between Backbone PE’s and
Customer Carrier PE’s. Run OSPF under the address family for the VRF CSC-A
on the Backbone PE’s. Configure the Backbone PE’s to propagate the Customer
Carrier Routers to each other thru MPLS VPN.
R2
Router ospf 1
Network 192.1.23.2 0.0.0.0 area 0
R3
Router ospf 1
Network 192.1.45.5 0.0.0.0 area 0
Task 8
Configure an iBGP neighbor relationship between R1 and R6 using the
Backbone Carrier to connect. Use Loopback 0 to establish this relationship.
Change the next-hop address to self.
AS 1256 AS 1256
Customer Customer
Carrier R3 R4 Carrier
192.1.23.0/24 192.1.45.0/24
F 0/1 F 0/0 F 0/1 F 0/0
R5
R2 F 0/0 F 0/1
192.1.34.0/24
192.1.56.0/24
192.1.12.0/24 AS 34
F 0/0
Backbone
F 0/0
Carrier R6
R1 F 0/1
F 0/1
192.1.17.0/24 192.1.68.0/24
F 0/0
F 0/0
CUST-A CUST-A R8
R7 EIGRP 100 EIGRP 100
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure OSPF as the IGP within the AS’s.. Hard code the Router-ID’s.
Advertise all links within the AS in OSPF. Do not advertise the Inter-AS links in
OSPF.
R1 R2
Task 2
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 219 of 311
Configure MPLS on all the physical links in the Backbone and Customer
Carrier AS, including the links R2-R3 and R4-R5 link.
R1
Task 3
Configure iBGP between the BGP routers within the Backbone AS. Configure
the neighbour relationship based on the loopback interface.
R3 R4
Task 4
Configure a MP-BGP neighbor relationship between R3 and R4. Configure the
neighbor relationship based on Loopback 0 interface. This will carry routes for
the Customer Carrier inside an MPLS VPN.
R3 R6
Task 5
Configure a VRF CSC-A with a RD value of 34:1 on R3 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to the Backbone Carrier to the Customer Carrier on
the appropriate routers.
R3 R4
Task 6
Configure a VRF for the Customers on the Customer Carrier PE routers.
Configure the VRF as CUST-A with a RD value of 1:100 on R1 and R6. Use the
same extended community for your Route-target import and export. Assign this
VRF to the links that connect Customer Carrier PE’s to the CE routers. Run
EIGRP in AS 100 as the PE-CE routing protocol. Advertise the Loopback
interfaces on the CE routers in EIGRP 100.
R1
ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/1
Ip vrf forwarding CUST-A
Ip address 192.1.17.1 255.255.255.0
!
Router EIGRP 1256
!
Address-family ipv4 vrf CUST-A
No auto-summary
Autonomous-system 100
Network 192.1.17.0
R6
Ip vrf CUST-A
rd 1:100
route-target both 1:100
!
Interface F 0/1
Ip vrf forwarding CUST-A
Ip address 192.1.68.6 255.255.255.0
!
Router EIGRP 1256
!
Address-family ipv4 vrf CUST-A
Task 7
Configure OSPF as the PE-CE routing protocol between Backbone PE’s and
Customer Carrier PE’s. Run OSPF under the address family for the VRF CSC-A
on the Backbone PE’s. Configure the Backbone PE’s to propagate the Customer
Carrier Routers to each other thru MPLS VPN.
R2
Router ospf 1
Network 192.1.23.2 0.0.0.0 area 0
R3
Router ospf 1
Network 192.1.45.5 0.0.0.0 area 0
Task 8
Configure an MP-BGP neighbor relationship between R1 and R6 using the
Backbone Carrier to connect. Use Loopback 0 to establish this relationship.
R1
Task 9
Configure Customer Carrier PE routers such that they propagated the
Customer routes to each other by perform mutual redistribution.
R1
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring IPv6 over MPLS VPN
R2 R3
F 0/1 F 0//0
192.1.23.0/24
F 0/0 F 0/1
192.1.12.0/24 192.1.34.0/24
SP Core
AS 12353
F 0/0
OSPF Area 0 F 0/0
R1 R4
F 0/1 F 0/1
2000:192:1:15::/64 2000:192:1:46::/64
F0/0 F 0/0
R5 R6
CUST-A CUST-A
R1
R2
R3
R4
R5
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4). Use x.x.x.x as the
router-id, where x is the Router number. Advertise all links in OSPF except for
the Serial Links on R1 & R4. Loopback 0’s should appear with a /8 mask in
the routing table.
R1 R2
Task 2
Configure BGP between R1 and R4 in AS 12353. Use the most reliable interface
to form the neighbour relationship between them.
R1 R4
Task 3
Copyrights Khawar Butt 2006-2020
Website: http://www.khawarb.com; Email: khawarb@khawarb.com
Page 229 of 311
Configure MPLS on all the physical links in the SP Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface.
R1 R2
(Builds on Lab 1)
Task 1
Configure a VPNv6 neighbor relationship between R1 and R4. Make sure to
send the extended community attribute.
R1
Ipv6 unicast-routing
!
Router BGP 12353
!
Address-family vpnv6
Neighbor 4.4.4.4 activate
Neighbor 4.4.4.4 send-community extended
R4
Ipv6 unicast-routing
!
Router BGP 12353
!
Address-family vpnv6
Neighbor 1.1.1.1 activate
Neighbor 1.1.1.1 send-community extended
Task 2
Configure a VRF CUST-A with a RD value of 12353:1 on R1 and R4 for IPv6.
Use the same extended community for your Route-target import and export.
Assign this VRF to the links that connect to CUST-A sites on R1 and R4.
R1 R4
Task 3
CUST-A is running BGP in AS 65001. Advertise all the routes on R5 in BGP.
Configure R1-R5 neighbor relationship in the appropriate address family. Make
sure the VRF CUST-A on R4 has reachability to routes learned from R5.
R1
ipv6 unicast-routing
!
router bgp 65001
!
bgp router-id 5.5.5.5
!
address-family ipv6
neighbor 2000:192:1:15::1 remote-as 100
network fc00:10:5:5::/64
Task 4
CUCT-A is running BGP in AS 65001. Advertise all the routes on R6 in BGP.
Configure R4-R6 neighbor relationship in the appropriate address family. Make
sure the VRF CUST-A on R1 has reachability to routes learned from R6.
R4
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring Layer 2 MPLS VPNs
C1-Site1 C1-Site2
R4 R5
R2
F 0/0.35
F 0/0.14
F 0/0.12 (.2) F 0/0.23 (.2)
192.1.12.0/24 VLAN 12
192.1.23.0/24 VLAN 23
F 0/0.23 (.3)
F 0/0.14
R1
R3
S 0/0
S 0/0
AS 123
OSPF Area 0
S 0/0 S 0/0
R6
R7
C2-Site2
C2-Site1
R1
R2
R3
Task 1
Configure OSPF between all the SP routers in AS 123 (R1, R2, R3. Hard code
the Router-ID’s. Advertise all links in OSPF except the Links between CE-PE’s.
R1 R2
Router ospf 1
Router-id 3.3.3.3
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.23.3 0.0.0.0 area 0
Task 2
Configure MPLS on all the physical links in the SP AS Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface.
Task 3
You need to connect R4 to R5 using Ethernet over MPLS. Configure R4 and R5
to be part of VLAN 45. Configure them with an IP address of 10.45.45.X/24,
where X is the 4 for R4 and 5 R5.
R4 R5
Task 4
Configure the PE Routers R1 and R3 to connect C1-Site1 and C1-Site2 to each
other. Use 145 as the PVC.
R1
Interface F 0/0.14
encapsulation dot1Q 45
Interface F 0/0.35
encapsulation dot1Q 45
xconnect 1.1.1.1 145 encapsulation mpls
Task 1
You need to connect R6 to R7 using HDLC over MPLS. Configure R6 and R7
with an IP address of 10.67.67.X/24 on the S 0/0 interface, where X is the 6
for R6 and 7 R7.
R6 R7
Task 2
Configure the PE Routers R1 and R3 to connect C2-Site1 and C2-Site2 to each
other. Use 167 as the PVC.
R1
Interface S 0/0
Clock rate 128000
xconnect 3.3.3.3 167 encapsulation mpls
no shut
R3
Interface S 0/0
Clock rate 128000
xconnect 1.1.1.1 167 encapsulation mpls
no shut
Task 1
Reset the Serial 0/0 interface on the PE routers R1 and R3.
R1 R3
Task 2
You need to connect R6 to R7 using PPP instead of HDLC over MPLS. Change
the encapsulation on R6 and R7 to ppp.
R6 R7
Task 3
Configure the PE Routers R1 and R3 to connect C2-Site1 and C2-Site2 to each
other. Use 167 as the PVC.
R1
Interface S 0/0
Encap ppp
Clock rate 128000
xconnect 3.3.3.3 167 encapsulation mpls
no shut
R3
Interface S 0/0
Encap ppp
Clock rate 128000
xconnect 1.1.1.1 167 encapsulation mpls
no shut
Task 1
Reset the Serial 0/0 interface on the PE routers R1 and R3. Also, reset the
Serial interfaces on the CE Rotuers, R6 and R7.
R1 R3
Task 2
You need to connect R6 to R7 using Frame-relay. You need to connect R6 to R7
using Frame-relay over MPLS. Configure R6 and R7 with an IP address of
10.67.67.X/24 on the S 0/0 interface, where X is the 6 for R6 and 7 R7.
Configure a Frame-relay map to connect R6 to R7. Use a PVC of 167 on both
routers.
R6 R7
Task 3
Configure the PE Routers R1 and R3 to connect C2-Site1 and C2-Site2 to each
other. Use 167 as the PVC.
R1
Frame-relay switching
!
Interface S 0/0
Encap frame-relay
Clock rate 128000
Frame-relay intf-type dce
no shut
Frame-relay switching
!
Interface S 0/0
Encap frame-relay
Clock rate 128000
Frame-relay intf-type dce
no shut
!
connect FR67 Serial0/0 167 l2transport
xconnect 1.1.1.1 167 encapsulation mpls
C1-Site1
R4
R2
F 0/0.14
F 0/0.12 (.2) F 0/0.23 (.2)
192.1.12.0/24 VLAN 12
192.1.23.0/24 VLAN 23
F 0/0.12 (.1)
F 0/0.23 (.3)
F 0/0.14
R1
R3
S 0/0
S 0/0
AS 123
OSPF Area 0
S 0/0
R7
C1-Site2
R1
R2
R3
Task 1
Configure OSPF between all the SP routers in AS 123 (R1, R2, R3. Hard code
the Router-ID’s. Advertise all links in OSPF except the Links between CE-PE’s.
R1 R2
Router ospf 1
Router-id 3.3.3.3
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.23.3 0.0.0.0 area 0
Task 2
Configure MPLS on all the physical links in the SP AS Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface.
Task 3
You need to connect R4 to R7 using a combination of Frame-Relay and
Ethernet over MPLS. You will be configuring R4 using Frame-relay and R7
using Ethernet. Configure the pseudowire-class using a encapsulation of MPLS
for internetwork IP on R4 and R7.
R1 R3
Task 4
Configure the R1 using Ethernet to connect R4 to R7 using the pseudowire-
class created in the previous task. Also, configure R3 using Frame-relay to
connect R4 to R7 using the pseudowire-class created in the previous task. Use
147 for the Frame-relay PVC and the MPLS PVC.
R1
interface F0/0.14
encap dot1q 14
frame-relay switching
!
interface Serial0/0
no ip address
encapsulation frame-relay
clock rate 128000
frame-relay intf-type dce
no shut
!
connect FR47 Serial0/0 147 l2transport
xconnect 1.1.1.1 147 pw-class FR-VLAN
Task 5
Configure R4 F0/0.14 to be part of VLAN 14. Configure it with an IP address of
10.47.47.4/24. Configure R7 with an IP address of 10.47.47.7/24 on the S 0/0
interface. Use a PVC of 147.
R4 R7
C1-Site1
R4
F 0/0.14
F 0/0.14
AS 123
R1 OSPF Area 0
S 0/0
S 0/0
R6
C1-Site2
R1
Interface F 0/0
No shut
!
Interface F 0/0.14
Encapsulation dot1q 14
Task 2
Configure R1 S0/0 to connect R6 using Frame-relay. Turn on Frame-relay
switching on R1.
R1
Frame-relay switching
!
Interface S 0/0
encapsulation frame-relay
clock rate 128000
frame-relay intf-type dce
no shut
Task 3
Configure R1 to connect R4 to R6 using F0/0.14 and S 0/0 using interworking
ip and a VC of 46.
R1
Task 4
Configure R4 and R6. Configure R4 F0/0.14 using a VLAN of 14. Configure it
with an IP Address of 10.46.46.4/24. Configure R6 S0/0 using Frame-relay.
Configure it with an IP Address of 10.46.46.6/24. Configure a Frame-relay map
using the PVC 46 to connect to R4.
R4 R6
C2-Site1
R6
F 0/0
C1-Site1 C2-Site2
R4 R7
R2
F 0/0
F 0/0
S 0/0.12 (.2) S 0/0.23 (.2)
192.1.12.0/24
192.1.23.0/24
AS 123
OSPF Area 0
F 0/0
R5
C1-Site2
R1
R2
R3
Task 1
Configure OSPF between all the SP routers in AS 123 (R1, R2, R3. Hard code
the Router-ID’s. Advertise all links in OSPF except the Links between CE-PE’s.
R1 R2
Router ospf 1
Router-id 3.3.3.3
Network 3.3.3.3 0.0.0.0 area 0
Network 192.1.23.3 0.0.0.0 area 0
Task 2
Configure MPLS on all the physical links in the SP AS Network. Use LDP to
distribute labels. The LDP neighbour relationships should be formed based on
the most reliable interface.
Task 3
You need to connect R4 to R5 using L2TPv3. Configure them with an IP
address of 10.45.45.X/24, where X is the 4 for R4 and 5 R5.
R4 R5
Task 4
Configure R1 Loopback 4 with an ip address of 1.1.1.4/24. Configure Loopback
5 with an IP Address of 1.1.1.5/24. Configure 2 Pseudowire-class using L2TPv3
for encapsulation. The first Pseudowire-class should be called R4R5 and
should use Loopback 4 as the source. The second Pseudowire-class should be
called R5R4 and should use Loopback 5 as the source.
R1
Interface Loopback 4
Ip address 1.1.1.4 255.255.255.255
!
Task 5
Configure R1 F 0/0 to connect to R4. Configure this interface to switch the
packets to R5 using the pesodowire-class R4R5. Use 45 as the PVC with a
destination address of 1.1.1.5
R1
int F 0/0
xconnect 1.1.1.5 45 encapsulation l2tpv3 pw-class R4R5
no shut
Task 6
Configure R1 F 0/1 to connect to R5. Configure this interface to switch the
packets to R4 using the pesodowire-class R5R4. Use 45 as the PVC with a
destination address of 1.1.1.4
R1
int F 0/1
xconnect 1.1.1.4 45 encapsulation l2tpv3 pw-class R5R4
no shut
Task 1
You need to connect R6 to R7 using L2TPv3. Configure them with an IP
address of 10.67.67.X/24, where X is the 6 for R6 and 7 R7.
R6 R7
Task 2
Configure 2 Pseudowire-class using L2TPv3 for encapsulation. The first
Pseudowire-class should be called R6R7 and should be created on R2. It
should use Loopback 0 as the source address. The second Pseudowire-class
should be called R7R6 and should be created on R3. It should use Loopback 0
as the source address.
R2
pseudowire-class R6R7
encapsulation l2tpv3
ip local interface Loopback0
R3
pseudowire-class R7R6
encapsulation l2tpv3
ip local interface Loopback0
Task 3
Configure R2 F 0/0 to connect to R6. Configure this interface to switch the
packets to R7 using the pesodowire-class R6R7. Use 67 as the PVC with a
destination address of 3.3.3.3.
R2
int F 0/0
xconnect 3.3.3.3 67 encapsulation l2tpv3 pw-class R6R7
no shut
R1
int F 0/0
xconnect 2.2.2.2 67 encapsulation l2tpv3 pw-class R7R6
no shut
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring MPLS Traffic Engineering
R2 R3
F 0/1 192.1.23.0/24 F 0//0
S 0/0 S 0/0
F 0/0 F 0/1
192.1.13.0/24
192.1.12.0/24 192.1.34.0/24
192.1.24.0/24
R1 R4
F 0/1 192.1.14.0/24 F 0//0
S 0/1
S 0/1
192.1.15.0/24
192.1.46.0/24
S 0/0 S 0/0
R5 R6
Site1 Site2
R1
R2
R3
R4
R5
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4). Use x.x.x.x as the
router-id, where x is the Router number. Advertise all links in OSPF except for
the Serial Links on R1 & R4 towards R5 & R6 respectively.
R1 R2
Task 3
Configure MPLS on all the physical links in the SP Network. The LDP
neighbour relationships should be formed based on the most reliable interface.
R1 R2
Task 1
Enable MPLS Traffic Engineering on all the Core Routers. OSPF Area 0 should
also be enabled for MPLS TE. Use Loopback 0 as the router-id.
R1 R2
Task 2
Enable RSVP Bandwidth reservation & MPLS Traffic Engineering on all SP
Interfaces on all SP Routers. Configure a reservation of 512 on all Fastethernet
ports. Configure a reservation of 192 on all Serial Interfaces. This needs to be
done on all SP Core routers.
R1 R2
Task 3
Configure a MPLS TE Tunnel to have R1 use the R1-> R2 -> R4 path for Traffic
destined to 4.4.4.4. This tunnel should have a bandwidth reservation
requirement of 128 kbps.
R1
Interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 explicit name R1-R4
!
ip explicit-path name R1-R4 enable
next-address 192.1.12.2
next-address 192.1.24.4
Notes: Make sure the Tunnel comes up and it is used in the routing table as the
next hop for the 4.4.4.4 network.
Task 4
Configure a MPLS TE Tunnel to have R4 use the R4-> R3 -> R1 path for Traffic
destined to 1.1.1.1. This tunnel should have a bandwidth reservation
requirement of 100 kbps.
R4
Interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 1.1.1.1
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
Task 5
Configure an IPv4 & VPNv4 neighbor relationship between R1 and R4. Make
sure to send the extended
R1
Task 6
Configure a VRF CUST-A with a RD value of 12353:1 on R1 and R4. Use the
same extended community for your Route-target import and export. Assign this
VRF to the links that connect to C1 sites on R1 and R4.
R1 R4
Task 7
Configure EIGRP 100 as the Routing Protocol between R5 and R1 in vrf CUST-
A. Advertise all the routes on R5 in EIGRP. Advertise the VRF link in EIGRP on
R1 under the appropriate address family. Make sure the VRF CUST-A on R4
has reachability to routes learned from R5.
R1
Router EIGRP 1
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
No auto-summary
Network 192.1.15.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute eigrp 100
R5
Task 8
Configure EIGRP 100 as the Routing Protocol between R4 and R6 in vrf CUST-
A. Advertise all the routes on R6 in EIGRP. Advertise the VRF link in EIGRP on
R4 under the appropriate address family. Make sure the VRF CUST-A on R1
has reachability to routes learned from R6.
R4
Router EIGRP 1
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
Task 9
Use a Traceroute command from R5 and R6 to verify that the traffic between
R1 and R4 is using the appropriate paths.
R5
Task 1
Delete the Tunnels created in Lab 2. We will be creating tunnels dynamically
based on the available bandwidth the routing protocol metrics.
R1 R4
Task 2
Re-configure RSVP bandwidth reservations based on the following:
R1 R2
R1
Interface Tunnel 12
ip unnumbered Loopback0
tunnel destination 2.2.2.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 dynamic
!
Interface Tunnel 13
ip unnumbered Loopback0
tunnel destination 3.3.3.3
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 dynamic
!
Interface Tunnel 14
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 80
tunnel mpls traffic-eng path-option 1 dynamic
Task 4
Verify which tunnels were created. Also, verify the path that is being taken by
the Tunnels.
R1
R6
Task 1
Configure a MPLS TE Tunnel on R4 to connect to R2. It should have a
bandwidth requirement of 128. Setup based on the Routing and RSVP
contraints.
R4
Interface Tunnel 24
ip unnumbered Loopback0
tunnel destination 2.2.2.2
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 dynamic
Task 2
Verify if the tunnel came up by checking the routing table for reachability to
2.2.2.2.
R4
Show IP route
Note : The tunnel didn't come up as the all the bandwidth was already reserved by
the other Tunnels.
Task 3
Change the mpls traffic-eng priority for the Tunnel on R4 towards 2.2.2.2 to 2
for both Setup and Hold. Check to see if the Tunnel Came up.
R4
Interfae Tunnel24
Tunnel mpls traffic-eng priority 2 2
Show IP route
Task 4
Verify Tunnel 12 on R1 towards 2.2.2.2.
R1
Show IP route
Note : Notice that R1 is not using the MPLS TE tunnel towards 2.2.2.2. This is the
tunnel that got pushed off to accomodate the higher priority tunnel.
Task 1
Disable OSPF on all 4 Core Routers.
R1 R2
Task 2
Configure IS-IS on all 4 routers in a single Area 49.0000. Use XXXX.XXX.XXXX
as the System ID. Advertise all the Loopbacks in IS-IS. Make sure that the
Routers only establish L1 Adjacencies with each other. Enable Wide style
metric to accomodate MPLS TE.
R1 R2
Task 3
Enable MPLS Traffic Engineering IS-IS for all Level-1 neighbors. Use Loopback
0 as the router-id.
R1 R2
Task 4
Verify the status of the tunnels on R1 & R4.
R1
Show IP route
!
Sh mpls traffic-eng tunnel brief
R2
S 0/0 S 0/1
192.1.23.0/24 192.1.24.0/24
S 0/0 S 0/1
R3 R4
F 0/1 192.1.34.0/24 F 0//0
F 0/0 F 0/1
192.1.13.0/24 192.1.46.0/24
F 0/0 F 0/0
R1 R5
R1
R2
R4
R5
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4,R5). Use x.x.x.x as
the router-id, where x is the Router number. Advertise all links in OSPF.
R1 R2
Task 2
Configure MPLS on all the physical links in the SP Network. The LDP
neighbour relationships should be formed based on the most reliable interface.
R1 R2
Task 3
Enable MPLS Traffic Engineering on all the Core Routers. OSPF Area 0 should
also be enabled for MPLS TE. Use Loopback 0 as the router-id.
R1 R2
Task 4
Enable RSVP Bandwidth reservation & MPLS Traffic Engineering on all SP
Interfaces on all SP Routers. Configure a reservation of 512 on all Fastethernet
ports. Configure a reservation of 192 on all Serial ports.
R1 R2
int F 0/0
mpls traffic-eng tunnel
ip rsvp bandwidth 512
R1
Interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 5.5.5.5
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 explicit name R1-R5
tunnel mpls traffic-eng fast-reroute
!
ip explicit-path name R1-R5 enable
next-address 192.1.13.3
next-address 192.1.34.4
next-address 192.1.45.5
Notes: Make sure the Tunnel comes up and it is used in the routing table as the
next hop for the 5.5.5.5 network.
Task 6
Configure a MPLS TE Tunnel on R3 to provide link protection for the R3-R4
link by using a backup path via R2 to R4. This tunnel should also have a
bandwidth reservation requirement of 128 kbps. Don't tunnel should be used
only as a backup in case of R3-R4 link going down. Configure this tunnel as
the back link on the Protected Link.
R3
Interface Tunnel 1
ip unnumbered Loopback0
tunnel destination 4.4.4.4
tunnel mode mpls traffic-eng
tunnel mpls traffic-eng priority 4 4
tunnel mpls traffic-eng bandwidth 128
tunnel mpls traffic-eng path-option 1 explicit name R3-R4
!
ip explicit-path name R3-R4 enable
next-address 192.1.23.2
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020 Configuring Multicast MPLS VPN
R2 R3
F 0/1 192.1.23.0/24 F 0//0
F 0/0 F 0/1
192.1.12.0/24 192.1.34.0/24
F 0/0 F 0/0
R1 R4
F 0/1 F 0/1
192.1.15.0/24
192.1.46.0/24
F 0/0 F 0/0
R5 R6
Site1 Site2
R1
R2
R3
R4
R5
Task 1
Configure OSPF between all the SP routers (R1, R2, R3, R4). Use x.x.x.x as the
router-id, where x is the Router number. Advertise all links in OSPF except for
the Serial Links on R1 & R4 towards R5 & R6 respectively.
R1 R2
Task 3
Configure MPLS on all the physical links in the SP Network. The LDP
neighbour relationships should be formed based on the most reliable interface.
R1 R2
Task 1
Configure an IPv4 & VPNv4 neighbor relationship between R1 and R4. Make
sure to send the extended
R1
Task 2
Configure a VRF CUST-A with a RD value of 100:1 on R1 and R4. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to C1 sites on R1 and R4.
R1 R4
R1
Router EIGRP 1
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
No auto-summary
Network 192.1.15.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
!
Address-family ipv4 vrf CUST-A
Redistribute eigrp 100
R5
Task 4
Configure EIGRP 100 as the Routing Protocol between R6 and R4 in vrf CUST-
A. Advertise all the routes on R6 in EIGRP. Advertise the VRF link in EIGRP on
R4 under the appropriate address family. Make sure the VRF CUST-A on R1
has reachability to routes learned from R6.
R4
Router EIGRP 1
!
Address-family ipv4 vrf CUST-A
Autonomous-system 100
No auto-summary
Network 192.1.46.0
Redistribute BGP 12353 metric 1 1 1 1 1
!
Router BGP 12353
Task 5
Configure Multicast routing on the Customer Routers (R5 & R6) using PIM
Sparse-dense-mode. Configure 10.5.5.5 as the RP-Address. Have the loopback
interface join the 224.56.56.56 multicast group.
R5
ip multicast-routing
!
int f 0/0
ip pim sparse-dense-mode
int lo0
ip pim sparse-dense-mode
ip igmp join-group 224.56.56.56
!
ip pim rp-address 10.5.5.5
R6
ip multicast-routing
!
int f 0/0
ip pim sparse-dense-mode
int lo0
ip pim sparse-dense-mode
ip igmp join-group 224.56.56.56
!
ip pim rp-address 10.5.5.5
Task 6
Configure Multicast routing on all SP routers using PIM Sparse-dense-mode.
Enable Multicast routing for the CUST-A VRF on the PE routers.
R1 R2
ip multicast-routing ip multicast-routing
! ip multicast-routing vrf CUST-A
int F 0/0 !
ip pim sparse-dense-mode int F 0/0
int F 0/1 ip pim sparse-dense-mode
ip pim sparse-dense-mode int F 0/1
int loopback 0 ip pim sparse-dense-mode
ip pim sparse-dense-mode int loopback 0
ip pim sparse-dense-mode
Task 7
Configure VRF CUST-A on the PE routers (R1 & R4) to use 239.1.1.1 as the
default control group address. It should be allowed to route the group
addresses in the 224.56.56.0/24 range. Configure 10.5.5.5 as the RP address
for this VRF.
R1
ip vrf CUST-A
mdt default 239.1.1.1
mdt data 224.56.56.0 0.0.0.255
!
ip pim vrf CUST-A rp-address 10.5.5.5
R4
ip vrf CUST-A
mdt default 239.1.1.1
mdt data 224.56.56.0 0.0.0.255
!
ip pim vrf CUST-A rp-address 10.5.5.5
R5
Ping 224.56.56.56
R6
Ping 224.56.56.56
Task 1
As we will be configuring Auto-RP on R5, take out the static assignment of the
RP on R1, R4, R5 & R6 Routers
R1 R4
No ip pim vrf CUST-A rp-address 10.5.5.5 No ip pim vrf CUST-A rp-address 10.5.5.5
R5 R6
Task 2
Configure R5 as the RP-Candidate and the Mapping agent. Use Loopback 0 as
the source address with a scope of 10 and an interval of 10 secs.
R5
Task 3
Verify that the other routers are notified of the RP Mapping using the show ip
pim rp mapping command
R1
Group(s) 224.0.0.0/4
RP 10.5.5.5 (?), v2v1
Info source: 10.5.5.5 (?), elected via Auto-RP
Uptime: 00:11:06, expires: 00:02:44
R4
Group(s) 224.0.0.0/4
RP 10.5.5.5 (?), v2v1
Info source: 10.5.5.5 (?), elected via Auto-RP
Uptime: 00:11:42, expires: 00:02:11
R6
sh ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 224.0.0.0/4
RP 10.5.5.5 (?), v2v1
Info source: 10.5.5.5 (?), elected via Auto-RP
Uptime: 00:12:25, expires: 00:02:28
Authored By:
Khawar Butt
Penta CCIE # 12353
CCDE # 20110020
Configuring MPLS on IOS-XR
R10 R9
CUST-A CUST-A
SITE # 2 SITE # 1
E 0/0 E 0/0
192.1.20.0/24 192.1.10.0/24
E 0/2 E 0/2
R2 R1
E 0/0
192.1.23.0/24 E 0/1 E 0/0
E 0/1
192.1.13.0/24
192.1.100.0/24
G 0/0/0/0
G 0/0/0/1
E 0/1
E 0/0 192.1.34.0/24 G 0/0/0/2
R4 R3
E 0/2
AS 100
192.1.48.0/24
E 0/2
E 0/0 192.1.78.0/24 G 0/0/0/2
R8 R7
E 0/1 G 0/0/0/1
G 0/0/0/0
192.1.67.0/24
192.1.200.0/24
192.1.57.0/24
G 0/0/0/1
E 0/0
E 0/1
G 0/0/0/0
R6 R5
192.1.60.0/24 192.1.50.0/24
E 0/0
E 0/0
CUST-A CUST-A
SITE # 4 SITE # 3
R12 R11
R1
R2
R3
R4
R5
R7
R8
Task 1
Configure IP Addresses on R1, R2, R3 & R4 based on the above table.
R1 R2
R3 R4
R1 R2
R3 R4
Task 3
Configure MPLS on all the physical links in the SP Network. The LDP
neighbour relationships should be formed based on the most reliable interface.
R1 R2
Task 1
Configure IP Addresses on R5,R6,R7 & R8 based on the above table.
R5 R6
R5 R6
Task 3
Configure MPLS on all the physical links in the SP Network. The LDP
neighbour relationships should be formed based on the most reliable interface.
R5 R6
Task 1
Configure a VPNv4 neighbor relationship between R1-R3 & another one
between R2 & R3 in AS 100. These relationships should be set based on the
Loopback interfaces. R1 & R2 should be route-reflector clients for R3.
R1
Task 2
Configure a VRF CUST-A with a RD value of 100:1 on R1 and R2. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to CUST-A sites on R1 and R2.
R1 R2
Task 3
Configure BGP as the PE-CE Routing Protocol. Configure the CE routers based
on the Table below. Advertise the Loopback Interfaces on the CE routers in
BGP. Use 65009 as the AS # for Site 1 and 65010 as the AS # for Site 2.
R9
R10
R1
Interface loopback 0
Ip address 10.9.9.9 255.255.255.0
!
Interface E 0/0
Ip address 192.1.10.9 255.255.255.0
No shut
!
Router bgp 65009
Network 10.9.9.0 mask 255.255.255.0
Neighbour 192.1.10.1 remote-as 100
R10
Interface loopback 0
Ip address 10.10.10.10 255.255.255.0
!
Interface E 0/0
Ip address 192.1.20.10 255.255.255.0
No shut
!
Router bgp 65010
Network 10.10.10.0 mask 255.255.255.0
Neighbour 192.1.20.2 remote-as 100
Task 1
Configure a VPNv4 neighbor relationship between R5-R7 & another one
between R6 & R7 in AS 200. These relationships should be set based on the
Loopback interfaces. R5 & R6 should be route-reflector clients for R7.
R5
Task 2
Configure a VRF CUST-A with a RD value of 200:1 on R5 and R6. Use the same
extended community for your Route-target import and export. Assign this VRF
to the links that connect to CUST-A sites on R5 and R6.
R5 R6
Task 3
Configure BGP as the PE-CE Routing Protocol. Configure the CE routers based
on the Table below. Advertise the Loopback Interfaces on the CE routers in
BGP. Use 65011 as the AS # for Site 3 and 65012 as the AS # for Site 4.
R11
R12
R5
route-policy IN
pass
end-policy
!
route-policy OUT
pass
end-policy
!
router bgp 200
address-family ipv4 unicast
!
vrf CUST-A
rd 200:1
bgp router-id 6.6.6.6
address-family ipv4 unicast
!
neighbor 192.1.60.12
remote-as 65012
address-family ipv4 unicast
route-policy IN in
route-policy OUT out
!
commit
R11
Interface loopback 0
Ip address 10.11.11.11 255.255.255.0
!
Interface E 0/0
Ip address 192.1.50.11 255.255.255.0
No shut
!
Router bgp 65011
Network 10.11.11.0 mask 255.255.255.0
Neighbour 192.1.50.5 remote-as 200
R12
Interface loopback 0
Ip address 10.12.12.12 255.255.255.0
!
Task 1
Configure BGP between the ASBRs R4 & R8. Enable BGP to send labels for
any IPv4 routes that are exchanged.
R4
Interface E 0/2
ip address 192.1.48.4 255.255.255.0
no shut
!
router bgp 100
neighbor 192.1.48.8 remote-as 200
neighbor 192.1.48.8 send-label
R8
Interface E 0/2
ip address 192.1.48.8 255.255.255.0
no shut
!
router bgp 200
neighbor 192.1.48.4 remote-as 100
neighbor 192.1.48.4 send-label
Task 2
Redistribute the Loopback interfaces of the PE and RR routers in each AS into
BGP on the ASBR. These routes are providing reachability between the PE &
RR routers in both the respective AS’s. Make sure to only redistribute the
Loopbacks from OSPF into BGP and vice versa.
R4
Task 3
Configure a VPNv4 neighbor relationship between the RR’s, R3-R7, to exchange
Customer Routers with each other. Make sure to segregate the Data Plance and
Control Plance Traffic.
route-policy IN
pass
end-policy
route-policy OUT
pass
end-policy
!
router bgp 100
neighbor 7.7.7.7
remote-as 200
update-source loopback0
ebgp-multihop
address-family vpnv4 unicast
route-policy IN in
route-policy OUT out
next-hop-unchanged
!
commit
R7
route-policy IN
pass
end-policy
route-policy OUT
pass
end-policy
!
router bgp 200
neighbor 3.3.3.3
remote-as 100
update-source loopback0
ebgp-multihop
address-family vpnv4 unicast
route-policy IN in
route-policy OUT out
next-hop-unchanged
!
commit
R1
vrf definition CUST-A
address-family ipv4
route-target import 200:1
R2
vrf CUST-A
address-family ipv4 unicast
import route-target
100:1
!
commit