c in EIGRP is more complicated than that in RIP-whereas RIP only uses hop count as a metric, EIGRP uses the combined bandwidth and delay values from all the links in the path. In fact, EIGRP uses more than just these two measurements, but, by default, the other metrics are disabled. However, with redis- tribution, you must specify them, SO let's take a look at what they should be. Redistributing into EIGRP As with RIP, you can use the default-metric command to specify the metric of redis- tributed routes, or you can specify the metric on each redistribute command line. Here are the arguments required for the default-metric command in EIGRP, and the allowed ranges of values: Bandwidth in Kbps: 1-4,294,967,295 Delay in 10-microsecond units: 0-4,294,967,295 Reliability metric, where 255 is 100 percent reliable: 0-255 Effective bandwidth metric (loading), where 255 is 100 percent loaded: 1-255 Maximum Transmission Unit (MTU) metric of the path: 1-4,294,967,295 How you configure these values will largely depend on your needs at the time. Remember that redistributed routes are external routes, SO they will always have a higher administrative distance than internal routes in EIGRP. Such routes will be advertised with an administrative distance of 170. You need to make redistributed routes appear as though they are links because that's what EIGRP understands. If you wanted to make redistributed routes appear as 100 Mbps Ethernet links, you would configure the default metric like this: (config-router)# default-metric 100000 10 255 1 1500 The appropriate values to use in these commands are not always obvious. For exam- ple, the bandwidth is presented in Kbps, not bps (a 100 Mbps link is 100,000 Kbps). This reflects the way that bandwidth is shown in the show interface command: R2# sho int fo/o I include BW MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, Conversely, notice how the show interface command shows the delay of an interface: R2# sho int fo/o I include DLY MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, Here, the dela