Return time over tunnel interface

[olorunloba]

If I ping the tunnel destination from a router, I get a return time of about 700ms, but pinging the the tunnel end itself returns about 1200ms. I am wondering if the tunneling encryption is adding more bandwidth, causing the higher delay. I have not configured any special thing apart from the tunnel ip address, the source and the destination addresses.

[deilert]

This is normal behavior for a ping, If you ping your own interface on any circuit the ping will travel to the remote side of the ciruit then comes back . If you ping the remote side the ping time will be 1/2 the response as if you your own interface , try it on any wide area link .

[olorunloba]

I am pinging the remote interface in both situation. The difference is that when I ping the remote tunnel interface, the return time is usually higher than when I ping the remote serial interface (which is the tunnel destination). I am beginning to wonder if there is any kind of checksumming necessary, or something additional I need to configure.

[olorunloba]

I am right now wondering whether the MTU size can affect it. The tunnel passes over different routers, which have ethernet, fastethernet and serial interfaces. The MTU on the Tunnel is 1476 (default) and the MTU on the ethernet along the link is 1500 while the serial is also 1500. Could this bring a perofrmance issue.

[deilert]

Ok

Don't forget these tunnelas are just virtual pipes , the best way to TS is to do a tracerouter to the tunnel dest sourcing it from the tunnel source , you may be traversing more hops than you realize, look for overutilized WAN links and speed /duplex mismatches on lan links

[olorunloba]

The route goes over 5 hops. I have heavy utilisation also on the links. What can I do to alleviate the problem.

[deilert]

You can massage the routing between the tunnel source and dest to try to reduce the hops or you could use differnt source & dest tunnel ip's that travers less hops , or you can reduce the traffic on the Wan.