From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Computing / Networking (Rated Start-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by Networking task force (marked as Mid-importance).

Removed from the article[edit]

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[1].

A doubt was raised about "still have the option to disable autonegotiation" at Talk:Ethernet. Source should be provided. (Liberatore, 2006). 12:19, 29 June 2006 (UTC)

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 [2].SDNick484 (talk) 22:33, 1 April 2009 (UTC)

Good article[edit]

I guess this article might qualify as a good article, and I intend to nominate it at Wikipedia:Good article candidates (Liberatore, 2006). 12:32, 9 August 2006 (UTC)

Updates needed for IEEE 802.3-2008[edit]

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 (talkcontribs) 22:44, 21 June 2011 (UTC)

Auto-negotiation confusion[edit]

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 (talk) 06:08, 21 June 2012 (UTC)

Section 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."

I intepret this as a requirement to assume half duplex but I can see how it could possiblly be interpreted otherwise. Plugwash (talk) 12:38, 31 December 2012 (UTC)