Just on that note I would like to mention It's a nightmare trying to hook
Foundry and Cisco together :)
-----Original Message-----
From: cisc...@puck.nether.net
[mailto:cisc...@puck.nether.net] On Behalf Of Mikael Abrahamsson
Sent: Sunday, January 16, 2005 2:34 AM
To: cisc...@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?
31 messages in net.nether.puck.cisco-nsp[c-nsp] autonegotiating hub was: Defe...
