12-31-2008 11:12 AM - edited 03-06-2019 03:12 AM
Can anyone tell me why I got differenct routing path for same destination 10.10.169.136?
SWITCH1#show ip route 10.10.169.136
Routing entry for 10.10.169.0/24
Known via "static", distance 1, metric 0
Redistributing via eigrp 100
Advertised by eigrp 100
Routing Descriptor Blocks:
* 10.210.2.2
Route metric is 0, traffic share count is 1
So the next hop should be 10.210.2.2(static route), right?
But when I trace the same destionation, the first hop I got is not 10.210.2.2. Please refer the following -
SWITCH1#trace 10.10.169.136
Type escape sequence to abort.
Tracing the route to 10.10.169.136
1 10.10.52.2 0 msec
10.10.23.2 0 msec
10.10.25.2 0 msec
2 10.252.1.170 4 msec 0 msec 0 msec
3 10.252.1.174 4 msec 0 msec 0 msec
4 10.10.169.136 0 msec * 0 msec
Can anyone explian it to me? Thanks in advance.
12-31-2008 11:37 AM
The gateway can be a recursive route.
Let's see show ip route 10.210.2.2 from the same switch.
__
Edison.
12-31-2008 11:44 AM
I believe that the suggestion by Edison that it is a recursive route is likely to be the correct answer. But if it turns out not to be a recursive route then another possibility to consider is the possibility that Policy Based Routing has been configured and is sending the traceroute differently from what is indicated in the routing table.
If it is not an issue with a recursive route then could you check for the configuration of PBR?
HTH
Rick
12-31-2008 02:29 PM
I think there will be a lot of differences between those two because doesn't the traceroute return the actual interface addresses that it passes through instead of the OSPF addresses used to populate the routing table (RID)?
Richard
12-31-2008 03:17 PM
Yes, you are right. That is recursive route.
SWITCH1#show ip route 10.210.2.2
Routing entry for 10.210.2.2/32
Known via "eigrp 100", distance 90, metric 130816, type internal
Redistributing via eigrp 100
Last update from 10.10.52.2 on Vlan752, 1d00h ago
Routing Descriptor Blocks:
10.10.52.2, from 10.10.52.2, 1d00h ago, via Vlan752
Route metric is 130816, traffic share count is 1
Total delay is 5010 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
10.10.28.2, from 10.10.28.2, 1d00h ago, via Vlan728
Route metric is 130816, traffic share count is 1
Total delay is 5010 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
10.10.25.2, from 10.10.25.2, 1d00h ago, via Vlan725
Route metric is 130816, traffic share count is 1
Total delay is 5010 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
* 10.10.23.2, from 10.10.23.2, 1d00h ago, via Vlan723
Route metric is 130816, traffic share count is 1
Total delay is 5010 microseconds, minimum bandwidth is 1000000 Kbit
Reliability 255/255, minimum MTU 1500 bytes
Loading 1/255, Hops 1
Thanks for all your help!
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