From: Adam (suckmy-balls.com)
Date: Fri Dec 17 2004 - 11:56:04 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Thu, Dec 16, 2004 at 10:46:26PM -0800, Greg Thomas wrote:
> Ok, I have great respect for Henning and others on the list but how
> has autonegotiation gotten such a bad rap if there aren't some
> problems out there?

Nobody said broken hardware doesn't exist. There have been some devices
which had faulty autoneg code, probably all of them have new
firmware/ios/whatever available to fix the problem though. Also, I've
seen people claim autoneg is broken because they tried to autoneg with a
device that doesn't even support it, and obviously it failed. The point
is, do people claim TCP is broken because some crappy switch always uses
the same ISN? Faulty implimentations do not make a protocol "broken".

> When a local tech sees a throughput problem when the switch and NIC
> are set to autonegotiation he asks the network guys to set the port to
> 100 full-duplex. He then changes the NIC of the problem machine to
> 100 full-duplex and the problem goes away.

I've seen people assume this before when actually, someone had left that
port in 100/full already, and then the machine tried to autoneg, failed
obviously, and got 100/half. Then the busy admin just forced them both
to 100/full, not even checking what they were in to start with, and
thinks forever more that autneg is broken. This may not be the case
where you are, but its sadly common, so worth a closer look. Otherwise
you probably just need to update the switch.

Adam

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]