[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: packet loss after Lenny Squeeze upgrade



On 3/21/2012 11:00 AM, Bonno Bloksma wrote:

> All I know right now is when I send pings to the server from another server I get 1-5% packet loss. :-(

It's a requirement on a *technical* mailing list to provide technical
data related to a problem, not merely subjective statements, which is
all you have provided thus far.  At *minimum* you should provide some
*evidence* of the problem.  Such evidence may consist of, but not only,
ping and traceroute output in both directions, to/from the "problem
server", from multiple hosts on different switch/router segments within
your network and outside of it.  We need to see your output, not just
comments, such as:

$ ping 217.114.99.194
PING 217.114.99.194 (217.114.99.194) 56(84) bytes of data.
64 bytes from 217.114.99.194: icmp_req=1 ttl=47 time=163 ms
64 bytes from 217.114.99.194: icmp_req=2 ttl=47 time=172 ms
64 bytes from 217.114.99.194: icmp_req=3 ttl=47 time=185 ms
64 bytes from 217.114.99.194: icmp_req=4 ttl=47 time=177 ms
64 bytes from 217.114.99.194: icmp_req=5 ttl=47 time=156 ms
64 bytes from 217.114.99.194: icmp_req=6 ttl=47 time=165 ms
64 bytes from 217.114.99.194: icmp_req=7 ttl=47 time=146 ms
^C
--- 217.114.99.194 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6023ms
rtt min/avg/max/mdev = 146.948/166.733/185.263/12.009 ms


$ traceroute -q 1 217.114.99.194
traceroute to 217.114.99.194 (217.114.99.194), 30 hops max, 60 byte packets
 1  smc.hardwarefreak.com (192.168.100.1)  0.883 ms
 2  mo-65-41-216-193.sta.embarqhsd.net (65.41.216.193)  65.722 ms
 3  mo-69-68-209-229.sta.embarqhsd.net (69.68.209.229)  66.578 ms
 4  208-110-240-186.centurylink.net (208.110.240.186)  68.559 ms
 5  bb-kscbmonr-jx9-01-ae0.core.centurytel.net (206.51.69.5)  75.374 ms
 6  bb-dllstx37-[...].core.centurytel.net (206.51.69.25)  84.665 ms
 7  dal-edge-18.inet.qwest.net (72.165.208.157)  85.815 ms
 8  dap-brdr-03.inet.qwest.net (67.14.2.85)  85.794 ms
 9  xe-8-1-0.edge2.dallas3.level3.net (4.68.63.49)  90.268 ms
10  vlan90.csw4.Dallas1.Level3.net (4.69.145.254)  92.403 ms
11  ae-83-83.ebr3.Dallas1.Level3.net (4.69.151.158)  94.672 ms
12  ae-3-3.ebr2.NewYork1.Level3.net (4.69.137.122)  124.038 ms
13  ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242)  128.148 ms
14  ae-6-6.ebr1.Washington12.Level3.net (4.69.148.106)  126.386 ms
15  ae-1-100.ebr2.Washington12.Level3.net (4.69.143.214)  128.035 ms
16  4.69.148.49 (4.69.148.49)  132.929 ms
17  ae-58-223.csw2.Amsterdam1.Level3.net (4.69.153.210)  220.366 ms
18  ae-2-52.edge4.Amsterdam1.Level3.net (4.69.139.170)  185.791 ms
19  gi1-7.bg1.am1.eu.equinix.net (212.72.40.62)  188.672 ms
20  ae-2-52.edge4.Amsterdam1.Level3.net (4.69.139.170)  188.527 ms
21  ve85.l3c-en1-1.as16243.net (87.249.109.1)  200.309 ms
22  ve1.far4.as16243.net (77.222.66.126)  199.577 ms
23  ve85.l3c-en1-1.as16243.net (87.249.109.1)  192.612 ms
24  ve1.far4.as16243.net (77.222.66.126)  192.505 ms
25  *
26  *
27  *
28  *
29  *
30  *

-- 
Stan


Reply to: