Date: Fri, 27 Dec 2002 14:31:23 -0500 From: Gerard Samuel <gsam@trini0.org> To: stacey@vickiandstacey.com Cc: FreeBSD Questions <questions@FreeBSD.ORG> Subject: Re: Network timeouts??? Message-ID: <3E0CAA8B.4050005@trini0.org> References: <3E0C72A9.9000302@trini0.org> <1041004206.68500.116.camel@localhost> <3E0C91F0.3000102@trini0.org> <1041012776.68500.128.camel@localhost> <3E0C9D2E.3000704@trini0.org> <1041015112.68500.144.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Stacey Roberts wrote:
>So both nic believe themselves to be running okay (as shown in their
>respective Oerr counts being 0 each - translation: the nics are fine as
>they are able to send all packets okay. Its only in receiving data that
>they're returning errors on the link.
>
>I'd suggest that you have a look at the switch itself as well. I know
>that this is a desktop switch (read non-enterprise) that is different to
>most others in this class as its got *no* cooling fans (hence that bump
>on the top). As such, depending on how you hammer this device, there is
>the chance of it over-heating. This, of course, is also dependant on
>where its actually located as well.
>
>It does have some link / speed / duplex indicator LED's on the front
>that can be useful. As well as checking the cabling into the switch, see
>if swapping the cables to available ports (except the uplink partner!)
>and see if this makes any difference.
>
>I remember one of the guys on my team at work got the Linksys peer to
>this switch and rubbished it within 3 weeks due to the switch locking up
>under sustained (4+ hours) heavy load transfers at his section lan
>point.
>
>Let us know how you get on, and what new information you might have for
>us.
>
>Regards,
>
>Stacey
>
>
I've had this switch running pretty much non-stop since last Feburary.
Its been great for my needs thus far. One of the boxes is running
Samba/CVS/www, and it sees quite a bit of traffic. Whether its on its
last leg, that remains to be seen.
Better get on the phone with tech support before they close for the weekend.
But I still think its cables. Because Im writing this email from a
laptop thats also connected to the switch, and here are its details ->
{gsam@laptop}-{~} > ifconfig ed1 [27 Dec
2:22pm]
ed1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255
ether 00:50:ba:7a:f0:a3
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
{gsam@laptop}-{~} > netstat -in [27 Dec
2:15pm]
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
Coll
lo0 16384 <Link#1> 0 0 0
0 0
lo0 16384 127 127.0.0.1 0 - 0
- -
ed1 1500 <Link#2> 00:50:ba:7a:f0:a3 44116 6 35805
0 0
ed1 1500 192.168.0 192.168.0.5 44049 - 35773
- -
No errors there. Maybe, Ill just make up some new cables, make sure, no
"wall warts" are near them, and see how it goes over the weekend.
If its still problematic, then Ill get the switch replaced.
Thanks for the help you've provided, and Ill let you know how it goes...
--
Gerard Samuel
http://www.trini0.org:81/
http://dev.trini0.org:81/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E0CAA8B.4050005>