ping times high in one direction and intermittent

[rongipp1961]

I have a customer with a WAN link 280 miles apart. Us (the Vendor) have an IP address on each side both on the same subnet on an isolated VLAN. Pings from site A to site B

are around 8ms consistently with no drops.

Pings from site B to site A vary from 8ms to 750ms. When I run a 64 byte 1 packet ping every 5 seconds I see the 10 latest ping reply times of

: 9ms, 9ms, 32ms, 14ms, 264ms, 13ms, 36ms, 19ms, 17ms, 254ms.

My natural reaction is to take a network trace. The issue is on the remote side (site B) there's only our equipment on the IP network. We don't have a tcptrace capability.

I would also like to ping between other IP addresses at site A or site B, but the customer doesn't have any other IP addresses on this VLAN. If I don't have any other way to

solve this I'm thinking I need to get the customer to assign an IP address to the VLAN on each side.

I'm looking for suggestions on what could be causing a longer ping time in one direction. I've doubled checked the speed/duplex settings on the interfaces and switch ports. We're not

getting any dropped packets or other errors on the switch ports. I've checked the subnet masks. It's possible we have a duplicate IP address or bad arp entry. But it happens when I ping

two different IP address on site A (from site B).

[Joseph W. Doherty]

Disclaimer

The   Author of this posting offers the information contained within this   posting without consideration and with the reader's understanding that   there's no implied or expressed suitability or fitness for any purpose.   Information provided is for informational purposes only and should not   be construed as rendering professional advice of any kind. Usage of  this  posting's information is solely at reader's own risk.

Liability Disclaimer

In   no event shall Author be liable for any damages whatsoever (including,   without limitation, damages for loss of use, data or profit) arising  out  of the use or inability to use the posting's information even if  Author  has been advised of the possibility of such damage.

Posting

Issue might be as simple as device you're pinging is occasionally slow to respond.  Cisco's SLA tests, with a SLA responder, try to adjust for host delay to provide a more accurate network latency reading.

[Alessio Andreoli]

Hi Ron,

To perform valid tests you can also create a loop back advertised as a host. Specifying the source address of your ping/trace

Ping 1.1.1.1 source 2.2.2.2 ! Loopback address

Would have the same effect than a pc on the LAN side. By the way,is it possible asymmetric routing or is it a physical point to point?

Alessio

Sent from Cisco Technical Support iPad App