Ethernet

From Wikipedia, the free encyclopedia
Jump to: navigation, search
A standard 8P8C (often called RJ45) connector used most commonly on cat5 cable, a type of cabling used primarily in Ethernet networks

Ethernet (pronounced /ˈiːθərˌnɛt/) is a family of frame-based computer networking technologies for local area networks (LAN). It defines a number of wiring and signaling standards for the Physical Layer of the OSI networking model as well as a common addressing format and a variety of Medium Access Control procedures at the lower part of the Data Link Layer.

Ethernet is standardized as IEEE 802.3. The combination of the twisted pair versions of Ethernet for connecting end systems to the network, along with the fiber optic versions for site backbones, is the most widespread wired LAN technology. It has been used from around 1980[1] to the present, largely replacing competing LAN standards such as token ring, FDDI, and ARCNET.

Contents

History

Ethernet was developed at Xerox PARC between 1973 and 1975.[2] It was inspired by ALOHAnet, which Robert Metcalfe had studied as part of his Ph.D. dissertation.[3] In 1975, Xerox filed a patent application listing Metcalfe, David Boggs, Chuck Thacker and Butler Lampson as inventors.[4] In 1976, after the system was deployed at PARC, Metcalfe and Boggs published a seminal paper.[5][note 1]

Metcalfe left Xerox in 1979 to promote the use of personal computers and local area networks (LANs), forming 3Com. He convinced Digital Equipment Corporation (DEC), Intel, and Xerox to work together to promote Ethernet as a standard, the so-called "DIX" standard, for "Digital/Intel/Xerox"; it specified the 10 megabits/second Ethernet, with 48-bit destination and source addresses and a global 16-bit Ethertype-type field and was first published on September 30, 1980 as "The Ethernet, A Local Area Network. Data Link Layer and Physical Layer Specifications".[6] Version 2 of this document was published in November, 1982 and defines what has become known as Ethernet II. The Institute of Electrical and Electronics Engineers (IEEE) first published the 802.3 standard as a draft in 1983[7] and as a standard in 1985. Support of Ethernet's carrier sense multiple access with collision detection (CSMA/CD) in other standardization bodies (i.e., ECMA, IEC, and ISO) was instrumental in getting past delays of the finalization of the Ethernet standard due to the difficult decision processes in the IEEE, and due to the competitive Token Ring proposal strongly supported by IBM.[citation needed] Ethernet initially competed with two largely proprietary systems, Token Ring and Token Bus. These proprietary systems soon found themselves competing in a market inundated by Ethernet products. In the process, 3Com became a major company. 3Com shipped its first 10 Mbit/s Ethernet 3C100 transceiver in March 1981, and that year started selling adapters for DEC/PDP11 and VAXes, as well as Intel Multibus and Sun Microsystems machines.[8] This was followed quickly by DEC's Unibus to Ethernet adapter, which DEC sold and used internally to build its own corporate network, which reached over 10,000 nodes by 1986; far and away the largest extant computer network in the world at that time.[9]

Through the first half of the 1980s, DEC's Ethernet implementation, 10BASE5, used a coaxial cable 0.375 inches (9.5 mm) in diameter, later called "thick ethernet" or "thicknet" in contrast to its successor, 10BASE2, called "thin ethernet" or "thinnet". Thinnet uses a cable similar to cable television cable of the era. The emphasis was on making installation of the cable easier and less costly.

Shared cable Ethernet was always hard to install in offices because its bus topology was in conflict with the star topology cable plans designed into buildings for telephony. Modifying Ethernet to conform to twisted pair telephone wiring already installed in commercial buildings provided another opportunity to lower costs, expand the installed base, and leverage building design, and, thus, twisted-pair Ethernet was the next logical development in the mid-1980s, beginning with StarLAN. UTP-based Ethernet became widely deployed with the 10BASE-T standard. This system replaced the coaxial cable systems with a system of full duplex switches linked via UTP.

With the advent of the 10BASE-T standard in 1990, Ethernet switches supplemented the half duplex CSMA/CD scheme with a full duplex system offering higher performance at a lower cost than routers. With the arrival of 100BASE-T, Ethernet switches capable of mixed speed and mixed duplex operation were built.

Standardization

Notwithstanding its technical merits, timely standardization was instrumental to the success of Ethernet. It required well-coordinated and partly competitive activities in several standardization bodies such as the IEEE, ECMA, IEC, and finally ISO.

