Token Ring Explained

Token Ring is a physical and data link layer computer networking technology used to build local area networks. It was introduced by IBM in 1984, and standardized in 1989 as IEEE 802.5. It uses a special three-byte frame called a token that is passed 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.

Token Ring was a successful technology, particularly in corporate environments, but was gradually eclipsed by the later versions of Ethernet. Gigabit Token Ring was standardized in 2001, but development has stopped since.[1]

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, and many teams worldwide began working on their own implementations. 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,[2] while early work at MIT[3] led to the Proteon 10 Mbit/s ProNet-10 Token Ring network in 1981[4] the same year that workstation vendor Apollo Computer introduced their proprietary 12 Mbit/s Apollo Token Ring (ATR) network running over 75-ohm RG-6U coaxial cabling. Proteon later evolved a 16 Mbit/s version that ran on unshielded twisted pair cable.

1985 IBM launch

IBM launched their own proprietary Token Ring product on October 15, 1985.[5] [6] It ran at 4 Mbit/s,[7] 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. Shortly thereafter it became the basis for the IEEE 802.5 standard.[8]

During this time, IBM argued that Token Ring LANs were superior to Ethernet, especially under load,[9] but these claims were debated.[10]

In 1988, the faster 16 Mbit/s Token Ring was standardized by the 802.5 working group.[11] An increase to 100 Mbit/s was standardized and marketed during the wane of Token Ring's existence and was never widely used.[12] While a 1000 Mbit/s standard was approved in 2001, no products were ever brought to market and standards activity came to a standstill[13] as Fast Ethernet and Gigabit Ethernet dominated the local area networking market.

Gallery

Comparison with Ethernet

Early Ethernet and Token Ring both used a shared transmission medium. They differed in their channel access methods. These differences have become immaterial, as modern Ethernet networks consist of switches and point-to-point links operating in full-duplex mode.

Token Ring and legacy Ethernet 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.[18]

A Token Ring network can be modeled as a polling system where a single server provides service to queues in a cyclic order.[19]

Access control

The data transmission process goes as follows:

Multistation Access Units and Controlled Access Units

See main article: Media Access Unit. 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.[20]

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

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.[22] 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, referred to as IBM Data Connectors in formal writing or colloquially as Boy George connectors, were used.[23] The connectors have the disadvantage of being quite bulky, requiring at least 3cm×3cmcm (01inches×01inchescm) panel space, and being relatively fragile. The advantages of the connectors being that they are genderless and have superior shielding over standard unshielded 8P8C. Connectors at the computer were usually DE-9 female. Several other types of cable existed such as type 2, and type 3 cable.[24]

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

Technical details

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 three octets in length and consist of a start delimiter, an access control octet, and an end delimiter.

Abort frame

Used by the sending station to abort transmission.

Data

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

