Thursday, May 23, 2019

Duplicate hops in traceroute

I have an odd issue on my hands. A user is complaining about slowness to an SAP server at certain times of the day [afternoon]. I asked them to do a traceroute and they replied. When things are fine the traceroute looks as one would expect. When things are slow, the traceroute shows a duplicate entry [with different ms responses] for every single hop including the first. So this explains why in the initial ticket they showed a ping result where the first ping goes through but after that they are all TTL expired.

Any thoughts?



No comments:

Post a Comment