From: Theo van den Berg (theo.vandenberg@gmail.com)
Date: Tue Oct 03 2006 - 10:03:53 ART
Hi There
Have you guys seen anything like this before ?
Any idea what would cause the negative ping values and also the large value
in negative reponse time of roughly 30300ms ?
I have included a trace below as well.
Hope you could assist or explain ?
Thanks
Theo
s4006_mtedg_02> (enable) ping -s 10.217.200.254 100
PING 10.217.200.254: 100 data bytes
108 bytes from 10.217.200.254: icmp_seq=0. time=28 ms
108 bytes from 10.217.200.254: icmp_seq=1. time=27 ms
108 bytes from 10.217.200.254: icmp_seq=2. time=66 ms
108 bytes from 10.217.200.254: icmp_seq=3. time=25 ms
108 bytes from 10.217.200.254: icmp_seq=4. time=26 ms
108 bytes from 10.217.200.254: icmp_seq=5. time=48 ms
108 bytes from 10.217.200.254: icmp_seq=6. time=25 ms
108 bytes from 10.217.200.254: icmp_seq=7. time=35 ms
108 bytes from 10.217.200.254: icmp_seq=8. time=23 ms
108 bytes from 10.217.200.254: icmp_seq=9. time=-30357 ms
108 bytes from 10.217.200.254: icmp_seq=10. time=24 ms
108 bytes from 10.217.200.254: icmp_seq=11. time=-30371 ms
108 bytes from 10.217.200.254: icmp_seq=12. time=24 ms
108 bytes from 10.217.200.254: icmp_seq=13. time=34 ms
108 bytes from 10.217.200.254: icmp_seq=14. time=27 ms
108 bytes from 10.217.200.254: icmp_seq=15. time=29 ms
108 bytes from 10.217.200.254: icmp_seq=16. time=-30370 ms
108 bytes from 10.217.200.254: icmp_seq=17. time=27 ms
108 bytes from 10.217.200.254: icmp_seq=18. time=27 ms
108 bytes from 10.217.200.254: icmp_seq=19. time=-30387 ms
108 bytes from 10.217.200.254: icmp_seq=20. time=-30375 ms
108 bytes from 10.217.200.254: icmp_seq=21. time=-30388 ms
108 bytes from 10.217.200.254: icmp_seq=22. time=31 ms
108 bytes from 10.217.200.254: icmp_seq=23. time=-30364 ms
108 bytes from 10.217.200.254: icmp_seq=24. time=25 ms
108 bytes from 10.217.200.254: icmp_seq=25. time=25 ms
108 bytes from 10.217.200.254: icmp_seq=26. time=-30370 ms
108 bytes from 10.217.200.254: icmp_seq=27. time=30 ms
108 bytes from 10.217.200.254: icmp_seq=28. time=-30373 ms
108 bytes from 10.217.200.254: icmp_seq=29. time=-30377 ms
108 bytes from 10.217.200.254: icmp_seq=30. time=-30367 ms
108 bytes from 10.217.200.254: icmp_seq=31. time=24 ms
108 bytes from 10.217.200.254: icmp_seq=32. time=27 ms
108 bytes from 10.217.200.254: icmp_seq=33. time=32 ms
108 bytes from 10.217.200.254: icmp_seq=34. time=32 ms
108 bytes from 10.217.200.254: icmp_seq=35. time=-30358 ms
108 bytes from 10.217.200.254: icmp_seq=36. time=29 ms
108 bytes from 10.217.200.254: icmp_seq=37. time=-30385 ms
108 bytes from 10.217.200.254: icmp_seq=38. time=-30369 ms
108 bytes from 10.217.200.254: icmp_seq=39. time=-30373 ms
108 bytes from 10.217.200.254: icmp_seq=40. time=28 ms
108 bytes from 10.217.200.254: icmp_seq=41. time=-30379 ms
108 bytes from 10.217.200.254: icmp_seq=42. time=23 ms
108 bytes from 10.217.200.254: icmp_seq=43. time=-30388 ms
108 bytes from 10.217.200.254: icmp_seq=44. time=31 ms
108 bytes from 10.217.200.254: icmp_seq=45. time=-30380 ms
108 bytes from 10.217.200.254: icmp_seq=46. time=28 ms
s4006_mtedg_02> (enable) trace 10.217.200.254
traceroute to 10.217.200.254 (10.217.200.254), 30 hops max, 40 byte packets
1 10.96.224.252 (10.96.224.252) 12 ms 7 ms 7 ms
2 10.96.224.2 (10.96.224.2) 7 ms 8 ms 6 ms
3 10.190.64.66 (10.190.64.66) 14 ms 10 ms 16 ms
4 10.217.200.253 (10.217.200.253) 23 ms 39 ms 21 ms
5 10.217.200.254 (10.217.200.254) 21 ms * 37 ms
This archive was generated by hypermail 2.1.4 : Wed Nov 01 2006 - 07:29:04 ART