latency issue

[wajid dabir]

my one of client site is phasing an internal network latency issue,what should i do to troubleshoot.

my access switches is connected to core switch via a trunk link,it is tier 2 network.

Ping response of interface vlan ip of core switch from access switch.

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=3ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=7ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=8ms TTL=255

Reply from 10.60.3.1: bytes=32 time=28ms TTL=255

Reply from 10.60.3.1: bytes=32 time=4ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=4ms TTL=255

Reply from 10.60.3.1: bytes=32 time=2ms TTL=255

Reply from 10.60.3.1: bytes=32 time=12ms TTL=255

Reply from 10.60.3.1: bytes=32 time=9ms TTL=255

Reply from 10.60.3.1: bytes=32 time=13ms TTL=255

Reply from 10.60.3.1: bytes=32 time=8ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=10ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

Reply from 10.60.3.1: bytes=32 time=1ms TTL=255

[Reza Sharifi]

If you are pinging an SVI and the switch is busy doing something else, the switch gives low priority to ping packets.

You may get a more accurate response, if you ping from one host to another.

HTH

[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

First determine if there really is a latency problem.  "Ordinary" ping, alone, is not designed for high accuracy latency measurements, it was designed to determine if a host is on-line and if there's two way reachability.