Labs – EIGRP Multi-Technology Lab – Lab Validation

Task 1

Task 2

Verify your configuration using the show ip eigrp topology command or using the show ip eigrp interfaces command:

To view the redistributed 172.x.x.x subnets, you must use the show ip eigrp topology command as these are not included in the show ip eigrp interfaces output.

Task 3

Verify your configuration using the show ip eigrp topology command or using the show ip eigrp interfacescommand:

Task 4

Verify your configuration using the show ip eigrp topology command or using the show ip eigrp interfacescommand:

Task 5

Verify your configuration using the show ip eigrp topology command or using the show ip eigrp interfacescommand:

Use the show ip protocols command to verify the stub configuration on R4. By default, a stub router will advertise connected and summary routes:

On the stub neighbor router, R3, use the show ip eigrp neighbors detail command to validate the stub peer status for R4:

Task 6

Given the requirements, this configuration requires the use of two distribute lists for the EIGRP route filtering. This configuration is implemented on R3 as follows:

Verify your configuration using the show ip route eigrp command. If your configuration is correct, the following entries should be reflected in the routing table on R3:

Task 7

Given the requirements, this configuration requires the use of a distribute list for the R3 EIGRP route filtering plus the use of the ip summary-address command to generate and advertise the default route to R4. This configuration is implemented on R3 as follows:

Use the show ip route command on R4 to verify that only the default route is received:

Use simple ping tests to verify that R4 can ping the 172.x.x.x and 150.x.x.x subnets:

Task 8

This task requires some thought. First, the task calls for load balancing and not for load sharing. Therefore, thevariance command cannot be used. In order to ensure that the metrics are the same, EIGRP offset lists will need to be used. The simplest method will be to offset the route metric of the best route such that it is equal to that of the worst (second) route. This will ensure that both routes have the same metric and EIGRP will automatically load balance. To complete this task, first use the show ip eigrp topology command to determine the route metrics:

Next, subtract the lowest (best) metric from the highest (worst) metric. Using the output above, we subtract 2172416 from 2684416 leaving us with a balance of 512000. The same logic is also applicable to the 150.2.2.0/24 prefix:

Following the same logic, if we subtract 2195456 from 2707456 the remaining balance is 512000. Following this, the offset lists are configured on R3 as follows:

Next, verify the load balancing using the show ip route command for both prefixes. R3 will now show the following for the 150.1.1.0/24 prefix:

R3 will now show the following for the 150.2.2.0/24 prefix:

Task 9

Remember that when configuring EIGRP authentication, the key chain name does NOT need to be the same; however, the key number used for authentication must be the same.

Next, use the show ip eigrp interfaces detail command to validate the configuration:

Task 10

As described in the ROUTE guide, an alternative method that can be used for route filtering is to use the distancecommand. Before implementing this configuration, R1 shows the following Loopback 0 subnet entries in the routing table:

The configuration required to complete this task is implemented as follows:

Following this configuration, the Loopback0 subnets are no longer present in the routing table:

You can also use the show ip access-lists command to see matches against the ACL: