Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Odd Traceroute Response !

SERVER: Traceroute to 208.0.Y.X (208.0.Y.X):

1 198.162.K.L (198.162.K.L) 2 ms 1 ms 1 ms

2 198.162.S.T (198.162.S.T) 3 ms 4 ms 5 ms

3 192.168.170.113 (192.168.170.113) 5 ms 3 ms 3 ms

4 192.168.170.9 (192.168.170.9) 147 ms 149 ms *

5 192.168.170.9 (192.168.170.9) 149 ms 162 ms *

6 192.168.170.9 (192.168.170.9) 152 ms 153 ms *

7 192.168.170.9 (192.168.170.9) 146 ms 151 ms *

8 192.168.170.9 (192.168.170.9) 150 ms 150 ms *

9 192.168.170.9 (192.168.170.9) 149 ms 151 ms *

10 192.168.170.9 (192.168.170.9) 150 ms 152 ms *

11 192.168.170.9 (192.168.170.9) 151 ms 153 ms *

12 192.168.170.9 (192.168.170.9) 147 ms 145 ms *

13 192.168.170.9 (192.168.170.9) 164 ms 155 ms *

14 192.168.170.9 (192.168.170.9) 164 ms 186 ms *

15 192.168.170.9 (192.168.170.9) 154 ms 148 ms *

16 192.168.170.9 (192.168.170.9) 146 ms 153 ms *

17 192.168.170.9 (192.168.170.9) 147 ms 155 ms *

18 192.168.170.9 (192.168.170.9) 150 ms 150 ms *

19 192.168.170.9 (192.168.170.9) 155 ms 146 ms *

20 * * 198.162.X.X (198.162.X.X) 3 ms

21 198.162.X.X (198.162.X.X) 3 ms 3 ms *

22 198.162.X.X (198.162.X.X) 3 ms 3 ms *

23 198.162.X.X (198.162.X.X) 5 ms 3 ms *

24 198.162.X.X (198.162.X.X) 8 ms 3 ms *

25 198.162.X.X (198.162.X.X) 3 ms 3 ms *

26 198.162.X.X (198.162.X.X) 3 ms 3 ms *

27 198.162.X.X (198.162.X.X) 3 ms 3 ms *

28 198.162.X.X (198.162.X.X) 3 ms 3 ms *

29 198.162.X.X (198.162.X.X) 4 ms 3 ms *

30 198.162.X.X (198.162.X.X) 3 ms 6 ms *

hop limit reached:

Can someone help decipher this odd behaviour of the traceroute command as shown in the output above. For some reason when it hits the 192.168.170 network, i get multiple hop counts on the same router.

Thanks in advance .

3 REPLIES
Green

Re: Odd Traceroute Response !

What does a PING do to the same address? If you get "TTL Timeout", then you have a router loop.

Good Luck

Scott

New Member

Re: Odd Traceroute Response !

Thanks for the response Scott, A ping actually goes through.

regards

Danyell

Re: Odd Traceroute Response !

Not sure this is what is happening in this case. But I've seen this behaviour when 1 of the hops (or the repeating one) is a firewall.

As for security reasons it wont sent the response from the inside routers back to you, it replied as if it was the firewall itself.

Usually you can check TTL values to make sure they are different (meaning your packets travelled through another hop).

Hope this help a bit,

if it does, please rate this post.

Vlad

125
Views
0
Helpful
3
Replies
CreatePlease to create content