Dead End: Token Ring

Zusammenfassung

IBM’s Token Ring was, by several technical measures, a superior network technology to Ethernet. It used a deterministic access protocol that guaranteed every device a turn to transmit, eliminated collisions that could degrade Ethernet performance under load, and at 16 Mbps outpaced Ethernet’s 10 Mbps. IBM pushed Token Ring as the 802.5 IEEE standard and made it the default networking technology for its own products throughout the late 1980s and early 1990s. Token Ring lost anyway — to cheaper cable, simpler equipment, and the switch from shared to switched Ethernet that eliminated Token Ring’s theoretical advantage at high utilization. IBM discontinued Token Ring products in 2001. The story of Token Ring is about how technical superiority in one dimension is frequently outweighed by the economic forces that determine what actually gets deployed.

The Token Ring Architecture

Token Ring was developed by IBM in the late 1970s and early 1980s, with the key patent credited to Olof Soderblom. The core idea was a token-passing protocol: a special control frame called a token circulated continuously around a ring of computers. A device that wanted to transmit had to first capture the token, then transmit its data, then release the token for the next device.

This architecture had important properties. It was deterministic: the maximum time any device would wait to transmit could be calculated. Under Ethernet’s CSMA/CD protocol, devices listened for a clear channel and transmitted opportunistically; if two transmitted simultaneously, there was a collision and both had to retry. Under high network load, collisions became frequent and Ethernet throughput degraded. Token Ring never had collisions. Every device knew its position in the ring and knew the token would arrive.

It was also fair: the token circulated through every device in sequence. No device could monopolize the network, and every device had a bounded wait time. This made Token Ring predictable in a way that mattered for time-sensitive applications — factory automation, process control, environments where a missed deadline had real consequences.

Error detection was built into the protocol. If a device failed to release the token after transmitting, an Active Monitor device on the ring detected the lost token and generated a new one. The ring could recover from single node failures without manual intervention.

IBM’s first commercial Token Ring specification ran at 4 Mbps. In 1989, IBM introduced 16 Mbps Token Ring, which added Early Token Release — a device could release the token immediately after transmitting rather than waiting for its data to arrive back at the source, significantly improving throughput under load.

The Hub Problem

Token Ring’s physical implementation required a Multistation Access Unit (MAU) — IBM’s term for what Ethernet called a hub. The MAU was the central point through which all devices connected. Each device ran a cable to the MAU; the MAU internally connected the cables in a ring sequence.

The MAU was expensive — significantly more expensive than an Ethernet hub. In the early 1990s, a 16-port Token Ring MAU from IBM cost approximately $1,000–$2,000. A comparable 16-port Ethernet hub cost $200–$400. Network Interface Cards (NICs) showed the same disparity: Token Ring NICs cost $300–$600; Ethernet NICs cost $50–$100.

The cable requirements compounded the cost. IBM’s original Token Ring specification required shielded twisted pair (STP) cable — heavier, more expensive, and harder to install than the unshielded twisted pair (UTP) that Ethernet’s 10BASE-T standard (finalized 1990) used. A Token Ring installation in a large office building required specialized cable installers, specific STP connectors, and careful attention to cable run length. Ethernet UTP installations used the same RJ-45 connectors that telephone systems used, in cable that building contractors could install without specialized networking training.

The IBM PC adapter for Token Ring — sold as the IBM Token Ring Network Adapter — carried IBM’s premium pricing. Organizations buying IBM PS/2 computers and IBM-branded networking were paying IBM prices throughout. This was IBM’s strategy: Token Ring was profitable hardware. Ethernet was a commodity where margins had collapsed.

The IEEE 802.5 Political Battle

During the early 1980s, both Token Ring and Ethernet were competing to be adopted as the IEEE networking standard. The IEEE 802 committee that covered local area networks created working groups for different technologies: 802.3 for Ethernet (CSMA/CD), 802.4 for Token Bus (a token-passing protocol used in factory automation), and 802.5 for Token Ring.

IBM lobbied aggressively for Token Ring adoption. The company had significant influence within IEEE, large corporate customers who trusted IBM’s networking recommendations, and a history of setting de facto standards (SNA, EBCDIC, 3270 terminals) within its customer base. IBM’s position was that Token Ring’s deterministic behavior made it technically superior, and that organizations with serious networking needs should adopt the superior standard.

Ethernet’s advocates — led by Digital Equipment Corporation, Intel, and Xerox (the original Ethernet developers) — argued that Ethernet’s lower cost and simpler implementation would accelerate adoption. The IEEE adopted both 802.3 (Ethernet) and 802.5 (Token Ring) as standards. The market then determined which would dominate.

IBM’s mainframe and minicomputer customers, who trusted IBM’s networking recommendations and bought IBM hardware, adopted Token Ring. Organizations without a strong IBM relationship, organizations in price-sensitive environments, and organizations that found Token Ring’s installation complexity onerous adopted Ethernet. The installed base split roughly along IBM customer alignment through the late 1980s.

10BASE-T and the Turning Point

