From owner-freebsd-net@FreeBSD.ORG Fri Jun 27 14:52:34 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 393C037B401 for ; Fri, 27 Jun 2003 14:52:34 -0700 (PDT) Received: from mail.buzzardnews.com (mail.buzzardnews.com [64.235.227.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE8EB4400D for ; Fri, 27 Jun 2003 14:52:33 -0700 (PDT) (envelope-from shawn@cpl.net) Received: from shawn ([216.117.221.133]) by mail.buzzardnews.com (8.11.3/8.11.3) with SMTP id h5RLqX417459 for ; Fri, 27 Jun 2003 14:52:33 -0700 (PDT) Message-ID: <010201c33cf5$eda0d360$85dd75d8@shawn> From: "Shawn Ramsey" To: References: Date: Fri, 27 Jun 2003 14:49:04 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Subject: Re: Lots of input errors... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 21:52:34 -0000 > > Ok.. It is set hard to 100BT/FD on both ends. I don't know if you saw this, > > but since resetting the stats a few hours ago, it shows no errors at all on > > their end, but were still getting errors on our end... The CRC and frame > > errors could have been from a media mismatch when things were first setup. > > Im not sure if the stats have ever been reset. Assuming the errors stay at > > zero on their end, any ideas? Am going to try another server/router, and if > > things look better, start replacing hardware on this router... > > > > I would say the physical wire is probably bad. Seeing unidirectional errors > in this case wouldn't be uncommon; one of the pair of the receive wires may > have issues. Have you swapped the cable? Most of the time you won't see > framing errors related to duplex mismatching. > > Also, although this sounds contrary to sane thinking about hard coding of > duplex and speed, the Cisco will do better autosensing if you are using an > Intel ethernet card on the server. I'm not sure why, but I've seen this > happen in the past. Im not sure if I asked this, but assuming the cable is bad, could this be causing the very high interupt usage we are seeing?