> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of John Sechrest > Sent: Wednesday, March 15, 2006 2:08 PM > To: [EMAIL PROTECTED]; Eugene Unix and Gnu/Linux User Group > Subject: Re: [Eug-lug] Results of traceroute command > > > This looks like a local network problem or a transit out problem. > > To test the difference: > > 1) Use tcpdump look at the network traffic. is your lan busy? > (broad cast storms etc) > > 2) look at the interface states with > ifconfig eth0 > > Is your error rate/packets sent less than 4% > > > 3) Ping another machine inside your network , is it fast. > > 4) I assume that from the atg, that you can not log into your > router and test from there. > > If it is a lan problem, you should be able to fix it. > If it is a link to atg problem, then you need to get them involved.
/agree At the risk of being too obvious, my question would be - when it's slow, do you run around to different machines on the LAN to verify that they're all slow and it's not just your workstation? Jason LaPier Network Manager TACS / WRRC University of Oregon > > > > Matthew Jarvis <[EMAIL PROTECTED]> writes: > > % I hope it's okay to do this, but I thought I'd post > Bad/Good traceroute % listings for comments: > % > % (Hope the lines wrap okay) > % > % Bad: > % > % 1 juggernaut.bf-internal.com (192.168.1.2) 1.152 ms > 1.239 ms 0.990 ms > % 2 66-224-46-89.atgi.net (66.224.46.89) 1275.689 ms > 1731.876 ms > % 1877.640 ms > % 3 64-42-83-225.atgi.net (64.42.83.225) 1898.639 ms > 1759.864 ms > % 1854.649 ms > % 4 fe100.cr1.salmor01.atgi.net (206.58.252.65) 1929.620 > ms 1873.787 > % ms 1944.657 ms > % 5 core0-Se5-2.pdx.eschelon.com (64.65.188.205) > 1980.565 ms 1802.929 > % ms 1758.592 ms > % 6 core0-po0-2.sea.eschelon.com (64.65.133.17) 1764.674 > ms 1798.729 > % ms 1801.801 ms > % 7 POS3-0.GW10.SEA1.ALTER.NET (157.130.180.1) 1793.573 > ms 1797.862 > % ms 1805.614 ms > % 8 122.ATM2-0.XR2.SEA1.ALTER.NET (152.63.104.6) > 1786.667 ms 1797.856 > % ms 1791.393 ms > % 9 0.so-0-0-0.XL2.SEA1.ALTER.NET (152.63.106.233) 1795.880 ms > % 1799.926 ms 1939.654 ms > % 10 0.so-5-0-0.XL2.SAT1.ALTER.NET (152.63.99.38) 1849.614 > ms 1798.868 % ms 1787.622 ms % 11 > 210.ATM6-0.GW2.SAT1.ALTER.NET (152.63.101.229) 1789.634 ms > % 1777.851 ms 1790.680 ms % 12 > rackspace-gw.customer.alter.net (157.130.128.150) 1779.660 > ms % 1787.866 ms 1790.674 ms % 13 > vl130.core1.sat.rackspace.com (64.39.2.33) 1787.676 ms 1778.826 ms > % 1778.674 ms > % 14 vl905.aggr5.sat2.rackspace.com (64.39.2.82) 1791.600 > ms 1780.933 % ms 1787.633 ms % 15 bikefriday.com > (65.61.159.9) 1772.665 ms 1903.872 ms 1779.659 ms % % % Good: > % > % 1 juggernaut.bf-internal.com (192.168.1.2) 1.766 ms > 1.164 ms 1.016 ms > % 2 66-224-46-89.atgi.net (66.224.46.89) 3.860 ms 3.317 > ms 3.967 ms > % 3 64-42-83-225.atgi.net (64.42.83.225) 10.983 ms > 11.222 ms 10.904 ms > % 4 fe100.cr1.salmor01.atgi.net (206.58.252.65) 10.982 > ms 11.302 ms > % 10.938 ms > % 5 core0-Se5-2.pdx.eschelon.com (64.65.188.205) 13.301 > ms 15.773 ms > % 12.976 ms > % 6 core0-po0-2.sea.eschelon.com (64.65.133.17) 20.965 > ms 19.366 ms > % 18.935 ms > % 7 POS3-0.GW10.SEA1.ALTER.NET (157.130.180.1) 17.976 ms > 73.620 ms > % 17.561 ms > % 8 122.ATM2-0.XR2.SEA1.ALTER.NET (152.63.104.6) 18.895 > ms 19.140 ms > % 18.935 ms > % 9 0.so-0-0-0.XL2.SEA1.ALTER.NET (152.63.106.233) > 17.896 ms 18.295 > % ms 20.859 ms > % 10 0.so-5-0-0.XL2.SAT1.ALTER.NET (152.63.99.38) 76.097 > ms 77.125 ms % 77.955 ms % 11 > 210.ATM6-0.GW2.SAT1.ALTER.NET (152.63.101.229) 75.932 ms 76.272 ms > % 75.859 ms > % 12 rackspace-gw.customer.alter.net (157.130.128.150) > 82.887 ms 86.312 % ms 83.885 ms % 13 > vl130.core1.sat.rackspace.com (64.39.2.33) 81.997 ms 82.247 > ms % 82.921 ms % 14 vl905.aggr5.sat2.rackspace.com > (64.39.2.82) 85.950 ms 98.608 ms % 83.967 ms % 15 > bikefriday.com (65.61.159.9) 81.882 ms 82.292 ms 87.921 ms > % % % Any thoughts on why one would be SO MUCH different > than the other? > % > % The return path displayed by traceroute from > www.bikefriday.com back to % us always seems to be > relatively quick... > % > % I'm wondering if from time to time we are getting our > packet's fubar'd % or something from within our network and > just spewing crap for a % while... then it clears up.... > % > % -- > % Matthew S. Jarvis > % IT Manager > % Bike Friday - "Performance that Packs." > % www.bikefriday.com > % 541/687-0487 x140 > % [EMAIL PROTECTED] > % _______________________________________________ > % EUGLUG mailing list > % [email protected] > % http://www.euglug.org/mailman/listinfo/euglug > > ----- > John Sechrest . Helping people use > . computers and the Internet > . more effectively > . > . Internet: [EMAIL PROTECTED] > . > . > http://www.peak.org/~sechrest > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug > _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
