|WikiProject Computing / Networking||(Rated Start-class, Low-importance)|
Removed from the article
- Note that some switch operating systems, as well as some card drivers, still have the option to disable autonegotiation and force a twisted pair connection to 1000Base-T full duplex or 1000Base-T half duplex, but this is against specification and should never be used because this way the other parameters required for Gigabit Ethernet operation are not negotiated. The correct way for forcing Gigabit Ethernet operation is to enable autonegotiation, but limit the advertised capabilities to the 1000Base-T ones only.
Well this is a way old discussion and I'm not going to add the section back, but here's a quote from a Sun document showing they did offer hardware with this capability (1000 Full-forced, Autoneg-disabled), "The IEEE 802.3ab specification does not allow for forced mode 1000BASE-T with autonegotiation disabled running at 1000 Mbps. As a result, many switch vendors do not support forced mode. Although the transceiver used in the Sun™ Gigaswift Ethernet UTP adapter 1.0 is configurable for the 1000 Mbps forced mode and the ce driver allows this mode be aware that it does not work under certain circumstances." Ethernet Autonegotiation Best Practices .SDNick484 (talk) 22:33, 1 April 2009 (UTC)
Updates needed for IEEE 802.3-2008
This page could be updated to include the fact that 10GBASE-T (10 gigabit ethernet over copper) now also requires autonegotiation and that Extended Next Pages were added in the standard and are required for 10GBASE-T autonegotation. The Priority table section would also need to have 10GBASE-T added. — Preceding unsigned comment added by Blockfloetenspieler (talk • contribs) 22:44, 21 June 2011 (UTC)
This page states explicitly that when auto-negotiation fails a device that is trying negotiate should go to half-duplex. I am familar with one implementation (JunOS for J-Series, ver 11.1R3.5) that goes to full duplex instead. I have also read the description in the first reference in the article and have been unable to discover any requirement to fail back to half-duplex. This does happen with Cisco implementations, but doesn't seem to be part of the standard. — Preceding unsigned comment added by 220.127.116.11 (talk) 06:08, 21 June 2012 (UTC)
- Section 18.104.22.168 of 802.3
- "NOTE 2—When selecting the highest common denominator through the Parallel Detection function, only the halfduplex
mode corresponding to the selected PMA may automatically be detected."