In the figure, R2 is configured with the subnet 192.168.10.8 and the wildcard mask 0.0.0.3. R2(config-router)#network 192.168.10.8 0.0.0.

3 Some IOS versions will also let you simply enter the subnet mask. For example, you might enter the following: R2(config-router)#network 192.168.10.8 255.255.255.252 However, the IOS will then convert the command to the wildcard mask format, as can be verified with the show run command: R2#show run <some output omitted> ! router eigrp 1 network 172.16.0.0 network 192.168.10.8 0.0.0.3 auto-summary

Use the show ip eigrp neighbors command to view the neighbor table and verify that EIGRP has established an adjacency with its neighbors.

show ip protocols command can be used to verify that EIGRP is enabled.

To verify that EIGRP and other functions of the router are configured properly is to examine the routing tables with the show ip route command. Notice that EIGRP routes are denoted in the routing table with a D, which stands for DUAL.

Null0 is not an actual interface. Notice that the summary routes are sourced from Null0 - this is because these routes are used for advertisement purposes. The 192.168.10.0/24 and 172.16.0.0/16 routes do not actually represent a path to reach the parent networks. If a packet does not match one of the level 2 child routes, it is sent to the Null0 interface. In other words, if the packet matches the level 1 parent the classful network address - but none of the subnets, the packet is discarded. Note: EIGRP automatically includes a null0 summary route as a child route whenever both of following conditions exist: There is at least one subnet that was learned via EIGRP. Automatic summarization is enabled. null0 summary route is removed when automatic summary is disabled.

The routing table for R3 shows that both R1 and R2 are automatically summarizing the 172.16.0.0/16 network and sending it as a single routing update. R1 and R2 are not propagating the individual subnets because of automatic summarization. We will turn off automatic summarization later. Because R3 is getting two equal cost routes for 172.16.0.0/16 from both R1 and R2, both routes are included in the routing table.

show ip protocols command is used to verify the K values. The command output for R1 is shown in the figure. Notice that the K values on R1 are set to the default.

show interface command we can examine the actual values used for bandwidth, delay, reliability, and load in the computation of the routing metric. The output in the figure shows the values used in the composite metric for the Serial 0/0/0 interface on R1. MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255

Delay Delay is a measure of the time it takes for a packet to traverse a route. The delay (DLY) metric is a static value based on the type of link to which the interface is connected and is expressed in microseconds. Delay is not measured dynamically. In other words, the router does not actually track how long packets are taking to reach the destination. The delay value, much like the bandwidth value, is a default value that can be changed by the network administrator. MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, reliability 255/255, txload 1/255, rxload 1/255 The table in the figure shows the default delay values for various interfaces. Notice that the default value is 20,000 microseconds for Serial interfaces and 100 microseconds for FastEthernet interfaces.

On most serial links, the bandwidth metric will default to 1544 Kbits. Because both EIGRP and OSPF use bandwidth in default metric calculations, a correct value for bandwidth is very important to the accuracy of routing information. But what do you do if the actual bandwidth of the link does not match the default bandwidth of the interface? Use the interface command bandwidth to modify the bandwidth metric: Router(config-if)#bandwidth kilobits Use the interface command no bandwidth to restore the default value. In the figure, the link between R1 and R2 has a bandwidth of 64 kbps, and the link between R2 and R3 has a bandwidth of 1024 kbps. The figure shows the configurations used on all three routers to modify the bandwidth on the appropriate serial interfaces.

We can verify the change using the show interface command. It is important to modify the bandwidth metric on both sides of the link to ensure proper routing in both directions.

A successor is a neighboring router that is used for packet forwarding and is the least-cost route to the destination network. The IP address of a successor is shown in a routing table entry right after the word via.

show ip eigrp topology The successor, feasible distance, and any feasible successors with their reported distances are kept by a router in its EIGRP topology table or topology database. As shown in the figure, the topology table can be viewed using the show ip eigrp topology command. The topology table lists all successors and feasible successors that DUAL has calculated to destination networks.

A detailed description of each part of the topology table entry for destination network 192.168.1.0/24 appears below. The first line displays: P - This route is in the passive state. When DUAL is not performing its diffusing computations to determine a path for a network, the route will be in a stable mode, known as the passive state. If DUAL is recalculating or searching for a new path, the route will be in an active state. All routes in the topology table should be in the passive state for a stable routing domain. DUAL will display an A if the route is "Active," 192.168.1.0/24 - This is the destination network that is also found in the routing table. 1 successors - This shows the number of successors for this network. If there are multiple equal cost paths to this network, there will be multiple successors. FD is 3014400 - This is the feasible distance, the EIGRP metric to reach the destination network. The first entry shows the successor: via 192.168.10.10 - This is the next-hop address of the successor, R3. This address is shown in the routing table. 3014400 - This is the feasible distance to 192.168.1.0/24. It is the metric shown in the routing table. 28160 - This is the reported distance of the successor and is R3's cost to reach this network. Serial0/0/1 - This is the outbound interface used to reach this network, also shown in the routing table.

