Date: Sat, 06 Mar 2004 21:11:09 -0500 From: Mike Tancsa <mike@sentex.net> To: "Marc G. Fournier" <scrappy@hub.org> Cc: freebsd-stable@freebsd.org Subject: Re: Odd network issue ... *very* slow scp between two servers Message-ID: <6.0.3.0.0.20040306210359.08fc35a8@209.112.4.2> In-Reply-To: <20040306211328.H13247@ganymede.hub.org> References: <20040306130937.N71806@ganymede.hub.org> <6.0.3.0.0.20040306180314.08adede0@209.112.4.2> <20040306210515.M13247@ganymede.hub.org> <20040306211328.H13247@ganymede.hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 08:20 PM 06/03/2004, Marc G. Fournier wrote:
>'k, I'm blind to start with ... I take it that this is the significant
>part of the output:
>
>Name Mtu Network Address Ipkts Ierrs Opkts
>Oerrs Coll
>em0 1500 <Link#1> 00:07:e9:05:1b:2e 760865424 58003349
>775965555 0 0
Yes, extremely significant.
>where the fxp devices don't show any Ierrs? That works out to be ~7% ...
It has nothing to do with the fxp on the other machine. Its input errors
divided by total packets coming in
# bc
bc 1.06
Copyright 1991-1994, 1997, 1998, 2000 Free Software Foundation, Inc.
This is free software with ABSOLUTELY NO WARRANTY.
For details type `warranty'.
scale=3
58003349/760865424
.076
>Dropping it to 10baseT/UTP appears to improve things by 10x:
>
>1038785 bytes received in 6.86 seconds (147.89 KB/s)
>
>And drop'ng it to 100baseTX, half-duplex makes an even larger difference:
>
>1038785 bytes received in 0.49 seconds (2.01 MB/s)
>1038785 bytes received in 0.14 seconds (6.89 MB/s)
>
>The fxp devices are all running 100baseTX, full-duplex, and doing 10MB/s
>between each other ...
I would in the following order
a) check the settings on the switch. AutoNeg *only* works when both sides
are set to auto-neg. If both sides are not auto, make sure both sides are
the same for speed and duplex settings.
b) try changing the cable. Go with cat6 for the em even if you use
100baseTX. Dont use anything shorter than 3f/1m
c) try the card in a different slot on your MB. We have found a few boards
where the em is picky about what slot its in and what it potentially shares
as an interrupt.
d) try a different card
---Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.3.0.0.20040306210359.08fc35a8>