Token Ring: Difference between revisions
Appearance
Content deleted Content added
m Reverted edits by 62.31.204.213 (talk) to last revision by 96.26.47.142 (HG) |
←Replaced content with 'Lies lies and guess what... more lies' Tag: blanking |
||
Line 1: | Line 1: | ||
Lies lies and guess what... more lies |
|||
{{IPstack}} |
|||
<!-- Edit image at Template:IPstack --> |
|||
[[image:token_ring.png|thumb|Two examples of token ring networks: a) Using a single [[Media Access Unit|MAU]] b) Using several MAUs connected to each other]] |
|||
[[image:TokenRingLogicalNetwork.svg|thumb|Token ring network]] |
|||
[[Image:Ibm 8228 mau.jpg|thumb|An IBM 8228 MAU.]] |
|||
'''Token ring''' [[local area network]] (LAN) technology is a local area network [[network protocol|protocol]] which resides at the [[data link layer]] (DLL) of the [[OSI model]]. It uses a special three-byte frame called a token that travels around the ring. Token ring frames travel completely around the loop. |
|||
==Description== |
|||
Stations on a token ring LAN are logically organized in a [[ring network|ring topology]] with data being transmitted sequentially from one ring station to the next with a control token circulating around the ring controlling access. This [[token passing]] mechanism is shared by [[ARCNET]], [[token bus]], and [[FDDI]], and has theoretical advantages over the [[stochastic]] [[CSMA/CD]] of Ethernet. |
|||
Physically, a token ring network is wired as a [[star network|star]], with 'hubs' and arms out to each station and the loop going out-and-back through each. |
|||
[[Image:IBM hermaphroditic connector.JPG|180px|thumb|left|IBM hermaphroditic connector with locking clip]] |
|||
Cabling is generally IBM "Type-1" [[Twisted pair#Shielded Twisted Pair .28STP.2|shielded twisted pair]], with unique [[Gender of connectors and fasteners#Genderless_connectors|hermaphroditic connectors]], commonly referred to as '''IBM data connectors'''. The connectors have the disadvantage of being quite bulky, requiring at least 3 x 3 cm panel space, and being relatively fragile. |
|||
Initially (in 1985) token ring ran at 4 [[Megabit per second|Mbit/s]], but in 1989 IBM introduced the first 16 Mbit/s token ring products and the 802.5 standard was extended to support this. In 1981, [[Apollo Computer]] introduced their proprietary 12 Mbit/s Apollo token ring (ATR) and [[Proteon]] introduced their 10 Mbit/s ProNet-10 token ring network in 1984. However, IBM token ring was not compatible with ATR or ProNet-10. |
|||
Each station passes or ''repeats'' the special token frame around the ring to its nearest downstream neighbor. This token-passing process is used to arbitrate access to the shared ring media. Stations that have data frames to transmit must first acquire the token before they can transmit them. Token ring LANs normally use [[differential Manchester encoding]] of bits on the LAN media. |
|||
IBM popularized the use of token ring LANs in the mid 1980s when it released its IBM token ring architecture based on active multi-station access units (MSAUs or MAUs) and the IBM Structured Cabling System. The Institute of Electrical and Electronics Engineers ([[IEEE]]) later standardized a token ring LAN system as IEEE 802.5.[http://www.ieee802.org/5/] |
|||
Token ring LAN speeds of 4 Mbit/s and 16 Mbit/s were standardized by the IEEE 802.5 working group. An increase to 100 Mbit/s was standardized and marketed during the wane of token ring's existence while a 1000 Mbit/s speed was actually approved in 2001, but no products were ever brought to market.<ref>[http://www.ieee802.org/5/www8025org/activity.html IEEE 802.5 activities]</ref> |
|||
When token ring LANs were first introduced at 4 Mbit/s, there were widely circulated claims that they were superior to [[Ethernet]],<ref>"IEEE 802.3 Local Area Network considerations", IBM document GG22-9422-0</ref> but these claims were fiercely debated.<ref name=Boggs1988>{{cite journal |
|||
| author = David R. Boggs, Jeffrey C. Mogul, Christopher A. Kent |
|||
| year = 1988 |
|||
| title = Measured capacity of an Ethernet: myths and reality |
|||
| journal = ACM SIGCOMM Computer Communication Review |
|||
| volume = 25 |
|||
| issue = 1 |
|||
| pages = 123–136 |
|||
| doi = 10.1145/205447.205460 |
|||
| url = http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-88-4.pdf |
|||
}}</ref><ref>[http://groups.google.com/group/comp.dcom.lans.misc/browse_thread/thread/17d6ef46a5162666/c875f342c33284ce?hl=en&q=ethernet+deterministic+%22token-ring%22#c875f342c33284ce USENET comp.dcom.lans.misc]</ref> |
|||
With the development of [[network switch|switched]] Ethernet and faster variants of Ethernet, token ring architectures lagged behind Ethernet, and the higher sales of Ethernet allowed [[economies of scale]] which drove down prices further, and added a compelling price advantage. |
|||
[[File:EISA TokenRing NIC.JPG|thumb|right|250px|Madge 4/16Mbps TokenRing ISA NIC.]] |
|||
[[File:EISA_Ethernet_NIC.JPG|right|thumb|Ethernet 10Base-5/2 ISA NIC.]] |
|||
Token ring networks have since declined in usage and the standards activity has since come to a standstill as 100Mbps switched Ethernet has dominated the LAN/layer 2 networking market. |
|||
==Token frame== |
|||
When no station is transmitting a data frame, a special token frame circles the loop. This special token frame is repeated from station to station until arriving at a station that needs to transmit data. When a station needs to transmit data, it converts the token frame into a data frame for transmission. Once the sending station receives its own data frame, it converts the frame back into a token. If a transmission error occurs and no token frame, or more than one, is present, a special station referred to as the ''Active Monitor'' detects the problem and removes and/or reinserts tokens as necessary (see [[Token_ring#Active_and_standby_monitors|Active and standby monitors]]). On 4 Mbit/s Token Ring, only one token may circulate; on 16 Mbit/s Token Ring, there may be multiple tokens. |
|||
The special token frame consists of three bytes as described below (J and K are special non-data characters, referred to as code violations). |
|||
==Token priority== |
|||
Token ring specifies an optional medium access scheme allowing a station with a high-priority transmission to request priority access to the token. |
|||
8 priority levels, 0-7, are used. When the station wishing to transmit receives a token or data frame with a priority less than or equal to the station's requested priority, it sets the priority bits to its desired priority. The station does not immediately transmit; the token circulates around the medium until it returns to the station. Upon sending and receiving its own data frame, the station downgrades the token priority back to the original priority. |
|||
==Token ring frame format== |
|||
A data token ring frame is an expanded version of the token frame that is used by stations to transmit [[media access control]] (MAC) management frames or data frames from upper layer protocols and applications. |
|||
Token Ring and IEEE 802.5 support two basic frame types: tokens and data/command frames. Tokens |
|||
are 3 bytes in length and consist of a start delimiter, an access control byte, and an end delimiter. |
|||
Data/command frames vary in size, depending on the size of the Information field. Data frames carry |
|||
information for upper-layer protocols, while command frames contain control information and have no |
|||
data for upper-layer protocols. Token ring can be connected to physical rings via equipment such as 100Base-TX equipment and CAT5e UTP cable. |
|||
===Data/Command Frame=== |
|||
{| class="wikitable" |
|||
|- |
|||
!SD |
|||
!AC |
|||
!FC |
|||
!DA |
|||
!SA |
|||
!PDU from LLC (IEEE 802.2) |
|||
!CRC |
|||
!ED |
|||
!FS |
|||
|- |
|||
|8 bits |
|||
|8 bits |
|||
|8 bits |
|||
|48 bits |
|||
|48 bits |
|||
|up to 18200x8 bits |
|||
|32 bits |
|||
|8 bits |
|||
|8 bits |
|||
|} |
|||
===Token Frame=== |
|||
{| class="wikitable" |
|||
|- |
|||
!SD |
|||
!AC |
|||
!ED |
|||
|- |
|||
|8 bits |
|||
|8 bits |
|||
|8 bits |
|||
|} |
|||
===Abort Frame=== |
|||
{| class="wikitable" |
|||
|- |
|||
!SD |
|||
!ED |
|||
|- |
|||
|8 bits |
|||
|8 bits |
|||
|} |
|||
; Starting Delimiter : consists of a special bit pattern denoting the beginning of the frame. The bits from most significant to least significant are J,K,0,J,K,0,0,0. J and K are code violations. Since [[Manchester encoding]] is self clocking, and has a transition for every encoded bit 0 or 1, the J and K codings violate this, and will be detected by the hardware. |
|||
{| class="wikitable" |
|||
|- |
|||
!J |
|||
!K |
|||
!0 |
|||
!J |
|||
!K |
|||
!0 |
|||
!0 |
|||
!0 |
|||
|- |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|} |
|||
; Access Control : this byte field consists of the following bits from most significant to least significant bit order: P,P,P,T,M,R,R,R. The P bits are priority bits, T is the token bit which when set specifies that this is a token frame, M is the monitor bit which is set by the Active Monitor (AM) station when it sees this frame, and R bits are reserved bits. |
|||
{| class="wikitable" style="text-align:center" |
|||
|- |
|||
! width="4%"|+ |
|||
! colspan="4" width="37.5%"| Bits 0–2 |
|||
! colspan="4" width="12.5%"| 3 |
|||
! colspan="8" width="37.5%"| 4 |
|||
! colspan="3" width="12.5%"| 5-7 |
|||
|- |
|||
! 0 |
|||
| colspan="4"| Priority |
|||
| colspan="4"| Token |
|||
| colspan="8"| Monitor |
|||
| colspan="16"| Reservation |
|||
|} |
|||
; Frame Control : a one byte field that contains bits describing the data portion of the frame contents.Indicates whether the frame contains data or control information. In control frames, this byte specifies the type of control information. |
|||
{| class="wikitable" style="text-align:center" |
|||
|- |
|||
! width="4%"|+ |
|||
! colspan="4" width="25%"| Bits 0–2 |
|||
! colspan="4" width="75%"| Bits 3-7 |
|||
|- |
|||
! 0 |
|||
| colspan="4"| Frame type |
|||
| colspan="4"| Control Bits |
|||
|} |
|||
Frame type - '''01''' indicates LLC frame IEEE 802.2 (data) and ignore control bits |
|||
'''00''' indicates MAC frame and control bits indicate the type of [[Media Access Control|MAC]] control frame |
|||
; Destination address : a six byte field used to specify the destination(s) physical address . |
|||
; Source address :Contains physical addressa of sending station . It is six byte field that is either the local assigned address (LAA) or universally assigned address (UAA) of the sending station adapter. |
|||
; Data : a variable length field of 0 or more bytes, the maximum allowable size depending on ring speed containing MAC management data or upper layer information.Maximum length of 4500 bytes |
|||
; Frame Check Sequence : a four byte field used to store the calculation of a CRC for frame integrity verification by the receiver. |
|||
; Ending Delimiter : The counterpart to the starting delimiter, this field marks the end of the frame and consists of the following bits from most significant to least significant: J,K,1,J,K,1,I,E. I is the intermediate frame bit and E is the error bit. |
|||
{| class="wikitable" |
|||
|- |
|||
!J |
|||
!K |
|||
!1 |
|||
!J |
|||
!K |
|||
!1 |
|||
!I |
|||
!E |
|||
|- |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|} |
|||
; Frame Status : a one byte field used as a primitive acknowledgement scheme on whether the frame was recognized and copied by its intended receiver. |
|||
{| class="wikitable" |
|||
|- |
|||
!A |
|||
!C |
|||
!0 |
|||
!0 |
|||
!A |
|||
!C |
|||
!0 |
|||
!0 |
|||
|- |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|1 bit |
|||
|} |
|||
'''A''' = 1 , Address recognized |
|||
'''C''' = 1 , Frame copied |
|||
; Abort Frame : |
|||
Used to abort transmission by the sending station |
|||
==Active and standby monitors== |
|||
Every station in a token ring network is either an active monitor (AM) or standby monitor (SM) station. |
|||
However, there can be only one active monitor on a ring at a time. |
|||
The active monitor is chosen through an election or ''monitor contention'' process. |
|||
The monitor contention process is initiated when |
|||
* a loss of signal on the ring is detected. |
|||
* an active monitor station is not detected by other stations on the ring. |
|||
* when a particular timer on an end station expires such as the case when a station hasn't seen a token frame in the past 7 seconds. |
|||
When any of the above conditions take place and a station decides that a new monitor is needed, it will transmit a "claim token" frame, announcing that it wants to become the new monitor. If that token returns back to the sender, it is OK for it to become the monitor. If some other station tries to become the monitor at the same time then the station with the highest [[MAC address]] will win the election process. Every other station becomes a standby monitor. All stations must be capable of becoming an active monitor station if necessary. |
|||
The active monitor performs a number of ring administration functions. The first function is to operate as the master clock for the ring in order to provide synchronization of the signal for stations on the wire. Another function of the AM is to insert a 24-bit delay into the ring, to ensure that there is always sufficient buffering in the ring for the token to circulate. A third function for the AM is to ensure that exactly one token circulates whenever there is no frame being transmitted, and to detect a broken ring. Lastly, the AM is responsible for removing circulating frames from the ring. |
|||
==Token ring insertion process== |
|||
Token ring stations must go through a 5-phase ring insertion process before being allowed to participate in the ring network. If any of these phases fail, the token ring station will not ''insert'' into the ring and the token ring driver may report an error. |
|||
* Phase 0 (Lobe Check) — A station first performs a lobe media check. A station is ''wrapped'' at the MSAU and is able to send 2000 test frames down its transmit pair which will loop back to its receive pair. The station checks to ensure it can receive these frames without error. |
|||
* Phase 1 (Physical Insertion) — A station then sends a 5 volt signal to the MSAU to open the relay. |
|||
* Phase 2 (Address Verification) — A station then transmits MAC frames with its own MAC address in the destination address field of a token ring frame. When the frame returns and if the address copied , the station must participate in the periodic (every 7 seconds) ring poll process. This is where stations identify themselves on the network as part of the MAC management functions. |
|||
* Phase 3 (Participation in ring poll) — A station learns the address of its Nearest Active Upstream Neighbour (NAUN) and makes its address known to its nearest downstream neighbour, leading to the creation of the ring map. Station waits until it receives an AMP or SMP frame with the ARI and FCI bits set to 0. When it does, the station flips both bits (ARI and FCI) to 1, if enough resources are available, and queues an SMP frame for transmission. If no such frames are received within 18 seconds, then the station reports a failure to open and de-inserts from the ring. If the station successfully participates in a ring poll, it proceeds into the final phase of insertion, request initialization. |
|||
* Phase 4 (Request Initialization) — Finally a station sends out a special request to a parameter server to obtain configuration information. This frame is sent to a special functional address, typically a token ring bridge, which may hold timer and ring number information with which to tell the new station about. |
|||
==See also== |
|||
{{Commons category|Token ring}} |
|||
* [[Cambridge Ring]] |
|||
* [[List of device bandwidths]] |
|||
==Notes== |
|||
<references/> |
|||
==References== |
|||
* {{cite book |
|||
| title = Network Consultants Handbook |
|||
| first = Matthew |
|||
| last = Castelli |
|||
| publisher = Cisco Press |
|||
| year = 2002 |
|||
| isbn = 1-58705-039-0 |
|||
}} |
|||
* {{cite book |
|||
| title = Networking Explained |
|||
| first = Michael |
|||
| last = Gallo |
|||
| coauthors = Hancock, William M. |
|||
| publisher = Digital Press |
|||
| year = 2001 |
|||
| isbn = 1-55558-252-4 |
|||
}} |
|||
== External links== |
|||
* [http://www.ieee802.org/5/ IEEE 802.5 Web Site] |
|||
* [http://standards.ieee.org/getieee802/802.5.html Get the IEEE 802.5 standard] |
|||
* [http://www.cisco.com/en/US/products/hw/modules/ps2643/products_tech_note09186a0080093dc2.shtml#first Troubleshooting Cisco Router Token Ring Interfaces] |
|||
* [http://futureobservatory.dyndns.org/9056.htm#LANs Futureobservatory.org discussion of IBM's failure in token ring technology] |
|||
{{Channel access methods}} |
|||
{{IEEE standards}} |
|||
[[Category:Network topology]] |
|||
[[Category:Local area networks]] |
|||
[[Category:IEEE 802]] |
|||
[[Category:IBM computers|Token ring]] |
|||
[[Category:IBM PC compatibles]] |
|||
[[Category:IEEE standards]] |
|||
[[Category:Serial buses]] |
|||
[[az:Token Ring]] |
|||
[[bn:টোকেন রিং]] |
|||
[[bs:Token Ring]] |
|||
[[bg:Token ring]] |
|||
[[cs:Token ring]] |
|||
[[de:Token Ring]] |
|||
[[et:Lubaringvõrk]] |
|||
[[el:Token ring]] |
|||
[[es:Token Ring]] |
|||
[[eu:Token Ring]] |
|||
[[fr:Anneau à jeton]] |
|||
[[ko:토큰링]] |
|||
[[id:Token Ring]] |
|||
[[it:Token ring]] |
|||
[[he:Token ring]] |
|||
[[hu:Token-Ring]] |
|||
[[ms:Gelang token]] |
|||
[[nl:Token Ring]] |
|||
[[ja:トークンリング]] |
|||
[[pl:Token ring]] |
|||
[[pt:Token ring]] |
|||
[[ru:Token ring]] |
|||
[[sk:Token ring]] |
|||
[[sl:Token ring]] |
|||
[[fi:Token Ring]] |
|||
[[sv:IEEE 802.5]] |
|||
[[tr:Token ring]] |
|||
[[uk:Token ring]] |
|||
[[vi:Token ring]] |
|||
[[zh:令牌环]] |
Revision as of 12:57, 26 May 2010
Lies lies and guess what... more lies