The second entry shows the feasible successor, R1 (if there is not a second entry, then there are no feasible successors): via 172.16.3.1 - This is the next-hop address of the feasible successor, R1. 41026560 - This would be R2's new feasible distance to 192.168.1.0/24 if R1 became the new successor. 2172416 - This is the reported distance of the feasible successor or R1's metric to reach this network. This value, RD, must be less than the current FD of 3014400 to meet the feasibility condition. Serial0/0/0 - This is the outbound interface used to reach feasible successor, if this router becomes the successor.

Null0 Analyzing a routing table containing EIGRP routes can be confusing due to EIGRP's automatic inclusion of Null0 summary routes. In the figure, R1's routing table contains two routes that have an exit interface of Null0. Remember from Chapter 7, "RIPv2," that the Null0 interface is simply a route to nowhere, commonly known as "the bit bucket." So by default, EIGRP uses the Null0 interface to discard any packets that match the parent route but do not match any of the child routes. You might think that if we configure classless routing behavior with the ip classless command, EIGRP would not discard that packet but would continue looking for a default or supernet route. However, the EIGRP Null0 summary route is a child route that will match any possible packets of the parent route that do not match another child route. Even with classless routing behavior, ip classless, where you would expect the route lookup process to check for supernets and default routes, EIGRP will use the Null0 summary route and discard the packet because this route will match any packets of the parent that do not have a child route.

EIGRP, by default, uses the auto-summary command. In the next topic, you will see that disabling automatic summarization will remove the Null0 summary route and allow EIGRP to look for a supernet or default route when an EIGRP child route does not match a destination packet.

no auto-summary As in RIPv2, automatic summarization can be disabled with the no auto-summary command. The router configuration command eigrp log-neighbor-changes is on by default on some IOS implementations. If on, you will see output similar to that shown for R1. DUAL takes down all neighbor adjacencies and then reestablishes them so that the effect of the no auto-summary command can be fully realized. All EIGRP neighbors will immediately send out a new round of updates that will not be automatically summarized.

Click R1, R2, and R3 in the figure.

We can see in the routing tables for all three routers that EIGRP is now propagating individual subnets. Notice that EIGRP no longer includes the Null0 summary route, because automatic summarization has been disabled with no auto-summary. As long as the default classless routing behavior (ip classless) is in effect, supernet and default routes will be used when there is not a match with a subnet route.

Configure EIGRP Manual Summarization To establish EIGRP manual summarization on all interfaces that send EIGRP packets, use the following interface command: Router(config-if)#ip summary-address eigrp as-number network-address subnet-mask Because R3 has two EIGRP neighbors, the EIGRP manual summarization in configured on both Serial 0/0/0 and Serial 0/0/1.

Using a static route to 0.0.0.0/0 as a default route is not routing protocol dependent. The "quad zero" static default route can be used with any currently supported routing protocols. The static default route is usually configured on the router that has a connection to a network outside the EIGRP routing domain, for example, to an ISP. EIGRP requires the use of the redistribute static command to include this static default route with its EIGRP routing updates. The redistribute static command tells EIGRP to include this static route in its EIGRP updates to other routers. The figure shows the configuration of the static default route and the redistribute static command on router R2.

By default, EIGRP will use only up to 50 percent of the bandwidth of an interface for EIGRP information. This prevents the EIGRP process from over-utilizing a link and not allowing enough bandwidth for the routing of normal traffic. The ip bandwidth-percent eigrp command can be used to configure the percentage of bandwidth that may be used by EIGRP on an interface. Router(config-if)#ip bandwidth-percent eigrp as-number percent

Configuring Hello Intervals and Hold Times Hello intervals and hold times are configurable on a per-interface basis and do not have to match with other EIGRP routers to establish adjacencies. The command to configure a different hello interval is: Router(config-if)#ip hello-interval eigrp as-number seconds If you change the hello interval, make sure that you also change the hold time to a value equal to or greater than the hello interval. Otherwise, neighbor adjacency will go down after the hold time expires and before the next hello interval. The command to configure a different hold time is: Router(config-if)#ip hold-time eigrp as-number seconds

The seconds value for both hello and hold time intervals can range from 1 to 65,535. This range means that you can set the hello interval to a value of just over 18 hours, which may be appropriate for a very expensive dialup link. However, in the figure we configure both R1 and R2 to use a 60-second hello interval and 180-second hold time. The no form can be used on both of these commands to restore the default values.