Token ring

Two examples of token ring networks: a) Using a single MAU b) Using several MAUs connected to each other
Token ring network
IBM hermaphroditic connector with locking clip

Token ring local area network (LAN) technology is a communications protocol for local area networks. It uses a special three-byte frame called a "token" that travels around a logical "ring" of workstations or servers. This token passing is a channel access method providing fair access for all stations, and eliminating the collisions of contention-based access methods.

Introduced by IBM in 1984, it was then standardized with protocol IEEE 802.5 and was fairly successful, particularly in corporate environments, but gradually eclipsed by the later versions of Ethernet.

(The main focus of this article is the IBM/IEEE 802.5 version, but there were several other earlier implementations of token rings).

History

A wide range of different local area network technologies were developed in the early 1970s, of which one, the Cambridge Ring had demonstrated the potential of a token passing ring topology.

At the IBM Zurich Research Laboratory Werner Bux and Hans Müller in particular worked on the design and development of IBM's token ring technology.[1]

Early work at MIT[2] led to the 1981, Proteon 10 Mbit/s ProNet-10 token ring network.[3] Proteon later evolved a 16 Mbit/s version that ran on unshielded twisted pair cable (although in the days before UTP cable standards had been developed, the choice of cable definitely mattered).

In 1981, workstation vendor Apollo Computer introduced their proprietary 12 Mbit/s Apollo token ring (ATR) network running over 75 ohm RG-6U coaxial cabling.

On October 15, 1985, IBM launched their own proprietary IBM Token Ring products.[4] It ran at 4 Mbit/s, and attachment was possible from IBM PCs, midrange computers and mainframes. It used a convenient star-wired physical topology, and ran over shielded twisted-pair cabling - and shortly became the basis for the (ANSI)/IEEE standard 802.5.[5]

In 1988 the faster 16 Mbit/s token ring was standardized by the 802.5 working group.[6]

During this time, IBM argued strongly that token ring LANs were superior to Ethernet, especially under load,[7] but these claims were fiercely debated.[8]

Although an increase to 100 Mbit/s was standardized and marketed during the wane of token ring's existence, it was never widely used, ("IBM does not view high-speed token ring as a requirement for the majority of its customers, and therefore the decision has been made not to provide 100 Mbps high-speed token ring uplinks on its products..."),[9] and while a 1000 Mbit/s was approved in 2001, no products were ever brought to market,[10] and standards activity came to a standstill as Fast Ethernet and Gigabit Ethernet dominated the local area networking market.

Comparison with Ethernet

Ethernet and Token ring have some notable differences:

Operation

Stations on a token ring LAN are logically organized in a ring topology with data being transmitted sequentially from one ring station to the next with a control token circulating around the ring controlling access. Similar token passing mechanisms are used by ARCNET, token bus, 100VG-AnyLAN (802.12) and FDDI, and they have theoretical advantages over the CSMA/CD of early Ethernet.

A token ring network can be modelled as a polling system where a single server provides service to queues in a cyclic order.[14]

Access control

The data transmission process goes as follows:

Multistation Access Units and Controlled Access Units

Main article: Media Access Unit
The IBM 8228 Multistation Access Unit with accompanying Setup Aid to prime the relays on each port

Physically, a token ring network is wired as a star, with 'MAUs' in the center, 'arms' out to each station, and the loop going out-and-back through each.[15]

A MAU could present in the form of a hub or a switch; since token ring had no collisions many MAUs were manufactured as hubs. Although Token Ring runs on LLC, it includes Source Routing [16] to forward packets beyond the local network. The majority of MAUs are configured in a 'concentration' configuration by default, but later MAUs also supporting a feature to act as splitters and not concentrators exclusively such as on the IBM 8226.[17]

MAUs operating as either concentrators or splitters.

Later IBM would release Controlled Access Units that could support multiple MAU modules known as a Lobe Attachment Module. The CAUs supported features such as Dual-Ring Redundancy for alternate routing in the event of a dead port, modular concentration with LAMs, and multiple interfaces like most later MAUs.[18] This offered a more reliable setup and remote management than with an unmanaged MAU hub.

Cabling and interfaces

Cabling is generally IBM "Type-1", a heavy two-pair 150 Ohm shielded twisted pair cable. This was the basic cable for the "IBM Cabling System", a structured cabling system that IBM hoped would be widely adopted. Unique hermaphroditic connectors, commonly referred to as IBM Data Connectors in formal writing or colloquially as Boy George connectors were used.[19] The connectors have the disadvantage of being quite bulky, requiring at least 3 x 3 cm panel space, and being relatively fragile. The advantages of the connectors being that they are genderless and have superior shielding over standard unshielded RJ45. Connectors at the computer were usually DE-9 female.

In later implementations of Token Ring, Cat 6 cabling was also supported, so RJ45 connectors were used on both of the MAUs, CAUs and NICs; with many of the network cards supporting both RJ45 and DE-9 for backwards compatibility.[15]

Frame types

Token

When no station is sending a 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 send data.

Tokens are 3 bytes in length and consist of a start delimiter, an access control byte, and an end delimiter.

