Lab Objective:
The focus of this lab is to understand EIGRP implementation and configuration in Cisco IOS routers. Additional technologies tested include authentication and default routing.
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please bring up the LAN interfaces connected to the routers by issuing the no shutdown command on the connected switches. If you are using a home lab with no interface fastethernet 0/0 Alternately, you can simply connect the interfaces to a hub or switch if you have one available in your own lab. Also, if you are using the www.howtonetwork.net racks, configure R3 as the Frame Relay switch using the following configuration commands: hostname R3-Frame-Relay-Switch |
Task 1
Configure hostnames and IP addressing on all routers as illustrated in the network topology.
Task 2
Configure EIGRP for AS 1 across the Frame Relay WAN as illustrated in the topology. Do NOT enable EIGRP for the point-to-point link between R1 and R2.
Task 3
Configure EIGRP for AS 2 over the LAN segment between R2 and R4 as illustrated in the topology. Do NOT enable EIGRP for the point-to-point link between R1 and R2.
Task 4
Advertise the 150.1.1.0/24 Â via EIGRP as an External EIGRP route. This route should be injected into EIGRP with a metric of 100,000 – 100 – 255 – 1 – 1500 and administrative route tag of 1111.
Additionally, advertise the 150.6.6.0/24 subnet via EIGRP 1. The route advertised by R2 should include the administrator tag 2222 and the route advertised by R4 should include the administrative tag 4444. Ensure that R1 prefers the path via R2 to reach this subnet. In the event that this path is unavailable, R1 should prefer the path via R4. In the event that the Frame Relay WAN is down, R1 should use the point-to-point link between R1 and R2. Verify your configuration using the appropriate commands.
Task 5
Configure EIGRP AS 2 so that the 150.6.6.0/24 subnet uses R2s Frame Relay connection to reach the 150.1.1.0/24 subnet. In the event that R2s Frame Relay connection is down, R4s Frame Relay connection should be used.
In the event that both R2 and R4 Frame Relay connections are down, then the point-to-point link between R1 and R2 should be used. You are NOT allowed to use offset lists or modify interface bandwidth values in your solution. Verify and test your configuration.
Lab Validation
Task 1
| Router(config)#hostname R1 R1(config)#interface fastethernet 0/0 R1(config-if)#no shutdown R1(config-if)#ip address 150.1.1.1 255.255.255.0 R1(config-if)#exit R1(config)#interface serial 0/0 R1(config-if)#ip address 10.0.1.1 255.255.255.252 R1(config-if)#no shutdown R1(config-if)#clock rate 2000000 R1(config-if)#exit R1(config)#interface serial 0/1 R1(config-if)#ip address 10.0.0.1 255.255.255.0 R1(config-if)#no shutdown R1(config-if)#encapsulation frame-relay R1(config-if)#exit |
| Router(config)#hostname R2 R2(config)#interface fastethernet 0/0 R2(config-if)#no shutdown R2(config-if)#ip address 150.6.6.2 255.255.255.0 R2(config-if)#exit R2(config)#interface serial 0/0 R2(config-if)#ip address 10.0.1.2 255.255.255.252 R2(config-if)#no shutdown R2(config-if)#exit R2(config)#interface serial 0/1 R2(config-if)#ip address 10.0.0.2 255.255.255.0 R2(config-if)#no shutdown R2(config-if)#encapsulation frame-relay R2(config-if)#exit |
| Router(config)#hostname R4 R4(config)#interface fastethernet 0/0 R4(config-if)#no shutdown R4(config-if)#ip address 150.6.6.4 255.255.255.0 R4(config-if)#exit R4(config)#interface serial 0/0 R4(config-if)#ip address 10.0.0.4 255.255.255.0 R4(config-if)#no shutdown R4(config-if)#encapsulation frame-relay R4(config-if)#exit |
Task 2
| R1(config)#router eigrp 1 R1(config-router)#no auto-summary R1(config-router)#network 10.0.0.1 0.0.0.0 R1(config-router)#exit |
| R2(config)#router eigrp 1 R2(config-router)#no auto-summary R2(config-router)#network 10.0.0.2 0.0.0.0 R2(config-router)#exit |
| R4(config)#router eigrp 1 R4(config-router)#no auto-summary R4(config-router)#network 10.0.0.4 0.0.0.0 R4(config-router)#exit |
Verify your configuration using the show ip eigrp neighbors command:
| R1#show ip eigrp neighbors IP-EIGRP neighbors for process 1 H  Address                Interface      Hold Uptime  SRTT  RTO Q Seq (sec)        (ms)      Cnt Num 1  10.0.0.4               Se0/1           145 00:00:36 1561 5000 0 3 0  10.0.0.2               Se0/1           144 00:02:30  20  200 0 3 |
| R2#show ip eigrp neighbors IP-EIGRP neighbors for process 1 H  Address                Interface      Hold Uptime  SRTT  RTO Q Seq (sec)        (ms)      Cnt Num 0  10.0.0.1               Se0/1            163 00:03:09 1240 5000 0 3 |
| R4#show ip eigrp neighbors IP-EIGRP neighbors for process 1 H  Address                Interface      Hold Uptime  SRTT  RTO Q Seq (sec)        (ms)      Cnt Num 0  10.0.0.1               Se0/0           160 00:01:18  15  200 0 5 |
Task 3
| R2(config)#router eigrp 2 R2(config-router)#no auto-summary R2(config-router)#network 150.6.6.2 0.0.0.0 R2(config-router)#exit |
| R4(config)#router eigrp 2 R4(config-router)#no auto-summary R4(config-router)#network 150.6.6.4 0.0.0.0 R4(config-router)#exit |
Verify your configuration using the show ip eigrp neighbors command:
| R2#show ip eigrp neighbors IP-EIGRP neighbors for process 1 H  Address                Interface      Hold Uptime  SRTT  RTO Q Seq (sec)        (ms)      Cnt Num 0  10.0.0.1               Se0/1           152 00:06:09 1240 5000 0 3 IP-EIGRP neighbors for process 2 |
| R4#show ip eigrp neighbors IP-EIGRP neighbors for process 1 H  Address                Interface      Hold Uptime  SRTT  RTO Q Seq (sec)        (ms)      Cnt Num 0  10.0.0.1               Se0/0           171 00:03:57  15  200 0 5 IP-EIGRP neighbors for process 2 |
Task 4
The first part of this task is completed by redistributing the 150.1.1.0/24 subnet into EIGRP using a route map to administrative tag. The metric can also be specified in the route map, or alternatively, you can specify the metric using the redistribute command. Either option is acceptable to complete this task:
| R1(config)#route-map CONNECTED permit 10 R1(config-route-map)#match interface fastethernet 0/0 R1(config-route-map)#set metric 100000 100 255 1 1500 R1(config-route-map)#set tag 1111 R1(config-route-map)#exit R1(config)#route-map CONNECTED deny 20 R1(config-route-map)#exit R1(config)#router eigrp 1 R1(config-router)#redistribute connected route-map CONNECTED R1(config-router)#exit |
The second part of this task requires redistribution metric manipulation and floating static route configuration. The 150.6.6.0/24 subnet must be redistributed into EIGRP 1 with a better route metric on R2 than on R4. Next, a floating static route is required to ensure that if the Frame Relay WAN is down, R1 will send packets to the 150.6.6.0/24 subnet via the point-to-point link to R2. The floating static route is should be configured with an administrative distance greater than 170 (external EIGRP administrative distance) but less than 255 (discard route). This task is completed by specifying an administrative distance between 171 and 254:
| R1(config)#ip route 150.6.6.0 255.255.255.0 serial 0/0 200 |
The redistribution section of this task is completed as follows:
| R2(config)#route-map CONNECTED permit 10 R2(config-route-map)#match interface fastethernet 0/0 R2(config-route-map)#set metric 100000 100 255 1 1500 R2(config-route-map)#set tag 2222 R2(config-route-map)#exit R2(config)#route-map CONNECTED deny 20 R2(config-route-map)#exit R2(config)#router eigrp 1 R2(config-router)#redistribute connected route-map CONNECTED R2(config-router)#exit |
| R4(config)#route-map CONNECTED permit 10 R4(config-route-map)#match interface fastethernet 0/0 R4(config-route-map)#set metric 10000 1000 255 1 1500 R4(config-route-map)#set tag 4444 R4(config-route-map)#exit R4(config)#route-map CONNECTED deny 20 R4(config-route-map)#exit R4(config)#router eigrp 1 R4(config-router)#redistribute connected route-map CONNECTED R4(config-router)#exit |
Verify your configuration by looking at the topology table on R1:
| R1#show ip eigrp topology 150.6.6.0 255.255.255.0 IP-EIGRP (AS 1): Topology entry for 150.6.6.0/24 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 2195456 Routing Descriptor Blocks: Â 10.0.0.2 (Serial0/1), from 10.0.0.2, Send flag is 0x0 Composite metric is (2195456/51200), Route is External Vector metric: Minimum bandwidth is 1544 Kbit Total delay is 21000 microseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1500 Hop count is 1 External data: Originating router is 150.6.6.2Â AS number of route is 0 External protocol is Connected, external metric is 0 Â Â Â Â Â Â Â Administrator tag is 2222 (0x000008AE) Â 10.0.0.4 (Serial0/1), from 10.0.0.4, Send flag is 0x0 |
Verify the floating static route configuration by shutting down the Frame Relay WAN:
| R1(config)#interface serial 0/1 R1(config-if)#shutdown R1(config-if)#exit R1(config)#do show ip route 150.6.6.0 255.255.255.0 Routing entry for 150.6.6.0/24 Known via “static”, distance 200, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via Serial0/0 Route metric is 0, traffic share count is 1 |
Task 5
The first requirement of this task is that the 150.1.1.0/24 subnet should known within EIGRP AS 2. This requires that EIGRP 1 be redistributed into EIGRP 2 on R2 and R4:
| R2(config)#router eigrp 2 R2(config-router)#redistribute eigrp 1 R2(config-router)#exit |
| R4(config)#router eigrp 2 R4(config-router)#redistribute eigrp 1 R4(config-router)#exit |
The second requirement is completed by modifying the default interface delay values so that routes received via R4 are less preferable to those received via R2.
To influence path selection, increase the delay on R4s Frame Relay interface OR decrease the delay on R2s Frame Relay interface. Either solution is acceptable.
| R2(config)#int s 0/1 R2(config-if)#delay 100 R2(config-if)#exit |
Following this change, R2 and R4 show the following route entries for the 150.1.1.0/24 subnet:
| R2#show ip route 150.1.1.0 255.255.255.0 Routing entry for 150.1.1.0/24 Known via “eigrp 1”, distance 170, metric 1709056 Tag 1111, type external Redistributing via eigrp 1, eigrp 2 Advertised by eigrp 2 Last update from 10.0.0.1 on Serial0/1, 00:00:42 ago Routing Descriptor Blocks: * 10.0.0.1, from 10.0.0.1, 00:00:42 ago, via Serial0/1 Route metric is 1709056, traffic share count is 1 Total delay is 2000 microseconds, minimum bandwidth is 1544 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 1 Route tag 1111 |
| R4#show ip route 150.1.1.0 255.255.255.0 Routing entry for 150.1.1.0/24 Known via “eigrp 2”, distance 170, metric 1711616 Tag 1111, type external Redistributing via eigrp 2 Last update from 150.6.6.2 on FastEthernet0/0, 00:01:04 ago Routing Descriptor Blocks: * 150.6.6.2, from 150.6.6.2, 00:01:04 ago, via FastEthernet0/0 Route metric is 1711616, traffic share count is 1 Total delay is 2100 microseconds, minimum bandwidth is 1544 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 2 Route tag 1111 |
The third required requires a floating static route to be configured on R2 for the 150.1.1.0/24 subnet. This floating static will also need to be redistributed into EIGRP 2 so that R4 receives this route when the Frame Relay WAN in down. This task is completed as follows:
| R2(config)#ip route 150.1.1.0 255.255.255.0 serial 0/0 200 name R1-BACKUP R2(config)#router eigrp 2 R2(config-router)#redistribute static metric 5000 5000 255 1 1500 R2(config-router)#exit |
Finally, verify that routing works as required. Shut down the Frame Relay WAN link on R2 and ensure that this router can still reach the 150.1.1.0/24 subnet and vice-versa across the Frame Relay network, i.e. via R4:
| R2(config)#int s0/1 R2(config-if)#shutdown R2(config-if)#exit R2(config)#do show ip route 150.1.1.0 255.255.255.0 Routing entry for 150.1.1.0/24 Known via “eigrp 2”, distance 170, metric 2198016 Tag 1111, type external Redistributing via eigrp 2 Last update from 150.6.6.4 on FastEthernet0/0, 00:00:14 ago Routing Descriptor Blocks: Â * 150.6.6.4, from 150.6.6.4, 00:00:14 ago, via FastEthernet0/0 Route metric is 2198016, traffic share count is 1 Total delay is 21100 microseconds, minimum bandwidth is 1544 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 2 Route tag 1111 R2(config)#do ping 150.1.1.1 source 150.6.6.2 Type escape sequence to abort. |
Next, shut down the Frame Relay WAN link on R4 and ensure that both R2 and R4 can still reach the 150.1.1.0/24 subnet and vice-versa:
| R2(config)#int s0/1 R2(config-if)#shutdown R2(config-if)#exit |
| R4(config)#int s0/0 R4(config-if)#shutdown R4(config-if)#exit |
| R1#show ip route 150.6.6.0 255.255.255.0 Routing entry for 150.6.6.0/24 Known via “static”, distance 200, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via Serial0/0 Route metric is 0, traffic share count is 1 |
| R2#show ip route 150.1.1.0 255.255.255.0 Routing entry for 150.1.1.0/24 Known via “static”, distance 200, metric 0 (connected) Redistributing via eigrp 2 Advertised by eigrp 2 metric 5000 5000 255 1 1500 Routing Descriptor Blocks: * directly connected, via Serial0/0 Route metric is 0, traffic share count is 1 |
| R4#show ip route 150.1.1.0 255.255.255.0 Routing entry for 150.1.1.0/24 Known via “eigrp 2”, distance 170, metric 1794560, type external Redistributing via eigrp 2 Last update from 150.6.6.2 on FastEthernet0/0, 00:00:47 ago Routing Descriptor Blocks: * 150.6.6.2, from 150.6.6.2, 00:00:47 ago, via FastEthernet0/0 Route metric is 1794560, traffic share count is 1 Total delay is 50100 microseconds, minimum bandwidth is 5000 Kbit Reliability 255/255, minimum MTU 1500 bytes Loading 1/255, Hops 1 |
| R1#ping 150.6.6.0 source 150.1.1.1Â Â Â Â Â
Type escape sequence to abort. |
| R2#ping 150.1.1.0 source 150.6.6.2
Type escape sequence to abort. |
| R4#ping 150.1.1.0 source 150.6.6.4
Type escape sequence to abort. |
Final Router Configurations
R1
|
R1#term len 0 Current configuration : 1143 bytes R1# |
R2
|
R2#term len 0 Current configuration : 1281 bytes R2# |
R3
|
R3-Frame-Relay-Switch#term len 0 Current configuration : 1556 bytes R3-Frame-Relay-Switch# |
R4
|
R4#term len 0 Current configuration : 1137 bytes R4# |