[c-nsp] autonegotiating hub was: Deferred packets on 295010/full interface

[Majid Farid]

Just on that note I would like to mention It's a nightmare trying to hook Foundry and Cisco together :)


--
Majid

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Mikael Abrahamsson
Sent: Sunday, January 16, 2005 2:34 AM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] autonegotiating hub was: Deferred packets on 295010/full interface

On Sat, 15 Jan 2005, Michael K. Smith wrote:

> There is a Technology Ability Field bit that allows you to tell the
> other side what you support vis-à-vis speed and duplex.  So, it is
> possible to have a hub that can have the appropriate bit set to tell the
> other side that it supports 100TX, but not have a bit set for supporting
> 100-Full Duplex.

This is what I want all vendors to support. If you set 100/f hard, then
keep the autoneg going but only announce ability to do 100/f. I see no 
reason to turn autoneg off just because you have fixed both duplex and 
speed? I haven't been able to aquire an answer to the rationale vendors 
have applied when opting to disable NWay when both duplex and speed is 
fixed?

-- 
Mikael Abrahamsson    email: swmike at swm.pp.se


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/