In the sho route command below you'll see that the ASA sees three paths to the network 10.1.48.0/23.
But it has selected 10.1.0.8 as the preferred path. How does the ASA end up selecting it as the preferred next hop?
ASA01/pri/act# sho route 10.1.48.0
Routing entry for 10.1.48.0 255.255.254.0
Known via "eigrp 10", distance 90, metric 3072, type internal
Redistributing via eigrp 10
Last update from 10.1.0.8 on INSIDE, 0:00:04 ago
Routing Descriptor Blocks:
* 10.1.0.8, from 10.1.0.8, 0:00:04 ago, via INSIDE
Route metric is 3072, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
10.1.0.3, from 10.1.0.3, 0:00:04 ago, via INSIDE
Route metric is 3072, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
10.1.0.2, from 10.1.0.2, 0:00:04 ago, via INSIDE
Route metric is 3072, traffic share count is 1
Total delay is 20 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
