Date: Fri, 27 Jun 2003 14:49:04 -0700 From: "Shawn Ramsey" <shawn@cpl.net> To: <freebsd-net@freebsd.org> Subject: Re: Lots of input errors... Message-ID: <010201c33cf5$eda0d360$85dd75d8@shawn> References: <BB21F606.155E7%mksmith@noanet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?010201c33cf5$eda0d360$85dd75d8>