Starting delimiter – The 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.
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.
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.

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 a 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.
  • Frame status – A one-byte field used as a primitive acknowledgment scheme on whether the frame was recognized and copied by its intended receiver.

    A = 1, Address recognizedC = 1, Frame copied

    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 the following happens:

    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 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, eight 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 eight 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

    Interconnection with Ethernet

    Bridging solutions for Token Ring and Ethernet networks included the AT&T StarWAN 10:4 Bridge,[25] the IBM 8209 LAN Bridge and the Microcom LAN Bridge. 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.[26]

    Operating system support

    In 2012, David S. Miller merged a patch to remove token ring networking support from the Linux kernel.[27]

    See also

    References

    General

    External links

    Notes and References

    1. Web site: IEEE 802.5 Activities . ieee802.org . IEEE . 29 October 2023.
    2. IEEE honors Zurich LAN pioneers . . Zurich, Switzerland . 14 April 2003.
    3. Early Token Ring Work at MIT . J. Noel Chiappa . Noel Chiappa . . 36 . 2 . April–June 2014 . 80–85 . 10.1109/MAHC.2014.14. 30761524 . free .
    4. Web site: 14.18 Proteon in Chapter 14 - Internetworking: Emergence 1985-1988 . The History of Computer Communications . James . Pelkey.
    5. Web site: 1985-10-15. IBM TOKEN-RING NETWORK. 2021-03-11. IBM.
    6. Major Vendors Differ On Network Approach . Don . Crabb . . 8 . 12 . 24 March 1986 . 27.
    7. Web site: InfoWorld . 21 November 1988 .
    8. http://www.ieee802.org/5/ IEEE Standards: P802.5 Working Group Area
    9. Book: IEEE 802.3 Local Area Network considerations . . GG22-9422-0.
    10. David R. Boggs . Jeffrey C. Mogul . Christopher A. Kent . 1988 . Measured capacity of an Ethernet: myths and reality . ACM SIGCOMM Computer Communication Review . 25 . 1 . 123–136 . 10.1145/205447.205460 . 52820607 . 2007-12-04 . 2012-03-02 . https://web.archive.org/web/20120302125906/http://www.hpl.hp.com/techreports/Compaq-DEC/WRL-88-4.pdf . dead .
    11. Sponsers, Communities, and Standards: Ethernet vs. Token Ring In The Local Area Networking Business . https://web.archive.org/web/20180219041820/http://hcd.ucdavis.edu/faculty/webpages/kenney/articles_files/Sponsors,%20Communities,%20and%20Standards_%20Ethernet%20vs.%20Token%20Ring%20in%20the%20Local%20Area%20Networking%20Business.pdf . 2018-02-19 . dead . Urs Von Burg . Martin Kenny . Industry and Innovation . 10 . 4 . 351–375 . December 2003 . 10.1080/1366271032000163621 . Taylor & Francis Ltd. 153804163 .
    12. White paper . Jonathan Follows . Token Ring Solutions . https://web.archive.org/web/20160806170758/http://www.redbooks.ibm.com/redpapers/pdfs/redp0031.pdf . 2016-08-06 . 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... . IBMInternational Technical Support Organization . 2000.
    13. Web site: IEEE 802.5 activities . IEEE 802 LAN/MAN Standards Committee . 2023-05-09.
    14. Web site: Louis Ohland . 8228 Multistation Access Unit . Ps-2.kev009.com . 2016-08-03 . https://web.archive.org/web/20180328113319/http://ps-2.kev009.com/ohlandl/NIC/8228.html#DirectCable . 2018-03-28 . deviated.
    15. Web site: What is the difference between an Ethernet hub and switch? . 10 May 2016 . 14 March 2017 . https://web.archive.org/web/20170314024014/http://www.duxcw.com/faq/network/hubsw.htm . dead .
    16. Web site: A Passive Ethernet Hub . Zen22142.zen.co.uk . 2016-08-03 . https://web.archive.org/web/20160824011107/http://www.zen22142.zen.co.uk/Circuits/Interface/pethhub.htm . 2016-08-24 . dead.
    17. Web site: networking - Duplicate MAC address on the same LAN possible? . Server Fault . 2013-01-03 . 2016-08-03.
    18. Web site: Does anyone actually still USE Token Ring? . John . Sheesley . April 2, 2008 . . https://web.archive.org/web/20131009032029/https://www.techrepublic.com/blog/classics-rock/does-anyone-actually-still-use-token-ring/ . 2013-10-09 . dead.
    19. Bux . W. . Token-ring local-area networks and their performance . 10.1109/5.18625 . Proceedings of the IEEE. 77 . 2 . 238 . 1989 .
    20. Web site: [ftp://ps-2.kev009.com/incoming/timc/PDFS/IBM/Networking/IBM_C_TR.pdf Why buy from IBM? ]. . 2016-08-03 . https://web.archive.org/web/20200616170856/ftp://ps-2.kev009.com/incoming/timc/PDFS/IBM/Networking/IBM_C_TR.pdf . 2020-06-16 . live.
    21. Web site: Louis Ohland . 8226 TR RJ45 Connection /Model 001 . Ardent Tool of Capitalism . 2023-05-09.
    22. Web site: IBM 8230 Controlled access Unit . Public.dhe.ibm.com . 2016-08-03 . https://web.archive.org/web/20200616164253/http://public.dhe.ibm.com/networking/nswww/neteam/998pg/c823003.pdf . 2020-06-16 . dead.
    23. Web site: Local Area Networks - Token Ring . Scottsnetworkclass.com . 2013-06-15 . https://web.archive.org/web/20130801102601/http://www.scottsnetworkclass.com/Ether_Token/Token_3.html . 2013-08-01 . dead.
    24. Web site: Network World . 25 April 1988 .
    25. Buying Smart . Edwin . Mier . . 8 . 21 . 56 . 1991-06-03 . 2016-08-03. IDG Network World Inc .
    26. Book: IBM 2210 Nways Multiprotocol Router Description and Configuration Scenarios - Volume I . Third . SG24-4446-02 . June 1997 . IBM International Technical Support Organization Raleigh Center . 2016-08-03.
    27. Web site: Corbet . Jonathan . The end of the token ring era? . 2023-09-22 . LWN.net.