The pivotal year for Token Ring’s decline was 1990, when the IEEE ratified 10BASE-T — Ethernet over unshielded twisted pair cable. Before 10BASE-T, Ethernet ran on coaxial cable (10BASE-5, “thick Ethernet,” and 10BASE-2, “thin Ethernet” or “cheapernet”). Coaxial cable required connecting devices in a bus topology, and a break anywhere in the cable segment could bring down the entire network. It was also harder to install in buildings with existing telephone wiring.

10BASE-T brought Ethernet to the same star topology Token Ring used — each device connected by its own cable to a central hub — while using the cheaper, thinner unshielded twisted pair cable that was already installed in most office buildings for telephone use. An organization that had existing UTP telephone cable could add Ethernet by installing hubs and NICs, often reusing cable runs they already had.

The cost gap between Token Ring and Ethernet, which had already existed, widened dramatically with 10BASE-T. The scale economics of Ethernet’s larger installed base meant NIC prices fell faster. By 1992, Ethernet NICs were available from third-party manufacturers for under $100. Token Ring NICs remained $200–$400.

The Switched Ethernet Solution

Token Ring’s primary technical argument — deterministic access that prevented performance degradation under high load — was addressed by switched Ethernet technology that emerged in the early 1990s.

Ethernet switches replaced shared hubs. In a shared Ethernet hub, all devices on the segment competed for the same bandwidth. A collision on any device affected all devices on the segment. In an Ethernet switch, each port was an independent collision domain — the switch examined the destination MAC address of incoming frames and forwarded them only to the appropriate port. Two devices connected to a switch could transmit simultaneously without interference.

Switched Ethernet effectively eliminated the shared-medium collision problem that had been Token Ring’s strongest argument. With each device on its own switched port, the network behaved like dedicated point-to-point connections between each device and the switch. Token Ring’s deterministic access advantage over shared Ethernet became irrelevant because switched Ethernet no longer shared access.

100BASE-TX (Fast Ethernet), ratified as IEEE 802.3u in 1995, brought Ethernet to 100 Mbps — ten times Token Ring’s 16 Mbps maximum. Token Ring vendors responded with High Speed Token Ring (HSTR) specifications for 100 Mbps and 1 Gbps Token Ring, but these were never widely deployed.

IBM’s Strategic Retreat

IBM’s response to Fast Ethernet was cautious and late. The company continued manufacturing and selling Token Ring products through the 1990s, maintaining its existing customer base while the broader market shifted. IBM’s networking revenue from Token Ring was significant — the equipment carried higher margins than Ethernet — and IBM was reluctant to acknowledge that the transition was happening.

By 1997–1998, industry analyst reports estimated that Token Ring installations represented approximately 10–15% of the LAN market, down from roughly 40% in the early 1990s. New installations were predominantly Ethernet. Organizations that had deployed Token Ring were maintaining existing networks rather than expanding them; new buildings were wired for Ethernet.

IBM announced in 2001 that it would discontinue Token Ring product development and manufacturing. The company transferred its Token Ring IP to a new company, Madge Networks (which had been a significant Token Ring vendor), and exited the market.

The existing Token Ring installed base continued operating for years after IBM’s exit. Organizations with large Token Ring deployments — particularly those in IBM-heavy environments, financial services, and factory automation — had no immediate reason to replace working infrastructure. Migration to Ethernet required replacing NICs in every computer, replacing MAUs with Ethernet switches, and potentially recabling if STP installations were being replaced with UTP. These migrations happened gradually through the 2000s as equipment was replaced during normal refresh cycles.

Token Ring’s Legacy Markets

Factory automation and process control — the environments where Token Ring’s deterministic behavior was most valuable — largely adopted PROFIBUS and later Industrial Ethernet variants rather than standard IEEE 802.5 Token Ring. The industrial networking market developed its own specifications (PROFIBUS, DeviceNet, ControlNet, later EtherNet/IP) that provided determinism guarantees on top of standard physical layers. IBM’s Token Ring, designed for office networking, was not optimized for the industrial environments where its technical properties would have mattered most.

Dead End: Cost Always Beats Capability

Token Ring’s failure encodes a lesson that appears repeatedly in technology history: when two technologies compete and one is cheaper, the cheaper one tends to win even when the more expensive one is technically superior in measurable ways.

Token Ring’s deterministic access was genuinely valuable in specific scenarios — high-utilization networks, time-sensitive applications, environments where maximum latency mattered more than average latency. But most office networks were not high-utilization, and most office applications were not time-sensitive. Email, file transfers, and shared printers worked adequately on shared Ethernet at 10 Mbps; the collision-driven performance degradation at high load was a theoretical problem that few real installations reached.

The economics of Ethernet were driven by scale. The PC NIC market was enormous — every PC being sold needed a NIC — and the competition among NIC manufacturers drove prices down rapidly. Token Ring’s smaller installed base could not achieve the same economies. A technology with 40% market share and a technology with 10% market share pay very different prices for components, even if the smaller technology is technically superior.

Ethernet also benefited from timing: when the transition from coaxial to twisted-pair happened in 1990, Ethernet got there first and at lower cost. If Token Ring had offered a credible UTP solution at competitive prices in 1990, the market might have gone differently. Instead, IBM’s proprietary pricing and STP cable requirements gave Ethernet an opening, and Ethernet’s scale advantages closed the door.