[c-nsp] The myths of autonegotiate vs forced

[John Neiberger]

On Fri, Aug 20, 2010 at 2:18 AM, Mikael Abrahamsson <swmike at swm.pp.se> wrote:
> On Fri, 20 Aug 2010, Peter Rathlev wrote:
>
>> On Fri, 2010-08-20 at 09:34 +0200, Mikael Abrahamsson wrote:
>>>
>>> In case of having to force, do use "speed auto / duplex full" if your
>>> equipment supports it.
>>
>> And on a side note, if one needs to provide less-than-linerate speeds
>> (e.g. a 100 Mbps customer on a gigabit interface) it's much better to
>> use "speed auto 100" than "speed 100". Not all devices/modules support
>> it (by far), but it will give you the benefits of autonegotiate while
>> still "locking" the interface at a lower speed.
>>
>> The 3560G supports it, most 6500 modules seem not to AFAICT. Let's see
>> if 100 Mbps disappears before this will be generally implemented.
>
> I feature requested this (why stop doing autoneg just because you select a
> single speed/duplex, there is no downside to still announcing your
> capabilities), the response back was the usual "you're the only one asking
> for this"-answer.

In my opinion, this is how things should behave by default. Fast
Ethernet devices often check to see if they have an autonegotiating
link partner and will fall back to half duplex if they don't detect
one. For the life of me I can't understand Cisco's reasoning for
disabling it completely when the settings are manually configured. It
costs you nothing to leave Nway enabled, and it regularly causes
problems when it is disabled. What could their logic possibly be?
There are two options and they picked the worst one. I can't think of
any rationale that holds up to reasoning.