Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Cisco CCIP MPLS Study Guide - James Reagan.pdf
Скачиваний:
250
Добавлен:
24.05.2014
Размер:
6.47 Mб
Скачать

398 Appendix A Challenge Labs

Atlanta(config-router)#address-family ipv4 vrf peer_vpn

Atlanta(config-router-af)#redistribute ospf 1 vrf peer_vpn

Raleigh#conf t

Enter configuration commands, one per line. End with CNTL/Z. Raleigh(config)#router ospf 1 vrf peer_vpn

Raleigh(config-router-af)#redistribute bgp 65000 metric transparent

Raleigh(config-router-af)#exit Raleigh(config-router)#exit Raleigh(config)#router bgp 65000

Raleigh(config-router)#address-family ipv4 vrf peer_vpn Raleigh(config-router-af)#redistribute ospf 1 vrf peer_vpn

Challenge Lab 5

The following challenge lab tests your ability to configure a VRF, a route distinguisher, a route target, static routes as a PE-CE routing protocol, and static route redistribution into MP-BGP. Note that the network is already set up with MPLS and MP-BGP (AS 65000).

Serial

0

Serial

0/1

Serial

0/0

Serial

0/1

Serial

0/0

Serial

0/3

Serial

0/1

Serial

0

 

 

 

 

 

 

 

 

Peer 1

 

Atlanta

 

 

 

Core

 

 

Raleigh

 

 

 

Peer 2

You need to know all the interfaces and IP addressing contained in the

following two tables:

 

 

Customer Addressing

 

 

 

 

 

Device

Loopback 0

Serial 0

 

 

 

Peer1

192.168.1.1/32

192.168.3.5/30

Peer2

192.168.2.1/32

192.168.3.10/30

 

 

 

Copyright ©2002 SYBEX, Inc., Alameda, CA

www.sybex.com

Challenge Lab 5 399

Service Provider Addressing

Device

Loopback 0

Serial 0/0

Serial 0/1

Serial 0/3

 

 

 

 

 

Atlanta

204.134.83.1/32

204.134.83.5/30

192.168.3.6/30

N/A

Core

204.134.83.2/32

204.134.83.9/30

204.134.83.6/30

N/A

Raleigh

204.134.83.3/32

N/A

192.168.3.9/30

204.134.83.10/30

 

 

 

 

 

VRF Configuration

This section includes the following lab exercise:

Lab 5.1: Configure a VRF, a route distinguisher, and a route target

L A B 5 . 1

Configure a VRF, a route distinguisher, and a route target

1.On the Atlanta POP router, create a VRF called peer_vpn.

2.On the Atlanta POP router, assign a route distinguisher of 50:1.

3.On the Atlanta POP router, configure an import route target and an export route target of 50:1.

4.On the Atlanta POP router, associate the PE-CE interface with the VRF and assign the appropriate address from the table.

5.On the Raleigh POP router, create a VRF called peer_vpn.

6.On the Raleigh POP router, assign a route distinguisher of 50:1.

7.On the Raleigh POP router, configure an import route target and an export route target of 50:1.

8.On the Raleigh POP router, associate the PE-CE interface with the VRF and assign the appropriate address from the table.

Static Routes and Redistribution

This section includes the following lab exercise:

Lab 5.2: Configure static routes on the peer and PE devices and configure redistribution static routes and connected interfaces

Copyright ©2002 SYBEX, Inc., Alameda, CA

www.sybex.com

400 Appendix A Challenge Labs

L A B 5 . 2

Configure static routes on the peer and PE devices

and configure redistribution static routes and connected interfaces

1.On Peer 1, configure a default route using the Serial 0 interface.

2.On Peer 2, configure a default route using the Serial 0 interface.

3.On the Atlanta POP router, configure a static route to the Loopback 0 interface of Peer 1 for the VRF.

4.On the Atlanta POP router, configure redistribution of the static route and the VRF connected interface.

5.On the Raleigh POP router, configure a static route to the Loopback 0 interface of Peer 2 for the VRF.

6.On the Raleigh POP router, configure redistribution of the static route and the VRF connected interface.

Answer to Lab 5.1

Atlanta#conf t

Enter configuration commands, one per line. End with CNTL/Z. Atlanta(config)#ip vrf peer_vpn

Atlanta(config-vrf)#rd 50:1 Atlanta(config-vrf)#route-target both 50:1 Atlanta(config-vrf)#exit Atlanta(config)#int s 0/1

Atlanta(config-if)#ip vrf forwarding peer_vpn

%Interface Serial0/1 IP address 192.168.3.6 removed due to enabling VRF peer_vpn

Atlanta(config-if)#ip address 192.168.3.6 255.255.255.252

Raleigh#conf t

Enter configuration commands, one per line. End with CNTL/Z. Raleigh(config)#ip vrf peer_vpn

Raleigh(config-vrf)#rd 50:1 Raleigh(config-vrf)#route-target both 50:1

Copyright ©2002 SYBEX, Inc., Alameda, CA

www.sybex.com

Challenge Lab 5 401

Raleigh(config-vrf)#exit

Raleigh(config)#int s 0/1

Raleigh(config-if)#ip vrf forwarding peer_vpn

% Interface Serial0/1 IP address 192.168.3.9 removed due to enabling VRF peer_vpn

Raleigh(config-if)#ip address 192.168.3.9 255.255.255.252

Answer to Lab 5.2

Peer1#conf t

Enter configuration commands, one per line. End with CNTL/Z. Peer1(config)# ip route 0.0.0.0 0.0.0.0 serial 0

Peer1(config)#^Z Peer1#

Peer2#conf t

Enter configuration commands, one per line. End with CNTL/Z. Peer2(config)#ip route 0.0.0.0 0.0.0.0 serial 0

Peer2(config)#^Z Peer2#

Atlanta#conf t

Enter configuration commands, one per line. End with CNTL/Z. Atlanta(config)# ip route vrf vpn_1 192.168.1.1

255.255.255.255 Serial0/1 192.168.3.5

Atlanta(config)#router bgp 65000

Atlanta(config-router)#address-family ipv4 vrf peer_vpn

Atlanta(config-router-af)#redistribute connected Atlanta(config-router-af)#redistribute static Atlanta(config-router-af)#^Z

Atlanta#

Raleigh#conf t

Enter configuration commands, one per line. End with CNTL/Z. Raleigh(config)# ip route vrf vpn_1 192.168.2.1

255.255.255.255 Serial0/1 192.168.3.10

Copyright ©2002 SYBEX, Inc., Alameda, CA

www.sybex.com