Trace route - high response time

Unanswered Question
Aug 9th, 2007

Hi,

I am facing a problem where the user complains about slowness to access web applications. Network utilizations is normal but when I do a trace I get a high response time on the firt trace (1st hop) and when I try for the second time it's normal. Is it something normal?

Could it be related to the slowness?


1 10.109.208.200 1007 msec 0 msec 0 msec

2 10.109.249.26 0 msec 8 msec 0 msec

3 172.18.242.71 0 msec 8 msec 0 msec

4 172.18.14.183 0 msec 8 msec 0 msec

5 172.18.14.182 0 msec 0 msec 0 msec

6 10.109.248.146 8 msec 0 msec 0 msec

7 (10.109.64.133) 8 msec 0 msec 0 msec


Tracing the route to (10.109.64.133)


1 10.109.208.200 0 msec 8 msec 0 msec

2 10.109.249.26 0 msec 0 msec 0 msec

3 172.18.242.71 0 msec 8 msec 9 msec

4 172.18.14.183 0 msec 0 msec 9 msec

5 172.18.14.182 0 msec 0 msec 0 msec

6 10.109.248.146 0 msec 8 msec 0 msec

7 10.109.64.133 0 msec 8 msec 0 msec

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
5d-swan Thu, 08/09/2007 - 17:28

The first packet takes a long time as the device is waiting for an ARP response for the first hop (10.109.208.200). Once it has this ARP entry it will be cached for the next time.

Pavel Bykov Fri, 08/10/2007 - 04:09

I don't think that's it, because than the first request would time out (it would go unanswered - the packet would be lost).


But it might have to do something with arp cache. Do you have any specific manual ARP configuration? Also it might be problem with fast switching (form of cache). Are you using CEF (i.e. ip cef enabled globally?) on your default gateway router?

Actions

This Discussion