cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2576
Views
14
Helpful
17
Replies

Traceroute is bouncing between redundant hops that have an equal cost.

BruteForce
Level 1
Level 1

Below is my topology. I have a very basic OSPF setup and every layer 3 switch sees every network on 'sh ip route', and every advertising router is known in the ospf database. If I try to do a traceroute from DN1 to VLAN2000 hosted on DN2 or its loopback, here's the output I see.

DN1_Lab#traceroute 10.10.2.1
Type escape sequence to abort.
Tracing the route to 10.10.2.1
VRF info: (vrf in name/id, vrf out name/id)
1 5.5.5.9 2 msec
5.5.5.1 2 msec
5.5.5.9 2 msec
2 *
5.5.5.14 2 msec *

As shown above, the traceroute bounces between the two CNs and both routes have a cost of 2. Oddly, if I do a traceroute to 5.5.5.14 on DN2 from DN1, there's no bouncing between the CNs.

DN1_Lab#traceroute 5.5.5.14
Type escape sequence to abort.
Tracing the route to 5.5.5.14
VRF info: (vrf in name/id, vrf out name/id)
1 5.5.5.9 2 msec 2 msec 1 msec
2 5.5.5.14 1 msec 2 msec *

 

Something odd about this network is that every single interface is a layer 2 interface.. The "point to point" vlans are trunked across but they still participate in OSPF. I'm not sure if this is causing some spanning tree issues which would explain the bouncing between CNs.

USSFGuy_0-1678898121750.png

 

17 Replies 17

check solution 

 

Joseph W. Doherty
Hall of Fame
Hall of Fame

It's expected behavior.

Each traceroute packet is treated as its own flow.  I.e. it's a feature, as it reveals multiple paths at a particular hop.

My previous comment was not clear hope you this time clear I config the cost equal in all interface 
see how R1 receive the 20.0.0.0 and 130.0.0.0 from R4 

 

Screenshot (410).pngScreenshot (412).pngScreenshot (413).png