her 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, configure the default metric like this: B(config-router)#default-metric 100000 10 255 1 1500 The appropriate values to use in these commands are not always obvious. For example, the bandwidth is presented in Kbps, not bps (a 100 Mbps link is 100,000 Kbps). This reflects the way bandwidth is displayed in the show interface command: R2#sho int fo/o 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 include DLY MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, Here, the delay is shown in microseconds, but when you specify the delay in redistrib- ution, you must use 10-microsecond units. That is, to achieve a delay of 100 micro- seconds, you specify a delay value of 10. When I configure redistribution, I always make the reliability 255, loading 1, and MTU 1500. In fact, I usually make the redistributed routes appear as 100 Mbps links, as shown previously. Keep it simple. While there may be instances where you'll want to alter these values, those instances will be rare. The method of specifying a default metric and overriding it with a specific metric de- scribed earlier in the section "Redistributing into RIP" on page 149 is also valid with EIGRP. Here, I've specified a default metric reflecting a 100 Mbps link with a delay of 100 microseconds, and I'm redistributing OSPF process 100 with a metric reflecting a 1,000 Mbps link with a delay of 50 microseconds: router eigrp 100 redistribute ospf 100 metric 1000000 5 255 1 1500 network 10.0.0.0 Redistributing into EIGRP default-metric 100000 10 255 1 1500 no auto-summary When redistributing OSPF routes into another protocol, you can limit the types of routes t