Home > Articles > Cisco Certification > CCIE > CCIE Practical Studies: Configuring Route-Maps and Policy-based Routing

CCIE Practical Studies: Configuring Route-Maps and Policy-based Routing

Chapter Description

Route maps are like duct tape for the network—they can be applied to numerous situations to address many issues. At times, they may not be the most "pretty solutions," but they will be very effective. Karl Solie and Leah Lynch show you how to configure and use route maps.

Lab 3: Configuring Complex Route Maps and Using Tags—Part I

Practical Scenario

Route maps are one of most powerful features you can use on a router. You can use them during redistribution, in PBR, in BGP, and in many other scenarios. This lab gives you practice in configuring complex route maps that will be used during redistribution. You then practice setting and using route tags.

Lab Exercise

GameNetworks.com is an upstart company focusing on providing WAN and LAN connectivity for console games. GameNetworks.com enables its customers to play the latest and greatest console games online through its private network. GameNetworks.com has two new locations in Wisconsin and California. Your task is to configure an IP network using the following strict design guidelines:

  • Configure the GameNetworks.com IP network as depicted in Figure 2-11. Use EIGRP as the routing protocol and 2002 as the autonomous system ID on the wisconsin_x, unreal, and halo routers. Use EIGRP as the routing protocol on the california_x router and the gamenet router; the autonomous system of this router will be 65001.

  • Join the EIGRP routing domains with OSPF on the gamenet and wisconsin_x routers.

  • Configure the Frame Relay network as depicted in Figure 2-11.

  • Configure all IP addresses as depicted in Figure 2-11.

  • Use the "Lab Objectives" section for configuration specifics.

Figure 11Figure 2-11 GameNetworks.com

Lab Objectives

  • Configure the routing protocols as depicted in Figure 2-11. The only interface on wisconsin_x broadcasting EIGRP updates should be the LAN interface.

  • Configure OSPF on the wisconsin_x and gamenet routers. The serial interface of wisconsin_x will be in OSPF area 2. The serial s0.1 interface of the gamenet router is in OSPF area 2, and the LAN interface is in OSPF area 0.

  • The s0.2 interface of the gamenet router will be configured for EIGRP, using AS 65001. All interfaces of the california_x router will be in the EIGRP domain.

  • Configure a loopback interface on the unreal router with an IP address of 172.16.11.11/24, and on the halo router with an address of 172.16.6.6/24. Advertise these networks via EIGRP.

  • Assign a tag value of 100 to all routes future and present advertised by the halo router. This includes all locally connected and LAN networks. In the future, other networks may be added to the halo router; ensure that these networks get a tag of 100, too.

  • After a route is tagged with the value of 100, ensure that the tag value is preserved in the routing domain for EIGRP 65001.

  • Routes advertised only by the halo router, and no other router, should appear as OSPF type 1 routes when they arrive on the gamenet router.

  • Assign an OSPF tag value of 10 to the network 172.16.11.0/24 from the unreal router.

  • When redistributing OSPF into EIGRP 65001 on the gamenet router, only redistribute those routes with a tag value of 100. The california_x router should be able to ping the halo network of 172.16.6.0/24, but not the network 172.16.11.0/24 on the unreal router.

  • Do not allow the private LAN 10.0.101.0/24, on california_x, to be redistributed into the OSPF routing domain.

Equipment Needed

  • Six Cisco routers; three will be connected via V.35 back-to-back cable or similar fashion to a single router serving as the Frame Relay switch.

  • Four LAN segments, provided via hubs or switches. The figure shows the california_x router with two LAN interfaces; one of these interfaces may be substituted with a loopback interface.

Physical Layout and Prestaging

  • Connect the hubs and serial cables to the routers as shown in Figure 2-11.

  • A Frame Relay switch with two PVCs is also required. Example 2-35 lists the Frame Relay configuration used in this lab.

Example 2-35 Frame Relay Switch Configuration

hostname frame_switch
!
frame-relay switching
!
interface Serial0
 no ip address
 encapsulation frame-relay
 no fair-queue
 clockrate 2000000
 frame-relay intf-type dce
 frame-relay route 102 interface Serial1 101
 frame-relay route 302 interface Serial4 206
!
interface Serial1
 no ip address
 encapsulation frame-relay
clockrate 2000000
 frame-relay intf-type dce
 frame-relay route 101 interface Serial0 102
!
<<<text omitted>>>
!
interface Serial4
 no ip address
 encapsulation frame-relay
 clockrate 64000
 frame-relay intf-type dce
 frame-relay route 206 interface Serial0 302
3. Lab 3: Configuring Complex Route Maps and Using Tags—Part II | Next Section Previous Section