Technical Overview of EIGRP
| < Free Open Study > |
Lab 20: Integrating RIP Networks: Redistribution, Route Filtering, and Control ”Part IILab WalkthroughAttach the four routers in a back-to-back manner to the Frame Relay switch. Use V.35 cables or CSU/DSUs with crossover cables to connect the routers to the Frame Relay switch. Create the four LANs by the use of switches or hubs/MAUs. When the physical connections are complete, assign IP addresses to all LAN interfaces, as depicted in Figure 9-7. Be sure that you can ping the router's local LAN interface before moving on. First, we will focus on configuring the routers in the RIP domain. Start by configuring a multipoint subinterface on the habanos router. The network between habanos, montecristo, and romeo_y_julieta is a multipoint network, so you need to use frame-relay map statements. Example 9-13 shows this portion of the Frame Relay configuration. Example 9-13 Frame Relay Configuration Part 1 ”RIP! hostname habanos ! interface Serial0.1 multipoint ip address 150.100.100.1 255.255.255.0 no arp frame-relay frame-relay map ip 150.100.100.2 110 broadcast frame-relay map ip 150.100.100.3 120 broadcast no frame-relay inverse-arp _______________________________________________________________________________ hostname montecristo ! interface Serial0 ip address 150.100.100.2 255.255.255.0 no ip directed-broadcast encapsulation frame-relay no ip mroute-cache frame-relay map ip 150.100.100.1 111 broadcast frame-relay map ip 150.100.100.3 111 broadcast frame-relay lmi-type cisco _______________________________________________________________________________ hostname romeo_y_julieta ! interface Serial0 ip address 150.100.100.3 255.255.255.0 no ip directed-broadcast encapsulation frame-relay no ip mroute-cache frame-relay map ip 150.100.100.1 121 broadcast frame-relay map ip 150.100.100.2 121 broadcast frame-relay lmi-type cisco At this point, you should be able to ping the WAN interfaces that you configured. To configure RIP, use the router rip and the network 150.100.0.0 commands on each router in the RIP domain. Because the Frame Relay network is a multipoint network, you need to disable split horizons on the habanos router. Without disabling split horizons, the montecristo Token Ring network will not propagate to the romeo_y_julieta router. The opposite also is true. To disable split “horizons, use the no ip split-horizon command on the Serial0.1 interface on the habanos router. Now that the RIP domain is complete, let's begin to configure the EIGRP domain. The first step is to configure a Frame Relay point-to-point network between the habanos and churchill_imports router. Example 9-14 shows the configuration, which uses Frame Relay inverse ARP. Example 9-14 Frame Relay Configuration Part 2 ”EIGRP! hostname habanos ! interface Serial0.2 point-to-point ip address 150.100.200.1 255.255.255.252 frame-relay interface-dlci 130 ! _______________________________________________________________________________ ! hostname churchill_imports ! interface Serial0 ip address 150.100.200.2 255.255.255.252 encapsulation frame-relay no fair-queue frame-relay interface-dlci 131 ! The EIGRP configuration is almost identical to the RIP configuration. Use the router eigrp 2001 command along with the network 150.100.0.0 statement on the habanos and churchill_imports routers. If you need more assistance in configuring EIGRP, see Chapter 11, "Hybrid: Enhanced Interior Gateway Routing Protocol (EIGRP)." To have full IP connectivity, you need to mutually redistribute between RIP and EIGRP on the habanos router. To accomplish this, use the redistribute command along with a default metric. The default metric for RIP is 2, and the default metric for EIGRP is 10000 1000 254 1 1500. Use the passive-interface command to avoid sending both RIP and EIGRP route updates out the same interface. Example 9-15 shows the updated configuration on habanos. Example 9-15 Routing Protocol Configuration on habanos! hostname habanos ! router eigrp 2001 redistribute rip You now should have a full routing table on the churhcill_imports router. You can see two EIGRP routes, 150.100.100.0/24 and 150.100.10.0/24 because the EIGRP distance is lower then that of RIP. You can also see two external EIGRP routes, 150.100.2.0/24 and 150.100.1.0/24, which come from RIP being redistributed into EIGRP. Example 9-16 shows the updated routing table for the churchill_imports router. Example 9-16 Routing Table of churchill_imports churchill_imports# show ip route <<<text omitted>>> 150.100.0.0/16 is variably subnetted, 6 subnets, 2 masks C 150.100.200.0/30 is directly connected, Serial0 D 150.100.100.0/24 [90/2681856] via 150.100.200.1, 00:29:52, Serial0 D EX 150.100.2.0/24 [170/2425856] via 150.100.200.1, 00:18:01, Serial0 C 150.100.3.0/24 is directly connected, Ethernet0 D EX 150.100.1.0/24 [170/2425856] via 150.100.200.1, 00:18:01, Serial0 D 150.100.10.0/24 [90/2195456] via 150.100.200.1, 00:29:52, Serial0 churchill_imports# The configuration is almost complete; however, if you observe the routing table on montecristo in Example 9-17, you see that the 150.100.200.0/30 route is missing from the table. Example 9-17 Routing Table of montecristo montecristo# show ip route <<<text omitted>>> 150.100.0.0/24 is subnetted, 5 subnets C 150.100.100.0 is directly connected, Serial0 R 150.100.2.0 [120/2] via 150.100.100.1, 00:00:05, Serial0 R 150.100.3.0 [120/2] via 150.100.100.1, 00:00:05, Serial0 C 150.100.1.0 is directly connected, TokenRing0 R 150.100.10.0 [120/1] via 150.100.100.1, 00:00:05, Serial0 montecristo# The 150.100.200.0/30 route is missing from the table because the bit mask is on a 30-bit boundary, and RIP does not forward the update out the Serial0.1 port of the habanos router. To remedy this, you need to summarize EIGRP on a 24-bit boundary on the Frame Relay link between habanos and the churchill_imports routers. To summarize the route, use the ip summary-address eigrp 2001 150.100.200.0 255.255.255.0 command on the Serial 0 interface of the churchill_imports router. You now can observe the routing table on montecristo and see that it has a summary route to 150.100.200.0/24, as demonstrated in Example 9-18. Example 9-18 Complete Routing Table on montecristomontecristo# show ip route <<<text omitted>>> 150.100.0.0/24 is subnetted, 6 subnets R 150.100.200.0 [120/2] via 150.100.100.1, 00:00:02, Serial0 C 150.100.100.0 is directly connected, Serial0 R 150.100.2.0 [120/2] via 150.100.100.1, 00:00:02, Serial0 R 150.100.3.0 [120/2] via 150.100.100.1, 00:00:02, Serial0 C 150.100.1.0 is directly connected, TokenRing0 R 150.100.10.0 [120/1] via 150.100.100.1, 00:00:02, Serial0 montecristo# TIP When you are modeling complex networks, it might take a while for network convergence and routes to propagate. You can force a route update to speed this process along by using the clear ip route * command. This flushes all routes and force routing updates to happen. When you have full IP connectivity, you can start to filter routes. In this model, you want prevent the route 150.100.10.0/24 from being propagated to the montecristo and romeo_y_julieta routers. To accomplish this, use a distribute-list out under the RIP portion of the habanos router. You also need to define an access list filtering out the network 150.100.10.0. Example 9-19 shows the final configurations. Example 9-19 Complete Routing Listingshostname habanos ! interface Ethernet2 ip address 150.100.10.1 255.255.255.0 media-type 10BaseT interface Serial0 no ip address encapsulation frame-relay no ip mroute-cache ! interface Serial0.1 multipoint ip address 150.100.100.1 255.255.255.0 no ip split-horizon no arp frame-relay frame-relay map ip 150.100.100.2 110 broadcast frame-relay map ip 150.100.100.3 120 broadcast no frame-relay inverse-arp ! interface Serial0.2 point-to-point ip address 150.100.200.1 255.255.255.252 frame-relay interface-dlci 130 ! router eigrp 2001 redistribute rip passive-interface Ethernet2 passive-interface Serial0.1 network 150.100.0.0 default-metric 10000 1000 254 1 1500 ! router rip redistribute eigrp 2001 passive-interface Serial0.2 network 150.100.0.0 default-metric 2 distribute-list 10 out Serial0.1 ! ip classless ! access-list 10 deny 150.100.10.0 0.0.0.255 access-list 10 permit any _______________________________________________________________________________ hostname montecristo ! ip subnet-zero ! interface Serial0 ip address 150.100.100.2 255.255.255.0 no ip directed-broadcast encapsulation frame-relay no ip mroute-cache frame-relay map ip 150.100.100.1 111 broadcast frame-relay map ip 150.100.100.3 111 broadcast frame-relay lmi-type cisco ! interface TokenRing0 ip address 150.100.1.1 255.255.255.0 no ip directed-broadcast ring-speed 16 ! router rip network 150.100.0.0 ! ip classless _______________________________________________________________________________ hostname romeo_y_julieta ! ip subnet-zero ! interface Ethernet0 ip address 150.100.2.1 255.255.255.0 no ip directed-broadcast ! interface Serial0 ip address 150.100.100.3 255.255.255.0 no ip directed-broadcast encapsulation frame-relay no ip mroute-cache frame-relay map ip 150.100.100.1 121 broadcast frame-relay map ip 150.100.100.2 121 broadcast frame-relay lmi-type cisco ! router rip network 150.100.0.0 _______________________________________________________________________________ hostname churchill_imports ! interface Ethernet0 ip address 150.100.3.1 255.255.255.0 ! interface Serial0 ip address 150.100.200.2 255.255.255.252 ip summary-address eigrp 2001 150.100.200.0 255.255.255.0 encapsulation frame-relay no fair-queue frame-relay interface-dlci 131 ! router eigrp 2001 network 150.100.0.0 ! Finally, the optional portion of the lab specifies that you need to configure the administrative distance of all routes from romeo_y_julieta to be set to 5. To produce this result, use the distance command under RIP. In this model, you don't want to set the entire distance of RIP to 5, but you want to set just the distance of routes from one neighbor. Therefore, you need to call an access list on the distance command as well, as demonstrated in Example 9-20. Example 9-20 Setting the Distance for Specific Routeshostname habanos ! router rip redistribute eigrp 2001 passive-interface Serial0.2 network 150.100.0.0 default-metric 2 distribute-list 10 out Serial0.1 distance 5 150.100.100.3 0.0.0.0 11 Finally, viewing the route table on the habanos router in Example 9-21 shows that the route 150.100.2.0 has an administrative distance of 5, versus the default distance of 120. Example 9-21 Setting the Distance for Specific Routeshabanos# show ip route Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR Gateway of last resort is not set 150.100.0.0/16 is variably subnetted, 7 subnets, 2 masks D 150.100.200.0/24 [90/2681856] via 150.100.200.2, 00:04:42, Serial0.2 C 150.100.200.0/30 is directly connected, Serial0.2 C 150.100.100.0/24 is directly connected, Serial0.1 R 150.100.2.0/24 [5/1] via 150.100.100.3, 00:00:20, Serial0.1 D 150.100.3.0/24 [90/2195456] via 150.100.200.2, 00:04:42, Serial0.2 R 150.100.1.0/24 [120/1] via 150.100.100.2, 00:00:07, Serial0.1 C 150.100.10.0/24 is directly connected, Ethernet2 habanos# |
| < Free Open Study > |
EAN: 2147483647
Pages: 283