irregualr ping response time from switch to PC

[chuikingman]

I have a 6400 switch . I use direct cable connect to a win 7 PC(10.1.9.97) .
The switch one use one port with vlan 1 and there is no other port connect.
I ping from switch to that PC .
I find the ping response time appear steady in a period of time and then suddenly it will jump with bigger delay.
I expect the ping time should be steady all the time as there is no any other traffic from switch to PC .
below is the ping time I observe.You can see usually ping time is within 5 ms but sometime it jump more than 10 ms .
Why and any suggestion ???

Code: Select all

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.01.16 09:19:41 =~=~=~=~=~=~=~=~=~=~=~=
64 bytes from 10.1.9.97: icmp_seq=98. time=3. ms
----10.1.9.97 PING Statistics----
99 packets transmitted, 99 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 3/12/233


-> ping 10.1.9.97 count 99
PING 10.1.9.97: 56 data bytes
64 bytes from 10.1.9.97: icmp_seq=0. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=1. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=2. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=3. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=4. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=5. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=6. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=7. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=8. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=9. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=10. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=11. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=12. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=13. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=14. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=15. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=16. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=17. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=18. time=33. ms
64 bytes from 10.1.9.97: icmp_seq=19. time=3. ms
64 bytes from 10.1.9.97: icmp_seq=20. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=21. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=22. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=23. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=24. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=25. time=200. ms
64 bytes from 10.1.9.97: icmp_seq=26. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=27. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=28. time=33. ms
64 bytes from 10.1.9.97: icmp_seq=29. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=30. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=31. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=32. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=33. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=34. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=35. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=36. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=37. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=38. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=39. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=40. time=55. ms
64 bytes from 10.1.9.97: icmp_seq=41. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=42. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=43. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=44. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=45. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=46. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=47. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=48. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=49. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=50. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=51. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=52. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=53. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=54. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=55. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=56. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=57. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=58. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=59. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=60. time=4. ms
64 bytes from 10.1.9.97: icmp_seq=61. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=62. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=63. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=64. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=65. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=66. time=6. ms
64 bytes from 10.1.9.97: icmp_seq=67. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=68. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=69. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=70. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=71. time=6. ms
64 bytes from 10.1.9.97: icmp_seq=72. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=73. time=126. ms
64 bytes from 10.1.9.97: icmp_seq=74. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=75. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=76. time=6. ms
64 bytes from 10.1.9.97: icmp_seq=77. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=78. time=7. ms
64 bytes from 10.1.9.97: icmp_seq=79. time=56. ms
64 bytes from 10.1.9.97: icmp_seq=80. time=8. ms
64 bytes from 10.1.9.97: icmp_seq=81. time=13. ms
64 bytes from 10.1.9.97: icmp_seq=82. time=17. ms
64 bytes from 10.1.9.97: icmp_seq=83. time=18. ms
64 bytes from 10.1.9.97: icmp_seq=84. time=21. ms
64 bytes from 10.1.9.97: icmp_seq=85. time=21. ms
64 bytes from 10.1.9.97: icmp_seq=86. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=87. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=88. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=89. time=7. ms
64 bytes from 10.1.9.97: icmp_seq=90. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=91. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=92. time=62. ms
64 bytes from 10.1.9.97: icmp_seq=93. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=94. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=95. time=101. ms
64 bytes from 10.1.9.97: icmp_seq=96. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=97. time=5. ms
64 bytes from 10.1.9.97: icmp_seq=98. time=5. ms
----10.1.9.97 PING Statistics----
99 packets transmitted, 99 packets received, 0% packet loss
round-trip (ms)  min/avg/max = 3/11/200


-> 

[devnull]

In general: the switch CPU ist very limited and ping (sending or replying) is done in software.

Hence it is not unusual to see "strange" response times when sending to/from a switch.
try to ping another device on the same switch, like an other PC and see whether you have this delays as well. In this case it is handled in hardware by the switch and there should be no delays.

[chuikingman]

I try another IP/device .I ping from switch to them .
The same result and I observer irregular dely in ping response time
Please advise and suggest

[devnull]

Not from switch..
from PC to PC through switch

[chuikingman]

the same

[Anth0]

I saw myself the same thing with my 6400 or 6450... The response times are varying moment. I was told that the PING is not a priority (src alcatel)