Trace route query

[Donny_Dog]

Has anyone else seen this behaviour before with Cisco devices?
I'm looking after a network that doesn't seem overly stable to me.

I'm trying to discover the path to a device on: 192.168.44.1.
sh ip route <etc>

D 192.168.44.0/24 [90/3328] via 192.168.24.249, 6w3d, Vlan888
[90/3328] via 192.168.9.250, 6w3d, Vlan9
[90/3328] via 192.168.7.249, 6w3d, Vlan6
[90/3328] via 192.168.2.249, 6w3d, Vlan2

The updates seem a bit lenghty to me, but they do run Eigrp and the routing tables for other subnets are similar update times.

Trace routing to 192.168.44.1 brings this:

Tracing the route to 192.168.44.1
1 192.168.2.249 0 msec
192.168.7.249 0 msec
192.168.9.250 8 msec
2 192.168.1.251 0 msec * 0 msec

The first hop is the device im on.
The two in the middle are interfaces for Vlan6 and Vlan9 - why are they listed?
The second hop of 192.168.1.251 is actually another interface on the 192.168.44.1 device and so the trace route is successful after two hops.

I've never seen this behaviour in a traceroute before.

 

[Donny_Dog]

Figured it out.

As there are multiple paths, traceroute sends 3 probes by default.

Doh.

 

[Cr33do]

Correct

you can change the probe count if you run an extended trace route.