From owner-freebsd-questions Sat Dec 28 10:51:30 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7546337B401 for ; Sat, 28 Dec 2002 10:51:27 -0800 (PST) Received: from hivemind.trini0.org (bgp626680bgs.brick201.nj.comcast.net [68.39.132.244]) by mx1.FreeBSD.org (Postfix) with SMTP id 39DC643ED1 for ; Sat, 28 Dec 2002 10:51:26 -0800 (PST) (envelope-from gsam@trini0.org) Received: (qmail 473 invoked by uid 0); 28 Dec 2002 18:51:25 -0000 Received: from unknown (HELO trini0.org) (192.168.0.5) by 192.168.0.2 with SMTP; 28 Dec 2002 18:51:25 -0000 Message-ID: <3E0DF2AE.7060702@trini0.org> Date: Sat, 28 Dec 2002 13:51:26 -0500 From: Gerard Samuel User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.1) Gecko/20021213 X-Accept-Language: en, en-us, nl, th MIME-Version: 1.0 To: stacey@vickiandstacey.com Cc: FreeBSD Questions Subject: Re: Network timeouts??? 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> <3E0CAA8B.4050005@trini0.org> <1041017922.68500.149.camel@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well after almost 24 hours later, here is what happened... Shortly after your last post, the situation got worse. I tried banging the switch with a screwdriver, and that was it. No more switch. The link light kept flashing, so I knew it was pretty much dead. Just so happens, that its a Friday evening, and banks were closed, credit card is maxed out from Christmas, so I had to endure a dead network till today. Got me a brand new switch from Circuit City, and all seems to be well in the universe. No more errors... Thanks for all the help... Stacey Roberts wrote: >On Fri, 2002-12-27 at 19:31, Gerard Samuel wrote: > > >>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 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 ) >> status: active >> >>{gsam@laptop}-{~} > netstat -in [27 Dec >>2:15pm] >>Name Mtu Network Address Ipkts Ierrs Opkts Oerrs >>Coll >>lo0 16384 0 0 0 >>0 0 >>lo0 16384 127 127.0.0.1 0 - 0 >>- - >>ed1 1500 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. >> >> > >Actually, there *are* 6 occurrences under Ierrs here :-( > >Seeing that you're actually on that switch (using a different port to >the other FBSD boxes referenced earlier), then I'd also look hard that >the uplink cabling as well - seeing that would be the one length of wire >that's common to all hosts off the switch. > >Good luck with this anyways.., Oh the joys of making patch cable!!!!! > >Regards, > >Stacey > > > >>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