10BASE5
7.1.2 This page will discuss the original 1980 Ethernet product, which is 10BASE5. 10BASE5 transmitted 10 Mbps over a single think coaxial cable bus.
10BASE5 is important because it was the first medium used for Ethernet. 10BASE5 was part of the original 802.3 standard. The primary benefit of 10BASE5 was length. 10BASE5 may be found in legacy installations. It is not recommended for new installations. 10BASE5 systems are inexpensive and require no configuration. Two disadvantages are that basic components like NICs are very difficult to find and it is sensitive to signal reflections on the cable. 10BASE5 systems also represent a single point of failure.
10BASE5 uses Manchester encoding. It has a solid central conductor. Each segment of thick coax may be up to 500 m (1640.4 ft) in length. The cable is large, heavy, and difficult to install. However, the distance limitations were favorable and this prolonged its use in certain applications.
When the medium is a single coaxial cable, only one station can transmit at a time or a collision will occur. Therefore, 10BASE5 only runs in half-duplex with a maximum transmission rate of 10 Mbps.
Figure illustrates a configuration for an end-to-end collision domain with the maximum number of segments and repeaters. Remember that only three segments can have stations connected to them. The other two repeated segments are used to extend the network.
The next page will discuss 10BASE2.
Tuesday, January 26, 2010
10-Mbps and 100-Mbps Ethernet
10-Mbps Ethernet
7.1.1 This page will discuss 10-Mbps Ethernet technologies.
10BASE5, 10BASE2, and 10BASE-T Ethernet are considered Legacy Ethernet. The four common features of Legacy Ethernet are timing parameters, the frame format, transmission processes, and a basic design rule.
Figure displays the parameters for 10-Mbps Ethernet operation. 10-Mbps Ethernet and slower versions are asynchronous. Each receiving station uses eight octets of timing information to synchronize its receive circuit to the incoming data. 10BASE5, 10BASE2, and 10BASE-T all share the same timing parameters. For example, 1 bit time at 10 Mbps = 100 nanoseconds (ns) = 0.1 microseconds = 1 10-millionth of a second. This means that on a 10-Mbps Ethernet network, 1 bit at the MAC sublayer requires 100 ns to transmit.
For all speeds of Ethernet transmission 1000 Mbps or slower, transmission can be no slower than the slot time. Slot time is just longer than the time it theoretically can take to go from one extreme end of the largest legal Ethernet collision domain to the other extreme end, collide with another transmission at the last possible instant, and then have the collision fragments return to the sending station to be detected.
10BASE5, 10BASE2, and 10BASE-T also have a common frame format.
The Legacy Ethernet transmission process is identical until the lower part of the OSI physical layer. As the frame passes from the MAC sublayer to the physical layer, other processes occur before the bits move from the physical layer onto the medium. One important process is the signal quality error (SQE) signal. The SQE is a transmission sent by a transceiver back to the controller to let the controller know whether the collision circuitry is functional. The SQE is also called a heartbeat. The SQE signal is designed to fix the problem in earlier versions of Ethernet where a host does not know if a transceiver is connected. SQE is always used in half-duplex. SQE can be used in full-duplex operation but is not required. SQE is active in the following instances:
• Within 4 to 8 microseconds after a normal transmission to indicate that the outbound frame was successfully transmitted
• Whenever there is a collision on the medium
• Whenever there is an improper signal on the medium, such as jabber, or reflections that result from a cable short
• Whenever a transmission has been interrupted
All 10-Mbps forms of Ethernet take octets received from the MAC sublayer and perform a process called line encoding. Line encoding describes how the bits are actually signaled on the wire. The simplest encodings have undesirable timing and electrical characteristics. Therefore, line codes have been designed with desirable transmission properties. This form of encoding used in 10-Mbps systems is called Manchester encoding.
Manchester encoding uses the transition in the middle of the timing window to determine the binary value for that bit period. In Figure , the top waveform moves to a lower position so it is interpreted as a binary zero. The second waveform moves to a higher position and is interpreted as a binary one. The third waveform has an alternating binary sequence. When binary data alternates, there is no need to return to the previous voltage level before the next bit period. The wave forms in the graphic show that the binary bit values are determined based on the direction of change in a bit period. The voltage levels at the start or end of any bit period are not used to determine binary values.
Legacy Ethernet has common architectural features. Networks usually contain multiple types of media. The standard ensures that interoperability is maintained. The overall architectural design is most important in mixed-media networks. It becomes easier to violate maximum delay limits as the network grows. The timing limits are based on the following types of parameters:
• Cable length and propagation delay
• Delay of repeaters
• Delay of transceivers
• Interframe gap shrinkage
• Delays within the station
10-Mbps Ethernet operates within the timing limits for a series of up to five segments separated by up to four repeaters. This is known as the 5-4-3 rule. No more than four repeaters can be used in series between any two stations. There can also be no more than three populated segments between any two stations.
The next page will describe 10BASE5.
7.1.1 This page will discuss 10-Mbps Ethernet technologies.
10BASE5, 10BASE2, and 10BASE-T Ethernet are considered Legacy Ethernet. The four common features of Legacy Ethernet are timing parameters, the frame format, transmission processes, and a basic design rule.
Figure displays the parameters for 10-Mbps Ethernet operation. 10-Mbps Ethernet and slower versions are asynchronous. Each receiving station uses eight octets of timing information to synchronize its receive circuit to the incoming data. 10BASE5, 10BASE2, and 10BASE-T all share the same timing parameters. For example, 1 bit time at 10 Mbps = 100 nanoseconds (ns) = 0.1 microseconds = 1 10-millionth of a second. This means that on a 10-Mbps Ethernet network, 1 bit at the MAC sublayer requires 100 ns to transmit.
For all speeds of Ethernet transmission 1000 Mbps or slower, transmission can be no slower than the slot time. Slot time is just longer than the time it theoretically can take to go from one extreme end of the largest legal Ethernet collision domain to the other extreme end, collide with another transmission at the last possible instant, and then have the collision fragments return to the sending station to be detected.
10BASE5, 10BASE2, and 10BASE-T also have a common frame format.
The Legacy Ethernet transmission process is identical until the lower part of the OSI physical layer. As the frame passes from the MAC sublayer to the physical layer, other processes occur before the bits move from the physical layer onto the medium. One important process is the signal quality error (SQE) signal. The SQE is a transmission sent by a transceiver back to the controller to let the controller know whether the collision circuitry is functional. The SQE is also called a heartbeat. The SQE signal is designed to fix the problem in earlier versions of Ethernet where a host does not know if a transceiver is connected. SQE is always used in half-duplex. SQE can be used in full-duplex operation but is not required. SQE is active in the following instances:
• Within 4 to 8 microseconds after a normal transmission to indicate that the outbound frame was successfully transmitted
• Whenever there is a collision on the medium
• Whenever there is an improper signal on the medium, such as jabber, or reflections that result from a cable short
• Whenever a transmission has been interrupted
All 10-Mbps forms of Ethernet take octets received from the MAC sublayer and perform a process called line encoding. Line encoding describes how the bits are actually signaled on the wire. The simplest encodings have undesirable timing and electrical characteristics. Therefore, line codes have been designed with desirable transmission properties. This form of encoding used in 10-Mbps systems is called Manchester encoding.
Manchester encoding uses the transition in the middle of the timing window to determine the binary value for that bit period. In Figure , the top waveform moves to a lower position so it is interpreted as a binary zero. The second waveform moves to a higher position and is interpreted as a binary one. The third waveform has an alternating binary sequence. When binary data alternates, there is no need to return to the previous voltage level before the next bit period. The wave forms in the graphic show that the binary bit values are determined based on the direction of change in a bit period. The voltage levels at the start or end of any bit period are not used to determine binary values.
Legacy Ethernet has common architectural features. Networks usually contain multiple types of media. The standard ensures that interoperability is maintained. The overall architectural design is most important in mixed-media networks. It becomes easier to violate maximum delay limits as the network grows. The timing limits are based on the following types of parameters:
• Cable length and propagation delay
• Delay of repeaters
• Delay of transceivers
• Interframe gap shrinkage
• Delays within the station
10-Mbps Ethernet operates within the timing limits for a series of up to five segments separated by up to four repeaters. This is known as the 5-4-3 rule. No more than four repeaters can be used in series between any two stations. There can also be no more than three populated segments between any two stations.
The next page will describe 10BASE5.
Module 7: Ethernet Technologies
Overview
Ethernet has been the most successful LAN technology mainly because of how easy it is to implement. Ethernet has also been successful because it is a flexible technology that has evolved as needs and media capabilities have changed. This module will provide details about the most important types of Ethernet. The goal is to help students understand what is common to all forms of Ethernet.
Changes in Ethernet have resulted in major improvements over the 10-Mbps Ethernet of the early 1980s. The 10-Mbps Ethernet standard remained virtually unchanged until 1995 when IEEE announced a standard for a 100-Mbps Fast Ethernet. In recent years, an even more rapid growth in media speed has moved the transition from Fast Ethernet to Gigabit Ethernet. The standards for Gigabit Ethernet emerged in only three years. A faster Ethernet version called 10-Gigabit Ethernet is now widely available and faster versions will be developed.
MAC addresses, CSMA/CD, and the frame format have not been changed from earlier versions of Ethernet. However, other aspects of the MAC sublayer, physical layer, and medium have changed. Copper-based NICs capable of 10, 100, or 1000 Mbps are now common. Gigabit switch and router ports are becoming the standard for wiring closets. Optical fiber to support Gigabit Ethernet is considered a standard for backbone cables in most new installations.
This module covers some of the objectives for the CCNA 640-801, INTRO 640-821, and ICND 640-811 exams.
Students who complete this module should be able to perform the following tasks:
• Describe the differences and similarities among 10BASE5, 10BASE2, and 10BASE-T Ethernet
• Define Manchester encoding
• List the factors that affect Ethernet timing limits
• List 10BASE-T wiring parameters
• Describe the key characteristics and varieties of 100-Mbps Ethernet
• Describe the evolution of Ethernet
• Explain the MAC methods, frame formats, and transmission process of Gigabit Ethernet
• Describe the uses of specific media and encoding with Gigabit Ethernet
• Identify the pinouts and wiring typical to the various implementations of Gigabit Ethernet
• Describe the similarities and differences between Gigabit and 10-Gigabit Ethernet
• Describe the basic architectural considerations of Gigabit and 10-Gigabit Ethernet
Ethernet has been the most successful LAN technology mainly because of how easy it is to implement. Ethernet has also been successful because it is a flexible technology that has evolved as needs and media capabilities have changed. This module will provide details about the most important types of Ethernet. The goal is to help students understand what is common to all forms of Ethernet.
Changes in Ethernet have resulted in major improvements over the 10-Mbps Ethernet of the early 1980s. The 10-Mbps Ethernet standard remained virtually unchanged until 1995 when IEEE announced a standard for a 100-Mbps Fast Ethernet. In recent years, an even more rapid growth in media speed has moved the transition from Fast Ethernet to Gigabit Ethernet. The standards for Gigabit Ethernet emerged in only three years. A faster Ethernet version called 10-Gigabit Ethernet is now widely available and faster versions will be developed.
MAC addresses, CSMA/CD, and the frame format have not been changed from earlier versions of Ethernet. However, other aspects of the MAC sublayer, physical layer, and medium have changed. Copper-based NICs capable of 10, 100, or 1000 Mbps are now common. Gigabit switch and router ports are becoming the standard for wiring closets. Optical fiber to support Gigabit Ethernet is considered a standard for backbone cables in most new installations.
This module covers some of the objectives for the CCNA 640-801, INTRO 640-821, and ICND 640-811 exams.
Students who complete this module should be able to perform the following tasks:
• Describe the differences and similarities among 10BASE5, 10BASE2, and 10BASE-T Ethernet
• Define Manchester encoding
• List the factors that affect Ethernet timing limits
• List 10BASE-T wiring parameters
• Describe the key characteristics and varieties of 100-Mbps Ethernet
• Describe the evolution of Ethernet
• Explain the MAC methods, frame formats, and transmission process of Gigabit Ethernet
• Describe the uses of specific media and encoding with Gigabit Ethernet
• Identify the pinouts and wiring typical to the various implementations of Gigabit Ethernet
• Describe the similarities and differences between Gigabit and 10-Gigabit Ethernet
• Describe the basic architectural considerations of Gigabit and 10-Gigabit Ethernet
Summary of Module 6
Summary
This page summarizes the topics discussed in this module.
Ethernet is not one networking technology, but a family of LAN technologies that includes Legacy, Fast Ethernet, and Gigabit Ethernet. When Ethernet needs to be expanded to add a new medium or capability, the IEEE issues a new supplement to the 802.3 standard. The new supplements are given a one or two letter designation such as 802.3u. Ethernet relies on baseband signaling, which uses the entire bandwidth of the transmission medium. Ethernet operates at two layers of the OSI model, the lower half of the data link layer, known as the MAC sublayer and the physical layer. Ethernet at Layer 1 involves interfacing with media, signals, bit streams that travel on the media, components that put signals on media, and various physical topologies. Layer 1 bits need structure so OSI Layer 2 frames are used. The MAC sublayer of Layer 2 determines the type of frame appropriate for the physical media.
The one thing common to all forms of Ethernet is the frame structure. This is what allows the interoperability of the different types of Ethernet.
Some of the fields permitted or required in an 802.3 Ethernet Frame are:
• Preamble
• Start Frame Delimiter
• Destination Address
• Source Address
• Length/Type
• Data and Pad
• Frame Check Sequence
In 10 Mbps and slower versions of Ethernet, the Preamble provides timing information the receiving node needs in order to interpret the electrical signals it is receiving. The Start Frame Delimiter marks the end of the timing information. 10 Mbps and slower versions of Ethernet are asynchronous. That is, they will use the preamble timing information to synchronize the receive circuit to the incoming data. 100 Mbps and higher speed implementations of Ethernet are synchronous. Synchronous means the timing information is not required, however for compatibility reasons the Preamble and SFD are present.
The address fields of the Ethernet frame contain Layer 2, or MAC, addresses.
All frames are susceptible to errors from a variety of sources. The Frame Check Sequence (FCS) field of an Ethernet frame contains a number that is calculated by the source node based on the data in the frame. At the destination it is recalculated and compared to determine that the data received is complete and error free.
Once the data is framed the Media Access Control (MAC) sublayer is also responsible to determine which computer on a shared-medium environment, or collision domain, is allowed to transmit the data. There are two broad categories of Media Access Control, deterministic (taking turns) and non-deterministic (first come, first served).
Examples of deterministic protocols include Token Ring and FDDI. The carrier sense multiple access with collision detection (CSMA/CD) access method is a simple non-deterministic system. The NIC listens for an absence of a signal on the media and starts transmitting. If two nodes or more nodes transmit at the same time a collision occurs. If a collision is detected the nodes wait a random amount of time and retransmit.
The minimum spacing between two non-colliding frames is also called the interframe spacing. Interframe spacing is required to insure that all stations have time to process the previous frame and prepare for the next frame.
Collisions can occur at various points during transmission. A collision where a signal is detected on the receive and transmit circuits at the same time is referred to as a local collision. A collision that occurs before the minimum number of bytes can be transmitted is called a remote collision. A collision that occurs after the first sixty-four octets of data have been sent is considered a late collision. The NIC will not automatically retransmit for this type of collision.
While local and remote collisions are considered to be a normal part of Ethernet operation, late collisions are considered to be an error. Ethernet errors result from detection of frames sizes that are longer or shorter than standards allow or excessively long or illegal transmissions called jabber. Runt is a slang term that refers to something less than the legal frame size.
Auto-Negotiation detects the speed and duplex mode, half-duplex or full-duplex, of the device on the other end of the wire and adjusts to match those settings.
This page summarizes the topics discussed in this module.
Ethernet is not one networking technology, but a family of LAN technologies that includes Legacy, Fast Ethernet, and Gigabit Ethernet. When Ethernet needs to be expanded to add a new medium or capability, the IEEE issues a new supplement to the 802.3 standard. The new supplements are given a one or two letter designation such as 802.3u. Ethernet relies on baseband signaling, which uses the entire bandwidth of the transmission medium. Ethernet operates at two layers of the OSI model, the lower half of the data link layer, known as the MAC sublayer and the physical layer. Ethernet at Layer 1 involves interfacing with media, signals, bit streams that travel on the media, components that put signals on media, and various physical topologies. Layer 1 bits need structure so OSI Layer 2 frames are used. The MAC sublayer of Layer 2 determines the type of frame appropriate for the physical media.
The one thing common to all forms of Ethernet is the frame structure. This is what allows the interoperability of the different types of Ethernet.
Some of the fields permitted or required in an 802.3 Ethernet Frame are:
• Preamble
• Start Frame Delimiter
• Destination Address
• Source Address
• Length/Type
• Data and Pad
• Frame Check Sequence
In 10 Mbps and slower versions of Ethernet, the Preamble provides timing information the receiving node needs in order to interpret the electrical signals it is receiving. The Start Frame Delimiter marks the end of the timing information. 10 Mbps and slower versions of Ethernet are asynchronous. That is, they will use the preamble timing information to synchronize the receive circuit to the incoming data. 100 Mbps and higher speed implementations of Ethernet are synchronous. Synchronous means the timing information is not required, however for compatibility reasons the Preamble and SFD are present.
The address fields of the Ethernet frame contain Layer 2, or MAC, addresses.
All frames are susceptible to errors from a variety of sources. The Frame Check Sequence (FCS) field of an Ethernet frame contains a number that is calculated by the source node based on the data in the frame. At the destination it is recalculated and compared to determine that the data received is complete and error free.
Once the data is framed the Media Access Control (MAC) sublayer is also responsible to determine which computer on a shared-medium environment, or collision domain, is allowed to transmit the data. There are two broad categories of Media Access Control, deterministic (taking turns) and non-deterministic (first come, first served).
Examples of deterministic protocols include Token Ring and FDDI. The carrier sense multiple access with collision detection (CSMA/CD) access method is a simple non-deterministic system. The NIC listens for an absence of a signal on the media and starts transmitting. If two nodes or more nodes transmit at the same time a collision occurs. If a collision is detected the nodes wait a random amount of time and retransmit.
The minimum spacing between two non-colliding frames is also called the interframe spacing. Interframe spacing is required to insure that all stations have time to process the previous frame and prepare for the next frame.
Collisions can occur at various points during transmission. A collision where a signal is detected on the receive and transmit circuits at the same time is referred to as a local collision. A collision that occurs before the minimum number of bytes can be transmitted is called a remote collision. A collision that occurs after the first sixty-four octets of data have been sent is considered a late collision. The NIC will not automatically retransmit for this type of collision.
While local and remote collisions are considered to be a normal part of Ethernet operation, late collisions are considered to be an error. Ethernet errors result from detection of frames sizes that are longer or shorter than standards allow or excessively long or illegal transmissions called jabber. Runt is a slang term that refers to something less than the legal frame size.
Auto-Negotiation detects the speed and duplex mode, half-duplex or full-duplex, of the device on the other end of the wire and adjusts to match those settings.
Link establishment and full and half duplex
Link establishment and full and half duplex
6.2.10 This page will explain how links are established through Auto-Negotiation and introduce the two duplex modes.
Link partners are allowed to skip offering configurations of which they are capable. This allows the network administrator to force ports to a selected speed and duplex setting, without disabling Auto-Negotiation.
Auto-Negotiation is optional for most Ethernet implementations. Gigabit Ethernet requires its implementation, though the user may disable it. Auto-Negotiation was originally defined for UTP implementations of Ethernet and has been extended to work with other fiber optic implementations.
When an Auto-Negotiating station first attempts to link it is supposed to enable 100BASE-TX to attempt to immediately establish a link. If 100BASE-TX signaling is present, and the station supports 100BASE-TX, it will attempt to establish a link without negotiating. If either signaling produces a link or FLP bursts are received, the station will proceed with that technology. If a link partner does not offer an FLP burst, but instead offers NLPs, then that device is automatically assumed to be a 10BASE-T station. During this initial interval of testing for other technologies, the transmit path is sending FLP bursts. The standard does not permit parallel detection of any other technologies.
If a link is established through parallel detection, it is required to be half duplex. There are only two methods of achieving a full-duplex link. One method is through a completed cycle of Auto-Negotiation, and the other is to administratively force both link partners to full duplex. If one link partner is forced to full duplex, but the other partner attempts to Auto-Negotiate, then there is certain to be a duplex mismatch. This will result in collisions and errors on that link. Additionally if one end is forced to full duplex the other must also be forced. The exception to this is 10-Gigabit Ethernet, which does not support half duplex.
Many vendors implement hardware in such a way that it cycles through the various possible states. It transmits FLP bursts to Auto-Negotiate for a while, then it configures for Fast Ethernet, attempts to link for a while, and then just listens. Some vendors do not offer any transmitted attempt to link until the interface first hears an FLP burst or some other signaling scheme.
There are two duplex modes, half and full. For shared media, the half-duplex mode is mandatory. All coaxial implementations are half duplex in nature and cannot operate in full duplex. UTP and fiber implementations may be operated in half duplex. 10-Gbps implementations are specified for full duplex only.
In half duplex only one station may transmit at a time. For the coaxial implementations a second station transmitting will cause the signals to overlap and become corrupted. Since UTP and fiber generally transmit on separate pairs the signals have no opportunity to overlap and become corrupted. Ethernet has established arbitration rules for resolving conflicts arising from instances when more than one station attempts to transmit at the same time. Both stations in a point-to-point full-duplex link are permitted to transmit at any time, regardless of whether the other station is transmitting.
Auto-Negotiation avoids most situations where one station in a point-to-point link is transmitting under half-duplex rules and the other under full-duplex rules.
In the event that link partners are capable of sharing more than one common technology, refer to the list in Figure . This list is used to determine which technology should be chosen from the offered configurations.
Fiber-optic Ethernet implementations are not included in this priority resolution list because the interface electronics and optics do not permit easy reconfiguration between implementations. It is assumed that the interface configuration is fixed. If the two interfaces are able to Auto-Negotiate then they are already using the same Ethernet implementation. However, there remain a number of configuration choices such as the duplex setting, or which station will act as the Master for clocking purposes, that must be determined.
This page concludes this lesson. The next page will summarize the main points from the module.
6.2.10 This page will explain how links are established through Auto-Negotiation and introduce the two duplex modes.
Link partners are allowed to skip offering configurations of which they are capable. This allows the network administrator to force ports to a selected speed and duplex setting, without disabling Auto-Negotiation.
Auto-Negotiation is optional for most Ethernet implementations. Gigabit Ethernet requires its implementation, though the user may disable it. Auto-Negotiation was originally defined for UTP implementations of Ethernet and has been extended to work with other fiber optic implementations.
When an Auto-Negotiating station first attempts to link it is supposed to enable 100BASE-TX to attempt to immediately establish a link. If 100BASE-TX signaling is present, and the station supports 100BASE-TX, it will attempt to establish a link without negotiating. If either signaling produces a link or FLP bursts are received, the station will proceed with that technology. If a link partner does not offer an FLP burst, but instead offers NLPs, then that device is automatically assumed to be a 10BASE-T station. During this initial interval of testing for other technologies, the transmit path is sending FLP bursts. The standard does not permit parallel detection of any other technologies.
If a link is established through parallel detection, it is required to be half duplex. There are only two methods of achieving a full-duplex link. One method is through a completed cycle of Auto-Negotiation, and the other is to administratively force both link partners to full duplex. If one link partner is forced to full duplex, but the other partner attempts to Auto-Negotiate, then there is certain to be a duplex mismatch. This will result in collisions and errors on that link. Additionally if one end is forced to full duplex the other must also be forced. The exception to this is 10-Gigabit Ethernet, which does not support half duplex.
Many vendors implement hardware in such a way that it cycles through the various possible states. It transmits FLP bursts to Auto-Negotiate for a while, then it configures for Fast Ethernet, attempts to link for a while, and then just listens. Some vendors do not offer any transmitted attempt to link until the interface first hears an FLP burst or some other signaling scheme.
There are two duplex modes, half and full. For shared media, the half-duplex mode is mandatory. All coaxial implementations are half duplex in nature and cannot operate in full duplex. UTP and fiber implementations may be operated in half duplex. 10-Gbps implementations are specified for full duplex only.
In half duplex only one station may transmit at a time. For the coaxial implementations a second station transmitting will cause the signals to overlap and become corrupted. Since UTP and fiber generally transmit on separate pairs the signals have no opportunity to overlap and become corrupted. Ethernet has established arbitration rules for resolving conflicts arising from instances when more than one station attempts to transmit at the same time. Both stations in a point-to-point full-duplex link are permitted to transmit at any time, regardless of whether the other station is transmitting.
Auto-Negotiation avoids most situations where one station in a point-to-point link is transmitting under half-duplex rules and the other under full-duplex rules.
In the event that link partners are capable of sharing more than one common technology, refer to the list in Figure . This list is used to determine which technology should be chosen from the offered configurations.
Fiber-optic Ethernet implementations are not included in this priority resolution list because the interface electronics and optics do not permit easy reconfiguration between implementations. It is assumed that the interface configuration is fixed. If the two interfaces are able to Auto-Negotiate then they are already using the same Ethernet implementation. However, there remain a number of configuration choices such as the duplex setting, or which station will act as the Master for clocking purposes, that must be determined.
This page concludes this lesson. The next page will summarize the main points from the module.
Ethernet auto-negotiation
Ethernet auto-negotiation
6.2.9 This page explains auto-negotiation and how it is accomplished.
As Ethernet grew from 10 to 100 and 1000 Mbps, one requirement was to make each technology interoperable, even to the point that 10, 100, and 1000 interfaces could be directly connected. A process called Auto-Negotiation of speeds at half or full duplex was developed. Specifically, at the time that Fast Ethernet was introduced, the standard included a method of automatically configuring a given interface to match the speed and capabilities of the link partner. This process defines how two link partners may automatically negotiate a configuration offering the best common performance level. It has the additional advantage of only involving the lowest part of the physical layer.
10BASE-T required each station to transmit a link pulse about every 16 milliseconds, whenever the station was not engaged in transmitting a message. Auto-Negotiation adopted this signal and renamed it a Normal Link Pulse (NLP). When a series of NLPs are sent in a group for the purpose of Auto-Negotiation, the group is called a Fast Link Pulse (FLP) burst. Each FLP burst is sent at the same timing interval as an NLP, and is intended to allow older 10BASE-T devices to operate normally in the event they should receive an FLP burst.
Auto-Negotiation is accomplished by transmitting a burst of 10BASE-T Link Pulses from each of the two link partners. The burst communicates the capabilities of the transmitting station to its link partner. After both stations have interpreted what the other partner is offering, both switch to the highest performance common configuration and establish a link at that speed. If anything interrupts communications and the link is lost, the two link partners first attempt to link again at the last negotiated speed. If that fails, or if it has been too long since the link was lost, the Auto-Negotiation process starts over. The link may be lost due to external influences, such as a cable fault, or due to one of the partners issuing a reset.
The next page will discuss half and full duplex modes.
6.2.9 This page explains auto-negotiation and how it is accomplished.
As Ethernet grew from 10 to 100 and 1000 Mbps, one requirement was to make each technology interoperable, even to the point that 10, 100, and 1000 interfaces could be directly connected. A process called Auto-Negotiation of speeds at half or full duplex was developed. Specifically, at the time that Fast Ethernet was introduced, the standard included a method of automatically configuring a given interface to match the speed and capabilities of the link partner. This process defines how two link partners may automatically negotiate a configuration offering the best common performance level. It has the additional advantage of only involving the lowest part of the physical layer.
10BASE-T required each station to transmit a link pulse about every 16 milliseconds, whenever the station was not engaged in transmitting a message. Auto-Negotiation adopted this signal and renamed it a Normal Link Pulse (NLP). When a series of NLPs are sent in a group for the purpose of Auto-Negotiation, the group is called a Fast Link Pulse (FLP) burst. Each FLP burst is sent at the same timing interval as an NLP, and is intended to allow older 10BASE-T devices to operate normally in the event they should receive an FLP burst.
Auto-Negotiation is accomplished by transmitting a burst of 10BASE-T Link Pulses from each of the two link partners. The burst communicates the capabilities of the transmitting station to its link partner. After both stations have interpreted what the other partner is offering, both switch to the highest performance common configuration and establish a link at that speed. If anything interrupts communications and the link is lost, the two link partners first attempt to link again at the last negotiated speed. If that fails, or if it has been too long since the link was lost, the Auto-Negotiation process starts over. The link may be lost due to external influences, such as a cable fault, or due to one of the partners issuing a reset.
The next page will discuss half and full duplex modes.
FCS and beyond
FCS and beyond
6.2.8 This page will focus on additional errors that occur on an Ethernet network.
A received frame that has a bad Frame Check Sequence, also referred to as a checksum or CRC error, differs from the original transmission by at least one bit. In an FCS error frame the header information is probably correct, but the checksum calculated by the receiving station does not match the checksum appended to the end of the frame by the sending station. The frame is then discarded.
High numbers of FCS errors from a single station usually indicates a faulty NIC and/or faulty or corrupted software drivers, or a bad cable connecting that station to the network. If FCS errors are associated with many stations, they are generally traceable to bad cabling, a faulty version of the NIC driver, a faulty hub port, or induced noise in the cable system.
A message that does not end on an octet boundary is known as an alignment error. Instead of the correct number of binary bits forming complete octet groupings, there are additional bits left over (less than eight). Such a frame is truncated to the nearest octet boundary, and if the FCS checksum fails, then an alignment error is reported. This is often caused by bad software drivers, or a collision, and is frequently accompanied by a failure of the FCS checksum.
A frame with a valid value in the Length field but did not match the actual number of octets counted in the data field of the received frame is known as a range error. This error also appears when the length field value is less than the minimum legal unpadded size of the data field. A similar error, Out of Range, is reported when the value in the Length field indicates a data size that is too large to be legal.
Fluke Networks has coined the term ghost to mean energy (noise) detected on the cable that appears to be a frame, but is lacking a valid SFD. To qualify as a ghost, the frame must be at least 72 octets long, including the preamble. Otherwise, it is classified as a remote collision. Because of the peculiar nature of ghosts, it is important to note that test results are largely dependent upon where on the segment the measurement is made.
Ground loops and other wiring problems are usually the cause of ghosting. Most network monitoring tools do not recognize the existence of ghosts for the same reason that they do not recognize preamble collisions. The tools rely entirely on what the chipset tells them. Software-only protocol analyzers, many hardware-based protocol analyzers, hand held diagnostic tools, as well as most remote monitoring (RMON) probes do not report these events.
The next page will describe Auto-Negotiation.
6.2.8 This page will focus on additional errors that occur on an Ethernet network.
A received frame that has a bad Frame Check Sequence, also referred to as a checksum or CRC error, differs from the original transmission by at least one bit. In an FCS error frame the header information is probably correct, but the checksum calculated by the receiving station does not match the checksum appended to the end of the frame by the sending station. The frame is then discarded.
High numbers of FCS errors from a single station usually indicates a faulty NIC and/or faulty or corrupted software drivers, or a bad cable connecting that station to the network. If FCS errors are associated with many stations, they are generally traceable to bad cabling, a faulty version of the NIC driver, a faulty hub port, or induced noise in the cable system.
A message that does not end on an octet boundary is known as an alignment error. Instead of the correct number of binary bits forming complete octet groupings, there are additional bits left over (less than eight). Such a frame is truncated to the nearest octet boundary, and if the FCS checksum fails, then an alignment error is reported. This is often caused by bad software drivers, or a collision, and is frequently accompanied by a failure of the FCS checksum.
A frame with a valid value in the Length field but did not match the actual number of octets counted in the data field of the received frame is known as a range error. This error also appears when the length field value is less than the minimum legal unpadded size of the data field. A similar error, Out of Range, is reported when the value in the Length field indicates a data size that is too large to be legal.
Fluke Networks has coined the term ghost to mean energy (noise) detected on the cable that appears to be a frame, but is lacking a valid SFD. To qualify as a ghost, the frame must be at least 72 octets long, including the preamble. Otherwise, it is classified as a remote collision. Because of the peculiar nature of ghosts, it is important to note that test results are largely dependent upon where on the segment the measurement is made.
Ground loops and other wiring problems are usually the cause of ghosting. Most network monitoring tools do not recognize the existence of ghosts for the same reason that they do not recognize preamble collisions. The tools rely entirely on what the chipset tells them. Software-only protocol analyzers, many hardware-based protocol analyzers, hand held diagnostic tools, as well as most remote monitoring (RMON) probes do not report these events.
The next page will describe Auto-Negotiation.
Subscribe to:
Posts (Atom)