Start Delimiter Access Control End Delimiter
8-bits 8-bits 8-bits

Abort frame

Used to abort transmission by the sending station

SD ED
8 bits 8 bits

Data

Data frames carry information for upper-layer protocols, while command frames contain control information and have no data for upper-layer protocols. Data/command frames vary in size, depending on the size of the Information field.

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 4500x8 bits 32 bits 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. Both the Starting Delimiter and Ending Delimiter fields are used to mark frame boundaries.
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.
+ Bits 0–2 3 4 5–7
0 Priority Token Monitor Reservation
Frame control 
A one byte field that contains bits describing the data portion of the frame contents which indicates whether the frame contains data or control information. In control frames, this byte specifies the type of control information.
+ Bits 0–1 Bits 2–7
0 Frame type 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 MAC control frame

Destination address 
A six byte field used to specify the destination(s) physical address.
Source address 
Contains physical address 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.
J K 1 J K 1 I E
1 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.
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

Other technical details

Active and standby monitors

Every station in a token ring network is either an active monitor (AM) or standby monitor (SM) station. 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

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

Optional priority scheme

In some applications there is an advantage to being able to designate one station having a higher priority. Token ring specifies an optional scheme of this sort, as does the CAN Bus, (widely used in automotive applications) - but Ethernet does not.

In the Token ring priority MAC, 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.

Here are the following 8 access priority and traffic types for devices that support 802.1Q and 802.1p:

Priority bits Traffic type
x'000' Normal data traffic
x'001' Not used
x'010' Not used
x'011' Not used
x'100' Normal data traffic (forwarded from other devices)
x'101' Data sent with time sensitivity requirements
x'110' Data with real time sensitivity (i.e. VoIP)
x'111' Station management

Bridging Token ring and Ethernet

Both Token ring and Ethernet interfaces on the 2210-24M

Bridging solutions for Token ring and Ethernet networks included the AT&T StarWAN 10:4 Bridge, the IBM 9208 LAN Bridge and the Microcom LAN Bridge. [20] Alternative connection solutions incorporated a router that could be configured to dynamically filter traffic, protocols and interfaces, such as the IBM 2210-24M Multiprotocol Router which contained both Ethernet and token ring interfaces.[21]

See also

References

  1. "IEEE honors Zurich LAN pioneers", Zurich, Switzerland, 14 April 2003
  2. "Early Token Ring Work at MIT", J. Noel Chiappa, ieeexplore.ieee.org
  3. "A History of Computer Communications 1968-1988", James Pelkey
  4. "Local Area Networks", InfoWorld 24 Mar 1986
  5. IEEE Standards: P802.5 Working Group Area. Ieee802.org. Retrieved on 2011-10-30.
  6. "ETHERNET VS. TOKEN RING IN THE LOCAL AREA NETWORKING BUSINESS", URS VON BURG AND MARTIN KENNY, Industry and Innovation, Volume 10, Number 4, 351–375, December 2003
  7. "IEEE 802.3 Local Area Network considerations", IBM document GG22-9422-0
  8. David R. Boggs, Jeffrey C. Mogul, Christopher A. Kent (1988). "Measured capacity of an Ethernet: myths and reality" (PDF). ACM SIGCOMM Computer Communication Review 25 (1): 123–136. doi:10.1145/205447.205460.
  9. 1 2 http://www.redbooks.ibm.com/redpapers/pdfs/redp0031.pdf
  10. IEEE 802.5 activities. Ieee802.org. Retrieved on 2011-10-30.
  11. http://ps-2.kev009.com/ohlandl/NIC/8228.html#DirectCable
  12. http://www.zen22142.zen.co.uk/Circuits/Interface/pethhub.htm
  13. http://serverfault.com/questions/462178/duplicate-mac-address-on-the-same-lan-possible
  14. Bux, W. (1989). "Token-ring local-area networks and their performance". Proceedings of the IEEE 77 (2): 238. doi:10.1109/5.18625.
  15. 1 2 ftp://ps-2.kev009.com/incoming/timc/PDFS/IBM/Networking/IBM_C_TR.pdf
  16. it:Source routing (token ring)
  17. http://ps-2.kev009.com/ohlandl/NIC/8226.html
  18. ftp://public.dhe.ibm.com/networking/nswww/neteam/998pg/c823003.pdf
  19. "Local Area Networks - Token Ring". Scottsnetworkclass.com. Retrieved 2013-06-15.
  20. https://books.google.ca/books?id=wRIEAAAAMBAJ&pg=PA56&lpg=PA56&dq=token+ring+ethernet+bridge&source=bl&ots=dEdPHBSSoT&sig=5VrPt6GBDY5k3JwccF7Fccg9f_A&hl=en&sa=X&ei=vSYOVZ2VD8S0sATKt4HABg&redir_esc=y#v=onepage&q=token%20ring%20ethernet%20bridge&f=false
  21. http://ps-2.kev009.com/basil.holloway/ALL%20PDF/sg244446.pdf

External links

Wikimedia Commons has media related to Token ring.
This article is issued from Wikipedia - version of the Tuesday, April 19, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.