In February 1980, IEEE started a project, IEEE 802, for the standardization of local area networks (LAN).[10]

The "DIX-group" with Gary Robinson (DEC), Phil Arst (Intel), and Bob Printis (Xerox) submitted the so-called "Blue Book" CSMA/CD specification as a candidate for the LAN specification. Since IEEE membership is open to all professionals, including students, the group received countless comments on this brand-new technology.

In addition to CSMA/CD, Token Ring (supported by IBM) and Token Bus (selected and henceforward supported by General Motors) were also considered as candidates for a LAN standard. Due to the goal of IEEE 802 to forward only one standard and due to the strong company support for all three designs, the necessary agreement on a LAN standard was significantly delayed.

In the Ethernet camp, it put at risk the market introduction of the Xerox Star workstation and 3Com's Ethernet LAN products. With such business implications in mind, David Liddle (General Manager, Xerox Office Systems) and Metcalfe (3Com) strongly supported a proposal of Fritz Röscheisen (Siemens Private Networks) for an alliance in the emerging office communication market, including Siemens' support for the international standardization of Ethernet (April 10, 1981). Ingrid Fromm, Siemens representative to IEEE 802 quickly achieved broader support for Ethernet beyond IEEE by the establishment of a competing Task Group "Local Networks" within the European standards body ECMA TC24. As early as March 1982 ECMA TC24 with its corporate members reached agreement on a standard for CSMA/CD based on the IEEE 802 draft. The speedy action taken by ECMA decisively contributed to the conciliation of opinions within IEEE and approval of IEEE 802.3 CSMA/CD by the end of 1982.

Approval of Ethernet on the international level was achieved by a similar, cross-partisan action with Fromm as liaison officer working to integrate IEC TC83 and ISO TC97SC6, and the ISO/IEEE 802/3 standard was approved in 1984.

Evolution

Ethernet is an evolving technology. Evolutions have included higher bandwidth, improved media access control methods, and changes to the physical medium. Ethernet evolved into the complex networking technology that today underlies most LANs. The coaxial cable was replaced with point-to-point links connected by Ethernet repeaters or switches to reduce installation costs, increase reliability, and enable point-to-point management and troubleshooting. There are many variants of Ethernet in common use.

Ethernet stations communicate by sending each other data packets, blocks of data that are individually sent and delivered. As with other IEEE 802 LANs, each Ethernet station is given a 48-bit MAC address. The MAC addresses are used to specify both the destination and the source of each data packet. Network interface cards (NICs) or chips normally do not accept packets addressed to other Ethernet stations. Adapters come programmed with a globally unique address.[note 2] Despite the significant changes in Ethernet from a thick coaxial cable bus running at 10 Mbit/s to point-to-point links running at 1 Gbit/s and beyond, all generations of Ethernet (excluding early experimental versions) use the same frame formats (and hence the same interface for higher layers), and can be readily interconnected through bridging.[citation needed]

Due to the ubiquity of Ethernet, the ever-decreasing cost of the hardware needed to support it, and the reduced panel space needed by twisted pair Ethernet, most manufacturers now build the functionality of an Ethernet card directly into PC motherboards, eliminating the need for installation of a separate network card.[11]

Shared media

A 1990s network interface card supporting both coaxial cable-based 10BASE2 (BNC connector, left) and twisted pair-based 10BASE-T (8P8C connector, right).

Ethernet was originally based on the idea of computers communicating over a shared coaxial cable acting as a broadcast transmission medium. The methods used were similar to those used in radio systems,[note 3] with the common cable providing the communication channel likened to the Luminiferous Aether in 19th century physics, and it was from this reference that the name "Ethernet" was derived.[12][13]

Original Ethernet's shared coaxial cable (the shared medium) traversed a building or campus to every attached machine. A scheme known as carrier sense multiple access with collision detection (CSMA/CD) governed the way the computers shared the channel. This scheme was simpler than the competing token ring or token bus technologies.[note 4] Computers were connected to an Attachment Unit Interface (AUI) transceiver, which was in turn connected to the cable (later with thin Ethernet the transceiver was integrated into the network adapter). While a simple passive wire was highly reliable for small networks, it was not reliable for large extended networks, where damage to the wire in a single place, or a single bad connector, could make the whole Ethernet segment unusable.[note 5]

Since all communications happen on the same wire, any information sent by one computer is received by all, even if that information is intended for just one destination.[note 6] The network interface card interrupts the CPU only when applicable packets are received: The card ignores information not addressed to it.[note 7] Use of a single cable also means that the bandwidth is shared, so that network traffic can be very slow when many stations are simultaneously active.

Collisions reduce throughput by their very nature. In the worst case, when there are lots of hosts with long cables that attempt to transmit many short frames, excessive collisions can reduce throughput dramatically. However, a Xerox report in 1980 summarized the results of having 20 fast nodes attempting to transmit packets of various sizes as quickly as possible on the same Ethernet segment.[14] The results showed that, even for the smallest Ethernet frames (64 Bytes), 90% throughput on the LAN was the norm. This is in comparison with token passing LANs (token ring, token bus), all of which suffer throughput degradation as each new node comes into the LAN, due to token waits. This report was controversial, as modeling showed that collision-based networks became unstable under loads as low as 40% of nominal capacity. Many early researchers failed to understand the subtleties of the CSMA/CD protocol and how important it was to get the details right, and were really modeling somewhat different networks (usually not as good as real Ethernet).[15]

Repeaters and hubs

For signal degradation and timing reasons, coaxial Ethernet segments had a restricted size. Somewhat larger networks could be built by using an Ethernet repeater. Initial repeaters had only 2 ports, but they gave way to 4, 6, 8, and more ports. People recognized the advantages of cabling in a star topology, primarily that a fault in one of the legs affects operation of only the stations attached to that leg.[citation needed]

A twisted pair Cat-3 or Cat-5 cable is used to connect 10BASE-T Ethernet

Ethernet on unshielded twisted-pair cables (UTP), beginning with StarLAN and continuing with 10BASE-T, was designed for point-to-point links only, and all termination was built into the device. This changed repeaters from a specialist device used at the center of large networks to a device that every twisted pair-based network with more than two machines had to use. The tree structure that resulted from this made Ethernet networks more reliable by preventing faults with one peer or its associated cable from affecting other devices on the network.[note 8]

Despite the physical star topology, repeater based Ethernet networks still use half-duplex and CSMA/CD, with only minimal activity by the repeater, primarily the Collision Enforcement signal, in dealing with packet collisions. Every packet is sent to every port on the repeater, so bandwidth and security problems are not addressed. The total throughput of the repeater is limited to that of a single link, and all links must operate at the same speed.

Bridging and switching

While repeaters could isolate some aspects of Ethernet segments, such as cable breakages, they still forwarded all traffic to all Ethernet devices. This created practical limits on how many machines could communicate on an Ethernet network. The entire network was one collision domain, and all hosts had to be able to detect collisions anywhere on the network. This limited the number of repeaters between the farthest nodes. Segments joined by repeaters had to all operate at the same speed, making phased-in upgrades impossible.

To alleviate these problems, bridging was created to communicate at the data link layer while isolating the physical layer. With bridging, only well-formed Ethernet packets are forwarded from one Ethernet segment to another; collisions and packet errors are isolated. Prior to discovery of network devices on the different segments, Ethernet bridges (and switches) work somewhat like Ethernet repeaters, passing all traffic between segments. However, as the bridge discovers the addresses associated with each port, it forwards network traffic only to the necessary segments, improving overall performance. Broadcast traffic is still forwarded to all network segments. Bridges also overcame the limits on total segments between two hosts and allowed the mixing of speeds, both of which became very important with the introduction of Fast Ethernet.

Early bridges examined each packet one by one using software on a CPU, and some of them were significantly slower than repeaters at forwarding traffic, especially when handling many ports at the same time.[citation needed] This was in part because the entire Ethernet packet would be read into a buffer, the destination address compared with an internal table of known MAC addresses, and a decision made as to whether to drop the packet or forward it to another or all segments.

In 1989, the networking company Kalpana introduced their EtherSwitch, the first Ethernet switch.[note 9] This worked somewhat differently from an Ethernet bridge, in that only the header of the incoming packet would be examined before it was either dropped or forwarded to another segment. This greatly reduced the forwarding latency and the processing load on the network device. One drawback of this cut-through switching method was that packets that had been corrupted would still be propagated through the network, so a jabbering station could continue to disrupt the entire network. The eventual remedy for this was a return to the original store and forward approach of bridging, where the packet would be read into a buffer on the switch in its entirety, verified against its checksum and then forwarded, but using more powerful application-specific integrated circuits. Hence, the bridging is then done in hardware, allowing packets to be forwarded at full wire speed.

When a twisted pair or fiber link segment is used and neither end is connected to a repeater, full-duplex Ethernet becomes possible over that segment. In full-duplex mode, both devices can transmit and receive to and from each other at the same time, and there is no collision domain. This doubles the aggregate bandwidth of the link and is sometimes advertised as double the link speed (e.g., 200 Mbit/s).[note 10] The elimination of the collision domain for these connections also means that all the link's bandwidth can be used by the two devices on that segment and that segment length is not limited by the need for correct collision detection.

Since packets are typically delivered only to the port they are intended for, traffic on a switched Ethernet is less public than on shared-medium Ethernet. Despite this, switched Ethernet should still be regarded as an insecure network technology, because it is easy to subvert switched Ethernet systems by means such as ARP spoofing and MAC flooding.

The bandwidth advantages, the slightly better isolation of devices from each other, the ability to easily mix different speeds of devices and the elimination of the chaining limits inherent in non-switched Ethernet have made switched Ethernet the dominant network technology.[16]

Advanced networking

Simple switched Ethernet networks, while a great improvement over repeater-based Ethernet, suffer from single points of failure, attacks that trick switches or hosts into sending data to a machine even if it is not intended for it, scalability and security issues with regard to broadcast radiation and multicast traffic, and bandwidth choke points where a lot of traffic is forced down a single link.[citation needed]

Advanced networking features in switches and routers combat these issues through a number of means including spanning-tree protocol to maintain the active links of the network as a tree while allowing physical loops for redundancy, port security and protection features such as MAC lock down and broadcast radiation filtering, virtual LANs to keep different classes of users separate while using the same physical infrastructure, multilayer switching to route between different classes and link aggregation to add bandwidth to overloaded links and to provide some measure of redundancy.

Varieties of Ethernet

The Ethernet physical layer evolved over a considerable time span and encompasses quite a few physical media interfaces and several magnitudes of speed. The most common forms used are 10BASE-T, 100BASE-TX, and 1000BASE-T. All three utilize twisted pair cables and 8P8C modular connectors. They run at 10 Mbit/s, 100 Mbit/s, and 1 Gbit/s, respectively. Fiber optic variants of Ethernet offer high performance, electrical isolation and distance (up to tens of kilometers with some versions). In general, network protocol stack software will work similarly on all varieties.

Ethernet frames

A data packet on the wire is called a frame. A frame begins with Preamble and Start Frame Delimiter, following which each Ethernet frame features an Ethernet header featuring source and destination MAC addresses. The middle section of the frame consists of payload data including any headers for other protocols (e.g., Internet Protocol) carried in the frame. The frame ends with a 32-bit cyclic redundancy check, which is used to detect any corruption of data in transit.

Autonegotiation

Autonegotiation is the procedure by which two connected devices choose common transmission parameters, such as speed and duplex mode. Autonegotiation was first introduced as an optional feature for Fast Ethernet, but it is also backward compatible with 10BASE-T. Autonegotiation is mandatory for Gigabit Ethernet.

See also

Notes

  1. ^ The experimental Ethernet described in the 1976 paper ran at 3 Mbit/s and had eight-bit destination and source address fields, so the original Ethernet addresses were not the MAC addresses they are today. By software convention, the 16 bits after the destination and source address fields specified a "packet type", but, as the paper says, "different protocols use disjoint sets of packet types". Thus the original packet types could vary within each different protocol, rather than the packet type in the current Ethernet standard, which specifies the protocol being used.
  2. ^ In some cases, the factory-assigned address can be overridden, either to avoid an address change when an adapter is replaced or to use locally administered addresses.
  3. ^ There are fundamental differences between wireless and wired shared-medium communications, such as the fact that it is much easier to detect collisions in a wired system system than a wireless system.
  4. ^ In a CSMA/CD system packets must be large enough to guarantee that the leading edge of the propagating wave of the message got to all parts of the medium before the transmitter could stop transmitting, thus guaranteeing that collisions (two or more packets initiated within a window of time that forced them to overlap) would be discovered. Minimum packet size and the physical medium's total length were, thus, closely linked.
  5. ^ Multipoint systems are also prone to strange failure modes when an electrical discontinuity reflects the signal in such a manner that some nodes would work properly, while others work slowly because of excessive retries or not at all. See standing wave for an explanation. These could be much more difficult to diagnose than a complete failure of the segment.
  6. ^ This "one speaks, all listen" property is a security weakness of shared-medium Ethernet, since a node on an Ethernet network can eavesdrop on all traffic on the wire if it so chooses.
  7. ^ Unless it is put into "promiscuous mode"
  8. ^ Some peer fault modes (e.g., deliberate misbehavior) could still affect other devices on the network.
  9. ^ The term switch was invented by device manufacturers and does not appear in the 802.3 standard.
  10. ^ This is misleading, as performance will double only if traffic patterns are symmetrical.

References

  1. ^ "Ethernet", Internetworking Technology Handbook, Cisco Systems, http://docwiki.cisco.com/wiki/Ethernet_Technologies, retrieved 2011-02-09 
  2. ^ "Ethernet Prototype Circuit Board". Smithsonian National Museum of American History. http://americanhistory.si.edu/collections/object.cfm?key=35&objkey=96. Retrieved 2007-09-02. 
  3. ^ Gerald W. Brock (2003-09-25). The Second Information Revolution. Harvard University Press. p. 151. ISBN 0674011783. 
  4. ^ U.S. Patent 4,063,220 "Multipoint data communication system (with collision detection)"
  5. ^ Metcalfe, Robert M. and Boggs, David R. (July 1976). "Ethernet: Distributed Packet Switching for Local Computer Networks". Communications of the ACM 19 (5): 395–405. doi:10.1145/360248.360253. http://portal.acm.org/citation.cfm?id=360253&dl=ACM&coll=ACM&CFID=39370057&CFTOKEN=52797288. 
  6. ^ Digital Equipment Corporation, Intel Corporation and Xerox Corporation. The Ethernet, A Local Area Network. Data Link Layer and Physical Layer Specifications. Xerox Corporation. 
  7. ^ Robert Breyer & Sean Riley. Switched, Fast, and Gigabit Ethernet. Macmillan. p. 8. ISBN 1-57870-073-6. 
  8. ^ Robert Breyer & Sean Riley. Switched, Fast, and Gigabit Ethernet. Macmillan. p. 9. ISBN 1-57870-073-6. 
  9. ^ Jamie Parker Pearson. Digital at Work. Digital Press. p. 163. ISBN 1555580920. 
  10. ^ Vic Hayes (27 August 2001). "Letter to FCC". http://www.ieeeusa.org/policy/policy/2001/01aug27IEEE802.pdf. Retrieved 2010-10-22. "IEEE 802 has the basic charter to develop and maintain networking standards... IEEE 802 was formed in February 1980..." 
  11. ^ Geetaj Channana (1 November 2004). "Motherboard Chipsets Roundup". PCQuest. http://pcquest.ciol.com/content/search/showarticle.asp?artid=63428. Retrieved 2010-10-22. "While comparing motherboards in the last issue we found that all motherboards support Ethernet connection on board." 
  12. ^ Charles E. Spurgeon (2000). Ethernet: The Definitive Guide. O'Reilly. ISBN 978-1565926608. 
  13. ^ Charles Spurgeon. "Why is it called Ethernet?". http://www.ethermanage.com/ethernet/ethername.html. Retrieved 2010-10-22. 
  14. ^ Shoch, John F. and Hupp, Jon A. (December 1980). "Measured performance of an Ethernet local network". Communications of the ACM (ACM Press) 23 (12): 711–721. doi:10.1145/359038.359044. ISSN: 0001-0782. http://portal.acm.org/citation.cfm?doid=359038.359044#abstract. 
  15. ^ Boggs, D.R., Mogul, J.C., and Kent, C.A. (August 1988). "Measured capacity of an Ethernet: myths and reality". ACM SIGCOMM Computer Communication Review (ACM Press) 18 (4): 222–234. doi:10.1145/52325.52347. ISBN 0-89791-279-9. http://portal.acm.org/citation.cfm?doid=52325.52347#abstract. 
  16. ^ "Token Ring-to-Ethernet Migration". Cisco. http://www.cisco.com/en/US/solutions/collateral/ns340/ns394/ns74/ns149/net_business_benefit09186a00800c92b9_ps6600_Products_White_Paper.html. Retrieved 2010-10-22. "Respondents were first asked about their current and planned desktop LAN attachment standards. The results were clear—switched Fast Ethernet is the dominant choice for desktop connectivity to the network" 

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Interaction
Toolbox
Print/export
Languages