02-24-2011 01:03 AM - edited 03-04-2019 11:32 AM
Hi,
I have an EIGRP routed network which is selecting best path routes, and routing information is being sent and received as expected. A few entries are in the routing table do not state the next hop, or the route's feasable distance. They are however reachable and I can pass traffic to and from the network:
D 10.18.1.46/32 [90/1408256] via 10.18.1.46, 01:44:39, Tunnel0
D 10.18.1.47/32
D 10.18.1.45/32 [90/1408256] via 10.18.1.45, 01:44:39, Tunnel0
Does any one know what would cause this?
Thanks
Jake
Solved! Go to Solution.
02-24-2011 02:41 AM
Hello Jake,
The information you provided suggests that the route towards 10.18.1.47/32 goes through the next hop 10.254.0.100, and it all appears to be a perfectly correct routing table entry. Are you suggesting that the pure show ip route output does not contain information about the next-hop IP and the egress interface? Is it possible that the output is just wrapped in a way that parts of the output are placed onto another line?
Have a look at the show ip route once more please - without any filters ( | include , | exclude etc.), and try to look a few lines before and after the confusing entry about 10.18.1.47/32 - especially the line immediately below the 10.18.1.47/32 entry should be actually a continuation of the previous line.
Best regards,
Peter
02-24-2011 01:52 AM
Hi Jake,
Whoa, interesting output Would you mind posting the output of the command show ip route 10.18.1.47 255.255.255.255 and perhaps also the entire show ip route output?
Best regards,
Peter
02-24-2011 02:33 AM
Routing entry for 10.18.1.47/32
Known via "eigrp 100", distance 90, metric 26245120, type internal
Redistributing via eigrp 100
Last update from 10.254.0.100 on FastEthernet0/1, 00:20:54 ago
Routing Descriptor Blocks:
* 10.254.0.100, from 10.254.0.100, 00:20:54 ago, via FastEthernet0/1
Route metric is 26245120, traffic share count is 1
Total delay is 525200 microseconds, minimum bandwidth is 200 Kbit
Reliability 255/255, minimum MTU 1472 bytes
Loading 11/255, Hops 4
02-24-2011 02:41 AM
Hello Jake,
The information you provided suggests that the route towards 10.18.1.47/32 goes through the next hop 10.254.0.100, and it all appears to be a perfectly correct routing table entry. Are you suggesting that the pure show ip route output does not contain information about the next-hop IP and the egress interface? Is it possible that the output is just wrapped in a way that parts of the output are placed onto another line?
Have a look at the show ip route once more please - without any filters ( | include , | exclude etc.), and try to look a few lines before and after the confusing entry about 10.18.1.47/32 - especially the line immediately below the 10.18.1.47/32 entry should be actually a continuation of the previous line.
Best regards,
Peter
02-24-2011 07:23 AM
Hi Peter,
sh ip route | i 10.18.1.
Was causing the strange output.
Thanks for your time :-)
Jake
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide