11-21-2016 04:59 AM - edited 03-08-2019 08:14 AM
Dear All,
I have one customer there are experiencing high latency from their LAN. When I tried extended ping from the router the latency was 124ms to 144ms. When the customer is pinging from the LAN the latency is 260ms. We the customer disconnected the LAN and connected his laptop directly to the router and checked the response is same about 260ms.
Any suggestion on the cause.
The ping responses are as below,
Router#ping
Protocol [ip]:
Target IP address: 172.17.10.1
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.20.235.240
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 172.17.10.1, timeout is 2 seconds:
Packet sent with a source address of 172.20.235.240
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 124/125/136 ms
Success rate is 100 percent (5/5), round-trip min/avg/max = 128/130/132 ms
Router#ping
Protocol [ip]:
Target IP address: 172.17.240.130
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.20.235.240
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 172.17.240.130, timeout is 2 seconds:
Packet sent with a source address of 172.20.235.240
!!!!!!!!!!!!!!!!!!!!!.!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!
Success rate is 97 percent (97/100), round-trip min/avg/max = 136/141/152 ms
Router#ping
Protocol [ip]:
Target IP address: 172.17.244.72
Repeat count [5]: 100
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface: 172.20.235.240
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 100, 100-byte ICMP Echos to 172.17.244.72, timeout is 2 seconds:
Packet sent with a source address of 172.20.235.240
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (100/100), round-trip min/avg/max = 144/148/164 ms
C:\Users\DKSPL003>ping 172.17.10.1
Pinging 172.17.10.1 with 32 bytes of data:
Reply from 172.17.10.1: bytes=32 time=260ms TTL=248
Reply from 172.17.10.1: bytes=32 time=260ms TTL=248
Reply from 172.17.10.1: bytes=32 time=259ms TTL=248
Reply from 172.17.10.1: bytes=32 time=259ms TTL=248
Ping statistics for 172.17.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 259ms, Maximum = 260ms, Average = 259ms
C:\Users\DKSPL003>tracert 172.17.10.1
Tracing route to ns.sys.mmc.co.jp [172.17.10.1]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 172.20.235.240
2 260 ms 260 ms 259 ms 172.17.28.25
3 260 ms 260 ms 260 ms 172.17.1.250
4 260 ms 260 ms 260 ms 172.17.27.241
5 259 ms 259 ms 259 ms ns.sys.mmc.co.jp [172.17.10.1]
6 260 ms 259 ms 259 ms ns.sys.mmc.co.jp [172.17.10.1]
7 260 ms 260 ms 261 ms 172.17.27.162
8 261 ms 260 ms 261 ms ns.sys.mmc.co.jp [172.17.10.1]
Trace complete.
C:\Users\DKSPL003>tracert 172.17.244.72
Tracing route to 172.17.244.72 over a maximum of 30 hops
1 1 ms 1 ms <1 ms 172.20.235.240
2 261 ms 260 ms 260 ms 172.17.28.25
3 260 ms 259 ms 268 ms 172.17.2.240
4 1468 ms 264 ms 264 ms 172.16.1.6
5 * 272 ms 270 ms 172.16.2.2
6 275 ms 275 ms 274 ms 172.16.2.1
7 275 ms 275 ms 275 ms 172.17.240.241
8 275 ms 275 ms 275 ms 172.17.243.241
9 285 ms 283 ms 282 ms 192.168.244.1
10 283 ms 283 ms 283 ms 172.17.244.72
Trace complete.
C:\Users\DKSPL003>ping 172.17.244.72
Pinging 172.17.244.72 with 32 bytes of data:
Reply from 172.17.244.72: bytes=32 time=282ms TTL=119
Reply from 172.17.244.72: bytes=32 time=283ms TTL=119
Reply from 172.17.244.72: bytes=32 time=285ms TTL=119
Reply from 172.17.244.72: bytes=32 time=294ms TTL=119
Ping statistics for 172.17.244.72:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 282ms, Maximum = 294ms, Average = 286ms
C:\Users\DKSPL003>
Regards,
Eash
11-21-2016 06:05 AM
Duplicate, please see: https://supportforums.cisco.com/discussion/13168086/high-latency-lan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide