Source: Metro Area Networking
PART
1 A Lesson in Medieval History
Downloaded from Digital Engineering Library @ McGra...
22 downloads
2477 Views
2MB Size
Report
This content was uploaded by our users and we assume good faith they have the permission to share this book. If you own the copyright to this book and it is wrongfully on our website, we offer a simple DMCA procedure to remove your content from our site. Start by pressing the button below!
Report copyright / DMCA form
Source: Metro Area Networking
PART
1 A Lesson in Medieval History
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
2
It is fascinating to me how much my interest in history helps me understand the evolution of modern networks and the inner workings of the technologies that power them. Metro networks are no exception. As I studied the evolution of the network from a relatively monolithic transport construct to a more differentiated and specialized set of technologies for performing access and transport tasks, I began to see parallels between it and —of all things—the development of medieval village societies. I had recently read Frances and Joseph Gies’ Life in a Medieval Village and Life in a Medieval Castle, and many of the things I learned while reading them were still rattling around in my head. When formal societies were still coalescing in Europe—prior to the sixth century or so—the world was a forbidding, often dangerous place. People huddled together in massed groups for protection because no form of social order existed to create formal, organized protection, division of labor, or any of the other characteristics of a modern society. As time passed, the social order evolved. The feudal castle model emerged in which people lived behind the walls of a fortress and relied on an organized militia for protection. Some people lived and worked outside the walls, but they were agricultural laborers who needed to interact with the land. The artisans and craftspeople (the more specialized laborers) lived within the castle that belonged to the landholder. The next evolutionary stage saw the development of the medieval village in the tenth century or thereabouts. As the Gies observe in Life in a Medieval Village1, The medieval village . . . was the primary community to which its people belonged for all life’s purposes. There they lived, there they labored, there they socialized, loved, married, brewed and drank ale, sinned, went to church, paid fines, had children in and out of wedlock, borrowed and lent money, tools, and grain, quarreled and fought, and got sick and died. Together they formed an integrated whole, a permanent community organized for agricultural production.
Life, then, was fairly concentrated in the sense that few strayed far from the fold. The only exceptions were those who struck out on their own to explore new frontiers, to expand the knowledge that society had at the time of life beyond known borders. They went in search of new opportunities and wealth, and often found it. However, they typically had to be supplied by caravans that traveled long distances to reach them, often at great peril.
1
Life in a Medieval Village, page 7.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
3
Over time, societies matured and became more complex. Instead of everyone living in a geographically constrained area, the boundaries of the societal model began to expand as new villages emerged. As social order arrived and stayed, and as a social fabric was woven that defined the mores of behavior for the people who lived in the society, the world became marginally safer. Soon people were straying farther from home and establishing cultural beachheads, and modern Europe began to flourish. From a highly centralized model, society evolved to include various modalities: the central castle that protected royalty and the wealthy merchant class, a collection of agrarian workers living immediately outside the castle and providing food to those within in exchange for protection, and a network of hamlets and villages scattered at the periphery of the territory overseen by the barony of the castle. How interesting it is to note that in many ways modern voice and data networks took a remarkably similar developmental path.
The Evolution of Modern Networks The first networks, of course, were simple point-to-point connections that interconnected individual households or businesses. The concept of switching had not been developed yet, so anyone who wanted to communicate with anyone else had to have a dedicated circuit between the two locations. There was a time when AT&T tried to gain control of rooftops in cities so that they would have a place to install the myriad wire pairs required to interconnect everyone that wanted service. Soon the skies were filled with wire, as shown in Figures 1-1 and 1-2. The only way to provide universal connectivity was to have individual connections for every conversation, and that required a lot of wire. Technically, a network that enabled any-to-any connectivity had to be fully meshed, as shown in Figure 1-3. With the arrival of switching came the ability to offer connectivity on demand. Instead of dedicated connections between every pair of would-be callers, each subscriber needed a connection from his or her house or business to the telephone company central office. There the switch (originally it was a human switch—the operator—shown in Figure 1-4) would take the call setup information from the subscriber and create a temporary connection between the calling and called parties. The result is that the bulk of the resources required to support telephony migrated into the core of the telephone network because it made technical and economic sense to do it that way. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
4 Figure 1-1 Aerial cable in a downtown area (Source: Lucent Technologies)
Figure 1-2 The number of crossbars on this pole illustrates the amount of wire that had to be in place to support telephony in the days before switching. (Source:Lucent Technologies)
As switching evolved and the human operator was replaced first by the mechanical, then the electromechanical, and finally the all-electronic switch, the intelligence that was part of the switching infrastructure began to show its value to both the service provider and the subscriber. New appliDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
5
Figure 1-3 A fully meshed network, showing any-to-any connectivity
Figure 1-4 Operators sitting at an old-style cord board (Source: Lucent Technologies)
cations evolved based on the marriage of computer and networking technologies, and the so-called intelligent network was born. This, in turn, led to the development of sophisticated capabilities that added to the perceived value of the network, which were the famous value-added services, including Caller ID, three-way calling, call return, and call trace. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
6
As the network grew and became more capable, it also became more functionally diversified. The voice network evolved into local and longdistance domains, helped along by a series of regulatory decisions that forced a functional and business-based schism between the two. Local service became primarily the access arm of the business, while long distance provided connectivity between far-flung communities.
Further Diversification In the 1970s, a new commercial phenomenon emerged: data transport. Corporations began to develop management information systems (MISs) and to forge new organizations to manage them, such as the Information Systems Organization (ISO or IS). Deep within the viscera of corporate data centers (see Figures 1-5 and 1-6), the mainframes and minicomputers, vital organs of the body of information that gave corporations their competitive edge, digested and processed the raw data they collected from the never-ending stream of transactions that fed them. These massive, centralized repositories relied on a web of dedicated, private-line facilities to interconnect them to the service centers, billing offices, and customer record centers that generated the traffic they managed. In the early 1980s, the PC arrived, and with it came a major reinvention of the data phenomenon. Instead of relying exclusively on centralized dataprocessing facilities, corporations began to rely more on a distributed pro-
Figure 1-5 Mainframe computers in a modern data center
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
7
Figure 1-6 A tape cartridge library in a modern data center
cessing model, which meant that like a cow with its five stomachs, the data was already somewhat digested by the time it arrived at the data center for processing. Instead of private-line circuits offering dedicated connectivity for the now famous “dumb terminals” through some kind of terminal multiplexer, PCs replaced the dumb devices. This began the migration of computing intelligence from the core of the network to the edge, where the users could take advantage of new capabilities to become better, more efficient workers. During this evolution of computer usage, the network went through a similar morphogenesis. As mentioned earlier, it initially had two regions: access and long-haul transport. Over time, however, a third region—the customer environment—was added to the list. This was where the local area network (LAN) first emerged, as did Ethernet, the most common of all LAN protocols. Thus, the customer environment (the LAN) generated and terminated traffic, the access network connected the customer to the network, and the transport network provided long-haul connectivity between customer locations. Interesting, isn’t it, how this compares to the castle, roadways, hamlets, villages, and far-flung outposts of early Europe?
Core Versus Edge: A Few Words Network-edge devices typically operate at the “frontier” of the network, serving as vital service outposts for their users. Their responsibilities Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
8
typically include traffic concentration, which is the process of statistically balancing the load against available network resources; discrimination, during which the characteristics of various traffic types are determined; policy enforcement, the process of ensuring that required quality of service (QoS) levels are available; and protocol internetworking in heterogeneous networks. Edge devices are often the origination point for Internet protocol (IP) services and typically provide no more than 20 Gbps of bandwidth across their backplanes. Core devices, on the other hand, are responsible for the high-speed forwarding of packet flows from network sources to network destinations. These devices respond to directions from the edge and ensure that resources are available across the wide area network (WAN), and guarantee that QoS is guaranteed on an end-to-end basis. They tend to be more robust devices than their edge counterparts and typically have 20 Gbps or more of full-duplex bandwidth across their backplanes. They are nonblocking and support larger numbers of high-speed interfaces. As the network has evolved to this edge/core dichotomy, the market has evolved as well. As convergence continues to advance and multiprotocol, multimedia networks become the rule rather than the exception, sales will grow exponentially. By 2003, consultancy RHK estimates that the edge switch and router market will exceed $21 billion, while the core market will be nearly $16 billion. At the core, Cisco currently holds the bulk of the market at roughly 50 percent, slightly less at the edge with 31 percent. Other major players include Lucent Technologies, Marconi, Nortel Networks, Juniper, Newbridge, Fore, Avici, and a host of smaller players. It is interesting to note that in order to adequately implement convergence, the network must undergo a form of divergence as it is redesigned in response to consumer demands. As previously described, the traditional network concentrates its bandwidth and intelligence in the core. The evolving network has in many ways been inverted, moving the intelligence and traffic-handling responsibilities out to the user, replacing them with the high-bandwidth core described earlier. In effect, the network becomes something of a high-tech donut. A typical edge-core network is shown in Figure 1-7. The core, then, becomes the domain of optical networking at its best, offering massively scalable bandwidth through routers capable of handling both high volume traffic and carrying out the QoS dictates of the edge devices that originate the traffic. The drivers behind this technology schism are similar to those cited earlier. They include
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
9
Figure 1-7 The edge and core regions of a modern data network
■
The need to create routes on demand between individual users as well as between disparate work groups in response to the market shying away from dedicated, costly facilities.
■
Guaranteed interoperability between disparate protocols.
■
Universal, seamless connectivity between far-flung corporate locations.
■
The optimum utilization of network bandwidth through the appropriate use of intelligent prioritization and routing techniques.
■
Traffic aggregation for wide area transport to ensure the efficient use of network bandwidth.
■
Granular QoS control through effective policy and queue management techniques.
■
The growing deployment of high-speed access technologies such as Digital Subscriber Line (DSL), cable modems, wireless local loop, and satellite connectivity.
And why is this evolution occurring? Because the closer the services a network provider sells are placed relative to the customer, the more customized, targeted, and immediate those services become. When they are housed in a shared central office, they are much more generalized, catering more to the requirements of the masses and treating the customer as if their requirements were commodities. As the network evolves and a clear functional delineation between the edge and the core becomes visible, the
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
10
role of the central office suddenly changes. In fact, the central office largely disappears. Instead of a massive centralized infrastructure from which all services are delivered (similar to the model employed in legacy data centers), we now see the deployment of hundreds of smaller “regional offices” placed close to customer concentrations and housing the edge-switching and routing technology that deliver the discrete services to each customer on an as-required basis. Those smaller offices are in turn connected to the newly evolved optical core that replaces the legacy central office and delivers high-speed transport for traffic to and from the customers connected to the edge offices. This is the network model of the future: It is more efficient and places both the services and the bandwidth that they require where they belong. Of course, the network management model must now change in response to the new network architecture. Instead of managing centralized network elements—a relatively simple task—the management system must now manage in a distributed environment. This is more complex, but if done properly it results in far better customer service because of the immediacy that results from managing at the customer level. Customer applications have evolved to require more bandwidth in response to its enhanced availability at a reasonable price, and dramatic augmentations have been made to the capabilities of customer-provided equipment (CPE), such as bridges, routers, switches, and multiplexers. Because of these factors, the traditional requirement that the aggregation, prioritization, and concentration of traffic be done in the network core is no longer valid. Additionally, network protocol models have evolved to the point that traffic prioritization and QoS guarantees no longer have to derive from central-office-based hardware and software. In fact, more and more, modern networks have evolved such that they now comprise two primary layers: an outer edge region, responsible for QoS policy enforcement, and a central core region, responsible for carrying out the mandates of edge devices and transporting traffic at all possible haste across the WAN. One driver behind this evolution is the shift in protocol models as IP-based networks become more and more common, and IP delivers upon its promise of a protocol-agnostic, high-bandwidth, QoS-driven architecture.
The Birth of Metro In the late 1980s, a new network region began to emerge. Driven by growing bandwidth requirements in campus installations and to a certain Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
11
degree by the mixed bandwidth demands of multitenant office buildings in major cities, the first rudimentary form of metropolitan area networks (MANs) arrived. There were good reasons for this early evolution. Corporations were beginning to rely more and more on their corporate data centers and the services they provided for competitive advantages. As a result, they also relied heavily on network connectivity to provide access to databases from remote locations. Traditional private-line technologies were neither costeffective nor redundant, and the cost to add redundancy was prohibitive. When the first metro carriers (Teleport Communications Group and Metropolitan Fiber Systems, the dreaded bypassers) came along with promises of optical connectivity, corporate information technologies (IT) and telecom managers sat up and took notice. Synchronous Optical Network (SONET) in the United States and Synchronous Digital Hierarchy (SDH) in Europe and the rest of the world were emerging as powerful ring-based transport options, and these companies built major installations in large cities based on these technologies. With promises of dual entry and 24⫻7 monitoring, they cornered a large segment of the enterprise market. The next technologies to step into the spotlight were Fiber Distributed Data Interface (FDDI) and the Switched Multimegabit Data Service (SMDS). FDDI was really something of a cross between the ring structure of SONET and IBM’s Token Ring, while SMDS was for all intents and purposes a form of connectionless Asynchronous Transfer Mode (ATM). Both were designed to offer high-speed service within the metro environment, and although they did so quite effectively, neither of them enjoyed significant longevity. There were several reasons for this: one was the fact that the metro market was new and really had not achieved critical mass as yet; another was that the demand for bandwidth had not yet reached the levels that either was capable of delivering; and the third was that both FDDI and SMDS were quite complex.
Fiber Distributed Data Interface (FDDI) FDDI was designed to address the growing requirements for connectivity in the metropolitan area. It had two key applications: to serve as a premiseswide backbone for LAN traffic in business parks or other campus environments, and to provide connectivity between high-speed workstations at research institutions. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
12
FDDI relies on token passing to control access to the shared transmission medium. First, it is important to note that token passing is typically implemented on ring networks. As a result, traffic always travels in the same direction, and the order of appearance of the stations on the LAN never changes. One consequence of this is a very predictable maximum token rotation time, which translates to a bounded delay in the transmission of data. This becomes a significant factor when latency is an issue. When a station wants to transmit a file to another station, it must first wait for the “token,” a small and unique piece of code that must be “held” by a station to validate the frame of data that is created and transmitted. Let’s assume for a moment that a station has secured a token because a prior station has released it. The station places the token in the appropriate field of the frame it builds, adds the data to be transmitted along with the destination address information, and transmits the frame to the next station on the ring. The next station, which also has a frame it wants to send, receives the frame, notes that it is not the intended recipient, and also notes that the token is busy. It does not transmit but instead passes the frame of data from the first station on to the next station. This process continues, station by station, until the frame arrives at the intended recipient on the ring. The recipient validates that it is the intended recipient, at which time it makes a copy of the received frame, sets a bit in the frame to indicate that it has been successfully received, leaves the token set as busy, and transmits the frame on to the next station on the ring. Because the token is still shown as busy, no other station can transmit. Ultimately, the frame returns to the originator, at which time it is recognized as having been received correctly. The station removes the frame from the ring, frees the token, and passes it on. FDDI differs from traditional token ring in one very significant way: It has two rings, not one. FDDI is a dual, counter-rotating optical ring architecture that operates at 100 Mbps and is capable of supporting as many as 500 workstations with distances between nodes as great as 2 kilometers. In a dual-ring deployment, the total ring length cannot exceed 100 kilometers. The dual-ring topology, shown in Figure 1-8, is primarily for fault tolerance. For the most part, stations are directly connected to both rings. One ring operates in a clockwise direction, while the other transmits data on the counterclockwise ring. One ring can be used as the primary path while the other can be used as a back ring. If the primary ring fails, stations on either side of the fiber cut realize that the signal has been lost, and the backup ring becomes the primary data path. In the event that both rings are cut, the stations on either side of the breach “wrap” internally, as shown in Figure 1-9. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
Figure 1-8 The typical dual-ring architecture found in optical networks
13 A
D
B
C
Figure 1-9 The failure of both rings causes the ring to wrap, ensuring connectivity.
B
C
A
D
Stations can be attached to FDDI rings in a variety of ways, as shown in Figure 1-10. A single attachment station (SAS) is only connected to the primary ring, while a dual-attached station (DAS) is connected to both the primary and backup rings. An alternative technique is to use what is called a dual attachment concentrator (DAC) that attaches to the rings and serves Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
14 DAS
Figure 1-10 A representative FDDI ring showing SASs, DASs, and a DAC with multiple stations
SAS A
D
B
DAC C
as a multiplexer of sorts, enabling multiple stations to access the rings as required. This architecture has pros and cons. It provides very good fault tolerance since the workstations themselves are isolated from the ring and therefore cannot disrupt transmission, should an individual workstation fail. It also enables easy network planning and lower-cost deployment. Furthermore, the technique is less disruptive to the overall network since the ring is not affected when stations are added or removed. On the other hand, the concentrator represents a failure point that could conceivably affect multiple stations. FDDI is still used in some corporations, but the rise of Fast and Gigabit Ethernet has for the most part stymied its proliferation. The other technology that heralded the arrival of the metro network was SMDS.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
15
Switched Multimegabit Data Service (SMDS) SMDS, largely gone now, was a connectionless, high-speed, packet-based data transport mechanism. It supported standard protocols, interfaces, and technologies. SMDS enabled users to extend their data communications reach over a broad geographical area. Since it was a service offered by the telcos rather than a technology, it permitted this distance extension using existing Customer Premises Equipment (CPE) with minimal upward investments in leased lines as the number of users increased. SMDS was defined by the Institute of Electrical and Electronics Engineers (IEEE) in its 802.6 MAN standard and was adopted and implemented by Bellcore, now a division of the Science Applications International Corporation (SAIC) known as Telcordia. The technology’s evolution occurred in parallel with ATM, and because SMDS is also a cell-based service, it enjoyed quite a bit of attention as ATM’s ascendancy began. Both services rely on 53-octet cells and can accommodate packet lengths as large as 9,188 octets (the maximum packet size for SMDS is 9,188 octets, while the maximum length for ATM is much larger. SMDS relies on three distinct protocols for its general functionality: Distributed Queue, Dual Bus (DQDB), the SMDS Interface Protocol (SIP), and the Data Exchange Interface (DXI). DQDB defines the manner in which stations gain access to the shared medium, SIP defines the interface between the end user and the medium, and DXI defines a standard protocol at the physical and data link layers for communication between the router and the data service unit (DSU)/channel service unit (CSU). Most North American implementations relied on DQDB, with DS1 or DS3 access for connectivity. SMDS was designed to provide broadband services across the metro region, but because it was a public offering it never enjoyed the uptake rate that would enable it to reach critical market mass. Banks, for example, expressed concerns over the transport of private banking data over a public network infrastructure, even though there was no justification for the concern. Virtual private networks (VPNs) with secure encryption protocols and tunneling capabilities had not yet been invented, so no precedent had
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
16
been established to define just how secure a public infrastructure solution could actually be. Many industry pundits claim that if SMDS had simply been renamed “Connectionless ATM,” the service providers would not have been able to keep up with orders. Unfortunately, like FDDI, it withered away and has for the most part disappeared. The metro market, of course, has continued to expand as new technologies have stepped into the breech. One of these, Ethernet, has been “reinvented” and is succeeding handily. More on Ethernet later.
The Maturing Metro Market According to a recent study by consultancy RHK, the unstoppable demand for bandwidth in North America will generate $4 billion in new revenues by 2006 for service providers that offer optical Ethernet connectivity within the metro space. Similarly, In-Stat predicts that the metro optical network market will grow from an already respectable $13 billion in 2001 to $23.6 billion by 2005, which moves the market segment to the top (or at least very close to the top) of the list of high-growth telecom segments. An array of new technologies is creating deployment strategies that meet the needs of metropolitan optical networks by not only introducing new technology solutions, but by also extending the life of installed legacy plant and protocols that are perfectly serviceable and may not yet be fully depreciated. The current state of the economy has caused service providers and other formerly capital-rich companies to reconsider their spending strategies. Ethernet and other legacy solutions are well understood, cost effective, and, given their current operational characteristics, perfectly capable of supporting the demand for broadband access and transport that is growing apace in the metro marketplace. SONET and SDH now routinely operate at 10 Gbps, and some next-generation optical hardware efficiently manages packet traffic and provides support for the burgeoning multiservices network. Dense Wavelength Division Multiplexing (DWDM) systems are being deployed in both core transport and edge access environments, and Optical Ethernet, operating at 1 Gbps and higher, is blurring the line between the LAN and the MAN.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
17
Metro Market Segments Today, the metro marketplace has changed dramatically. It has come into its own and become the focal point for a significant number of companies that include component manufacturers, system manufacturers, service providers, and the end users within the metro marketplace (see Figure 1-11). In fact, these four segments make up something of a food chain in the metro arena: End users buy services from the service providers, service providers buy systems from the systems manufacturers, and systems manufacturers buy semiconductor and opto-electronic components from the component manufacturers. In reality, the metro networking environment has become extremely important to all four layers of the food chain. The reasons are well known, but it would be wise to review them here. The first reason was stated earlier: Metro is the last frontier in the development of the global telecommunications network. Because it lies close to the customer, and because it serves a new type of customer (the multiservice enterprise metro user), untold revenues can be mined from the segment. Keep in mind that the greatest diversity of new opportunities always lies at the periphery of the current operating domain, regardless of whether the discussion topic is networks, computers, biotechnology, or European explorers pushing the limits of geographic knowledge. We often hear tales about the optical glut in today’s network. Let us be perfectly clear about the truth behind that observation: Although an overabundance of optical fiber has been installed in the core transport network,
Figure 1-11 The metro marketplace food chain
End User
Service Provider
System
Component
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
18
and therefore an attendant overabundance of available bandwidth exists, there is a dramatic paucity of bandwidth at the edge. Broadband access is still not as widely available as customers and service providers would like, and the metro space is equally underrepresented. The primary reason for the lack of bandwidth at the edge is regulatory, not technological in nature, and although regulatory bodies are now coming to grips with the results of earlier decisions and taking steps to move broadband forward, such things take time and are politically charged. We’ll talk more about the impact of regulatory decisions later in the book. Another driving force is service creation: The metro network lies between the customer-premise-based LAN and the service provider’s transport network. It therefore plays a significant part in the service provider’s ability to offer what customers demand, particularly given the dynamic nature of the metro networking environment. As LAN solutions become more servicecapable and as transport technologies plummet toward commodity status, the need to bridge what appears to be an “unbridgeable gap” between the service-rich edge and the high-bandwidth, low-cost core becomes critically important to both service providers looking to preserve their dwindling revenue base and customers looking for diverse service capabilities. Of course, like anything new, the metro network environment has its set of challenges that present difficulties for service providers and users alike. The metro domain is neither local, access, or transport; in fact, it has elements of all three. It is neither circuit-switched nor is it packet-based; instead, it’s a hybrid of the two. Finally, metro networks are not well understood yet, which means that the enormous volumes of data that they have now been found to generate are not necessarily well served by current network designs. The diverse collection of applications found in the metro— LAN traffic, video, high-bandwidth data, voice, Internet, and so on—makes capacity design considerations something of an arcane art. Most metro infrastructures are built upon legacy SONET rings, which are fine for the transport of synchronous, high-speed data generated by traditional applications, but they are inadequate for the requirements of less predictable bursty traffic streams from packet-based applications. And when the two are mixed across the same network, one typically dominates network resources and somebody’s service quality suffers. Another issue is protocol complexity. Consider the requirements of the typical enterprise network customer: They want (at a minimum) low-cost, high-bandwidth transport; 24/7 proactive network management and vendor support; discrete, configurable, dynamic, and measurable QoS with an attendant service level agreement (SLA); and multiservice, multiprotocol support. To accomplish this today, networks look like a layer cake: multiDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
19
channel DWDM at the lowest level for bandwidth; SONET or SDH at the next level for management and international standardization; ATM at the next level for predictable, configurable, and measurable QoS; and IP at the highest layer for multiprotocol support. The protocol overhead alone is out of bounds. SONET reserves roughly 5 percent of each frame for management overhead, ATM reserves 10 percent of every cell for network overhead, and even IP holds back a small percentage of the available bandwidth for packet overhead. If the protocol complexity can be reduced, and if some of the overhead can be eliminated or at least minimized, a far more efficient network will result. Consider the diagram shown in Figure 1-12. The left side of the illustration details the model we have just described: IP over ATM over SONET/SDH over DWDM. This model is by far the most costly, most complex, and least efficient protocol stack that could be implemented. It does the job, however. All the requirements (high bandwidth, low cost, QoS, multiprotocol support) are possible with this four-tier model. It represents the legacy model of service transport. Over time, one plan will evolve through the two possible scenarios shown in the center of the diagram. The first one, IP over ATM over DWDM, assumes that SONET and SDH are no longer required because the management and framing they typically offer are being done somewhere else, thus reducing one layer of overhead. Similarly, the next transitional model assumes that ATM has been eliminated, presumably because its granular QoS capabilities are being performed by another protocol, presumably Multiprotocol Label Switching (MPLS) or Generalized MPLS (GMPLS) (more on these later in the book). With this model, the ATM “cell tax” is eliminated. Finally, by ultimately implementing the model shown on the right
Figure 1-12 The evolution of technology in the metro network
IP
IP
IP
IP
ATM
ATM
SONET
Ethernet
DWDM
DWDM
DWDM
SONET DWDM Most costly Most complex Least efficient
Least costly Least complex Most efficient
Legacy………Transitional…………Future Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
20
side of the illustration, we eliminate both ATM and SONET/SDH. IP packets are instead encapsulated in Ethernet frames for transport across the network, and DWDM channelization provides all the necessary bandwidth. This is clearly the most cost-effective, efficient, and least complex model available to network providers and customers today. And although it has not yet been widely implemented, it will be as networks evolve toward their future architecture schemes. As a result of all these complex issues, the metro network is a complex environment to work within and is therefore a challenge to both manage and budget. Clearly, the metro space is not going to go away. It’s not one of those passing fads, nor is it a network region that is in danger of being subsumed by another. So what efforts are underway to help overcome the challenges posed? First of all, given the growing influence of Ethernet in all its many forms and the perception that SONET and SDH are inflexible and getting a bit long in the tooth for certain applications, a number of standards bodies have kicked off efforts to reexamine and redefine the standards that govern goings-on within the metro arena. Among these are IEEE efforts for Gigabit and 10-Gigabit Ethernet; ITU X.86, which maps Ethernet frames into SONET/SDH frames; and the IEEE’s 802.17 standard for the recently announced Resilient Packet Ring (RPR) technology that will ultimately replace SONET and SDH in certain situations. Other standards work is just beginning on such technology areas of interest as Carrier-Class Ethernet (Ethernet with QoS so that it can offer the legendary “five nines of reliability”), switching infrastructures based on MPLS and/or GMPLS, the long-term use of DWDM, the role of next-generation intelligent networks, and the evolution of network management requirements.
Carrier-Class Ethernet Carrier-Class Ethernet has enjoyed significant attention in recent months for all the right reasons. It is well established and understood, it is userfriendly, it is internationally standardized and accepted, and it is inexpensive. Because of these factors and the evolving demands of the marketplace, Ethernet is finding itself thrust in a variety of directions. It is seen as a potential replacement for SONET and SDH, and as a service interface capable of supporting multiprotocol/multiservice access for such protocols as traditional voice, voice over IP (VoIP), VPNs, Frame Relay, ATM, and IP.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
21
Traditional Ethernet was never intended to address the applications it is currently being positioned to resolve. However, the arrival of Gigabit and 10- Gigabit Ethernet has changed that, and the technology is taking on new responsibilities for which it is imminently qualified. For example, 10-Gig Ethernet will be formally ratified later in 2002; already, however, a number of 10-Gig Ethernet solutions are on the market. Ten-Gigabit Ethernet is quite flexible and can be implemented in a range of topologies, including connection-oriented networks, traditional Ethernet, switched networks, mesh topologies, and rings. It can be deployed in pointto-point architectures or as an aggregation technology for lower-speed Ethernet segments. The technology has a variety of advantages that include scalable bandwidth ranging from 64 Kbps to 1 Gbps, the capability to offer service-level granularity (including burst and bit-rate guarantees), rapid provisioning, point-to-point and point-to-multipoint installation options, and compatibility with legacy SONET installations through the transmapping of X.86. Of course, like any new technology, Carrier-Class Ethernet has its share of detractors, many of them among the carriers. Their single greatest concern is the degree to which Ethernet can handle both bursty data applications and the synchronous requirements of voice and continuous data. They are also concerned about the technology’s capability to support high-speed restoration and rerouting as well as legacy solutions already do. Some believe that although Ethernet is highly capable, it is not the most efficient protocol available for existing applications. Some believe that it is wasteful of bandwidth when implemented in ring configurations, the primary reason that IEEE 802.17 (RPR) is under development. As we will see later in the book, RPR is extremely efficient, making the most of available ring bandwidth and offering 50-millisecond protection switching.
MPLS/GMPLS-Enabled Networks MPLS, first created by Cisco under the name tag switching and later adopted by the Internet Engineering Task Force (IETF), combines datalink-layer information about the state of network links such as bandwidth, latency, and overall utilization with network-layer information (typically IP) to improve the efficiency of packet exchange. It gives service providers significant flexibility for traffic rerouting in order to avoid link failures, congestion, and network bottlenecks.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
22
One of the greatest beneficiaries of MPLS is Internet service providers (ISPs), who will be able to manage different kinds of traffic based on priority and requested QoS levels. This translates into variable billing options, which in turn translates into adaptable customer service. In MPLS networks, label edge routers (LERs) assign a label (in reality, an identifier) to each packet. These labels contain destination information, bandwidth requirements, delay limits, and a variety of other measurements. Once the packets have been classified, they are assigned to label switched paths (LSPs), where label switched routers (LSRs) assign labels to the outgoing packets. As a result, network operators can reroute traffic based on a variety of customer requirements and characteristics. Packet processing occurs much faster because packets do not have to be opened and examined by every router along the path. GMPLS, on the other hand, is designed to enable edge devices such as routers and switches to request bandwidth directly from the optical layer. It is also designed to make the optical network more dynamic by migrating intelligence into some traditionally “dumb” optical elements such as optical cross-connects. By adding intelligence in specific areas of the optical network, providers can offer faster restoration of service following network disruptions and more efficient bandwidth utilization. GMPLS also will deliver information about the optical network to embedded routers, enabling them to make more informed decisions about network routing using knowledge about the “health” of routes through the optical network. GMPLS lends itself to the management of Time Division Multiplexing (TDM)-switched networks, packet-switched networks, lambda-switched optical networks, and fiber-based transport. In short, it attempts to inject the sophistication of the router into the optical layer for a wide variety of network types.
DWDM Conduit space in the metropolitan area has been depleted in many cities, and the cost to add more can be prohibitive, as can the morass of permits and bureaucratic paperwork required to secure permission to dig up city streets. DWDM is one alternative that has received a great deal of attention. In the long-haul environment, the cost to deploy additional fiber as a solution to capacity exhaust is approximately $70,000 per fiber mile, compared to $12,000 for the same capacity addition accomplished through DWDM deployment. In the metro, those numbers are higher because of the Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
23
environment: more congestion, more traffic, and more obstacles. Nevertheless, DWDM is a good solution because it offers the opportunity to add more available bandwidth by changing the endpoint electronics rather than trenching and physically adding fiber. Metro DWDM is the latest arrival on the scene, with devices offering as many as 32 wavelengths per fiber at 10 Gbps per channel. Forty Gbps is just around the corner, which adds more credence to the claim that it is far more cost effective to replace the endpoint electronics than it is to physically add fiber. Of course, this adds a whole new management element that to date has largely been ignored. Bandwidth management at the optical level has traditionally been primitive at best, a serious problem for the metro service provider that wants to offer differentiated services based on discrete optical network management. The result of this is the arrival of a whole new set of companies in the optical space that offers products known as multiservice provisioning platforms (MSPP). These platforms enable the service provider to manage their infrastructure components and service offerings with far more granularity. They offer service providers the ability to gradually migrate to an all-optical infrastructure when the time arrives, to support wavelength-based services at the optical level, and to support legacy, transitional, and future services all on a common network infrastructure. This is a powerful capability indeed. Lucent Technologies was one of the first companies to offer this service with its WaveWrapper technology, and others have followed. A number of new and significant standards have been put into place in the last couple of years that address wavelength management, including G.959.1 and G.709. Many vendors are taking this approach, using proprietary methods to perform optical framing and wrapping. In other words, they encapsulate client signals in a framing scheme—using digital wrappers—that supports management and monitoring functions as well as higher-order multiplexing. The purpose of optical framing in DWDM systems is to produce a wavelength-aware device that can provide transport for all the other major lower-layer protocols, including SONET and SDH. These techniques are proprietary now, but standards for DWDMenhanced/all-optical networks are falling into place. A number of optical network standards were presented during 2001, including G.709 and G.959.1, which address the physical-layer interfaces and the frame format for all-optical networks. G.709 was carefully written to incorporate many of SONET and SDH’s more valuable characteristics, including performance monitoring and span protection, yet it also adds forward error correction (FEC) and end-to-end wavelength management (to address the arrival and Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
24
incorporation of DWDM). The only disadvantage of G.709 is that it requires a substantial investment in new network infrastructure; the result is that many carriers may choose to ignore new solutions until they absolutely require conversion to a new standard.
The Next-Generation Intelligent Network The intelligent network is an old concept now, but the idea is still a powerful one. By embedding intelligence in the network in the form of databases and computers capable of accessing them, and by devising applications that extend the capabilities of the in-place network through the judicious use of those network-based databases, the network suddenly begins to generate revenue in new ways. Value-added services are designed to eke more out of the legacy network, and they do: Consider the revenues generated by Caller ID services alone. These information services add revenues to a revenue stream (voice) that is essentially flat. Next-generation services are those that will become available as the network evolves through the addition of optical bandwidth, more effective optical management, and more evolved routing capabilities (MPLS and GMPLS). Although MPLS was not specifically designed for the metro market, it is carving out a significant niche for itself there. As we discussed earlier, its primary function is to enable routers and switches to designate end-to-end paths through a packet or cell-based network with specific QoS characteristics implied. As a result, carriers can support connection-oriented services such as enterprise VPNs and ATM, a variety of traffic engineering requirements, and bandwidth management on a network-wide basis. Because it is compatible with both ATM frames and IP packets, MPLS supports the evolution of IP switching, the well-known hybrid technology that incorporates the best of both IP and ATM. MPLS was originally targeted at packet networks with the specific goal of providing a migration path that would ultimately eliminate the need for ATM, the sole source of QoS in modern packet networks. Generalized MPLS, however, is designed for all-optical networks and works with SONET, SDH, and DWDM. MPLS and GMPLS may well serve as the integration layer for metro networks by providing intelligent management and QoS guarantees for DWDM-enhanced optical networks that transport IP packets. It could offer
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
25
end-to-end bandwidth provisioning, traffic engineering, network or lambda management, and monitoring/redundancy services.
Network Management The last thing implemented and the first thing missed, network management is one of the most important aspects of competitive networks. Without management, the network cannot be monitored, provisioned, maintained, or able to generate invoices for the usage of resources. It is perhaps the single most important differentiator of all, because it permits network administrators to define the capabilities of their network and to develop service offerings based on that definition. These efforts are designed to improve network efficiency, manage the increasingly unpredictable (and massive) packet volume that networks are required to transport, reduce the overall cost of providing network services, and reduce provisioning intervals (a significant competitive advantage). In short, the goal is to (1) reduce costs, (2) increase revenues, or (3) both. Consider, for example, the evolution of SONET and SDH. It is a massively overhead-heavy protocol model that manages a wide array of functions. At one time, those functions were necessary because no other network protocol was capable of performing them. Today, however, many of those functions are considered to be redundant or no longer required, given the changes that have occurred with the characteristics of transported data. Today SONET and SDH are being positioned to perform a reduced subset of tasks. These include 50-millisecond protection switching to a backup span, remote element management to ensure that any device on the ring can be surveilled and managed remotely, enhanced performance monitoring, end-to-end path management, and the full complement of Operations, Administration, Maintenance, and Provisioning (OAM&P) capabilities that the technology has come to be known for. All these exist in traditional legacy SONET/SDH implementations, but many other capabilities that have now been deemed largely unnecessary also exist, so the intent is to “prune the capability tree,” as it were. The bottom line is this: Networks by and large are migrating to a packet model, and SONET and SDH were never designed to handle packets. The intent is to evolve the legacy infrastructure so that it lends its considerable capabilities to the IP world while at the same time preserving the investment that service providers have made. Given the interest in evolving multiservice network infrastructures, it only
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
26
makes sense that legacy technologies, to the greatest degree possible, will be preserved with a certain degree of modification. SONET and SDH, which will be discussed in detail later in the book for those readers interested in learning more about the details of the technology, are really expanded and more capable versions of T- or E-Carriers—T1 on steroids, if you will. They provide a channelized or unchannelized “pipe” capable of carrying a wide variety of payload types, provided those payload components fit within the parameters of the framing structure. The new SONET or SDH is a multiservice-friendly technology that is more adept at transporting packets, a characteristic that is particularly important in metro networks. The only downside today is that because this evolved architecture is still relatively new, it is largely proprietary. However, the ITU-T has created Draft Standard G.7041, which defines a generic framing procedure (GFP) for the evolved SONET/SDH infrastructure. The bulk of the standard was written in 2001, and while work on it continues, it is expected to be complete by the end of 2002 or the beginning of 2003. In effect, G.7041 removes components of SONET and SDH that are deemed to be unnecessary for modern networks, leaving what many call a “thin physical layer” deployment that preserves required capabilities while eliminating those that are not. It will be implemented in two forms: Frame-Mapped (GFP-F) and Transparent mode (GFP-X). Frame-Mapped mode will be used for the encoding and transport of protocols that have already been framed or packetized by the originating client, such as the point-to-point protocol (PPP), IP, Ethernet Media Access Control (MAC) frames, or even Frame Relay frames. Transparent mode is designed to address the growing requirements of LAN and storage network installations and is designed to transport block-mode traffic such as Gigabit and 10-Gigabit Ethernet, Fibre Channel Connectivity (FICON), Enterprise System Connectivity (ESCON), Fibre Channel, and other Storage Area Network (SAN) protocols. Standards developers cite numerous advantages to the generic framing structure approach, including improved bandwidth efficiency due to multiplexed packet-based data streams, the capability to deliver granular QoS, significantly lower overhead than prior technology solutions, backward compatibility with existing implementations, a multiservice-friendly approach, a standards-based mapping scheme for multiple protocols, and, perhaps most important, a design that is friendly to current, transitional, and future network and service architectures. The generic framing structure concept is not necessarily a universally acceptable solution, however. Because it is built around the SONET/SDH model, it will be most attractive to companies with a large installed base of Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
27
legacy optical technology—the incumbent carriers. It is also (to use a term from The Hitchhiker’s Guide to the Galaxy) inextricably intertwingled with other emerging technology standards such as optical burst switching and resilient packet ring, which means that its adoption and commercial success may be a bit slower than many would like.
An Aside: Resilient Packet Ring (RPR) RPR has been standardized under IEEE 802.17 and is designed to interoperate with any packet- or frame-based protocol, not just Ethernet. It is designed to support the delivery of so-called carrier-class packet services through the adoption and use of expanded redundancy, traffic engineering, and deterministic resource management. Expanded redundancy refers to the fact that RPR relies on traditional ring survivability techniques, including a 50-millisecond switchover from a primary to a backup ring, node awareness, and ring wrapping. Traffic engineering refers to the fact that RPR is designed to allocate bandwidth on an as-needed basis, using a network-wide (or ring-wide) bandwidth allocation technique. Finally, deterministic resource management speaks to the fact that RPR replaces traditional ring-buffering techniques with ingress node queuing and packet discards, a far more intelligent packet management technique. These will be discussed in more detail later in the book.
Anatomy of the Metro Network: The Edge Metro networks reside at the edge of the WAN or core backbone network and touch both the user and the core. As a result, they incorporate both edge and core devices. Edge devices operate at the frontier of the network and are responsible for protocol internetworking, traffic concentration, QoS policy enforcement, and traffic flow discrimination. They provide the access capabilities of the metro network and serve as the interface to the wide area transport domain. This is also the place where IP is often first encountered as a network-layer protocol used to implement multiprotocol or multiservice networking. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
28
The Multiservice Metro Network Multiservice networking defines the capability of a single network to transport a variety of traffic types over the same physical infrastructure while preserving their various requirements for transport quality. In today’s world, six primary service types are targeted for this type of network: ■
Voice, which includes not only so-called carrier-class voice, but also IP telephony and other alternatives.
■
IP, which includes Internet access, long-haul IP transport (with or without QoS), and interworking among routers.
■
Private line, which includes both channelized and unchannelized T1 and E1, point-to-point Ethernet transport, DS3, E3, and SONET/SDH facilities.
■
ATM, including QoS characteristics such as channel concatenation, service adaptation and emulation, and QoS-aware transport support for DSL access, cable access, and voice, video, and data services.
■
LAN, including VPNs, LAN extensions, virtual LANs (VLANs), transparent LAN (TLAN) services, and LAN-based edge switching.
■
Wavelength-based services, which rely on DWDM to offer scalable and configurable bandwidth on demand.
It should be clear that because of their unique location in the overall topology, metro networks must provide a collection of key functions that distinguish them from the edge and core. These include ■
Demarcation, the logical separation point between the core and the edge, or some other designated network regions
■
Adaptation, the technique used to match a transported payload to a transport medium
■
Aggregation, the process of combining multiple traffic flows for simultaneous transport across a shared path
■
Transport, or transmission
■
Edge switching, the process of establishing the initial path at the edge of the network before being handed off to the long-haul portion of the network
■
Core switching, long-haul, high-speed transport
■
Grooming, the addition or deletion of certain designated channels at an intermediate point along the way
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
29
■
OAM&P, the standards functions performed in the management of a telecommunications network
■
Billing and service delivery, as defined by the customer
Furthermore, because they are visible to the customer (because they touch the customer) and also connect to the core transport network, metro networks must be survivable, flexible, reliable, cost effective, easily configurable, and manageable. They must also offer a broad array of capabilities, including differentiable QoS, service transparency (transport and payload independence), broadcast, and point-to-multipoint connectivity. Much of the energy that has propelled the service providers toward a multiservice philosophy and which in turn has caused the system manufacturers and therefore the component manufacturers to turn their attention in the same direction comes from the ongoing technology convergence phenomenon. Technology convergence defines the desire of service providers to simplify their business operations by reducing the complexity of the network through reductions in hardware, software, and protocols that they must support. The common misconception is that service providers are working hard to migrate traffic to a single, all-IP network, eliminating the need for separate support, operations, design, provisioning, repair, and sales organizations for each of their networks: ATM, Frame Relay, IP, wireless, the Public Switched Telephone Network (PSTN), X.25, and others. This is indeed a misconception, although not entirely. Service providers do want to simplify their networks by reducing the number of elements they must manage, the amount of enabling software they must support, and the number of protocols they must carry. However, they are also quick to say that their intent is not to retire legacy technologies such as T1/E1, SONET/SDH, and others, because these technologies do, after all, generate the bulk of service provider revenues. Instead, they are making seminal decisions about the overall architecture of the network, taking into account the fact that the core and the edge are distinctly different in both form, function, and the developing models that enable legacy and new technologies to exist side by side. The device that makes this change in the network possible is the multiprotocol (or multiservice) add-drop multiplexer (ADM). The concept is simple. A high-speed backplane in the device accepts input from an array of input/output (I/O) cards, each of which is designed to process a different protocol: ATM, Integrated Services Digital Network (ISDN), IP, PPP, Frame Relay, voice, and a host of others. QoS software enables traffic prioritization
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
30 Figure 1-13 A multiservice ADM
ATM FR IP
Multiservice ADM
High-speed trunks
T1 SONET SDH
and queue management; the result is network simplification. A schematic representation of a multiservice ADM is shown in Figure 1-13.
Network Inversion The network is undergoing an inversion of sorts in which the distinct functions of the edge and core regions of the network are becoming (for the first time, really) clear and distinct. Historically, the core of the network has had a variety of functions. It provided high-speed, wide-area transport, the signaling intelligence necessary to carry out efficient network routing, many of the applications that provided functionality to customers, and rudimentary protocol discrimination. In the last few years, however, that model has become untenable because of customer application diversification and the growing demand for increasingly granular service differentiation at the edge of the network. As a result, many of the functions that have traditionally resided within the network core are migrating to the edge. For example, protocol discrimination (multiprotocol capability) and QoS-based policy enforcement, formerly done in the core switch or router, are now performed at the edge of the network by intelligent edge devices that aggregate traffic, prioritize it according to a rule set established by the customer, and communicate with core transport resources to ensure that each logical traffic stream is handled according to its QoS requirements. Furthermore, bandwidth has begun to migrate from the core to the edge as the network inversion continues. Recent regulatory decisions that make the universal provisioning of broadband access infinitely more appealing to the incumbent service providers will cause them to begin the task of pumpDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
31
ing additional capital into the edge of the network in short order. Highspeed access that is widely available will spark the creation of broadbanddependent applications, most notably those dependent upon multimedia content. The result of this cascade of functionality is the creation of the multiservice edge. Consider the facts: Service providers have spent hundreds of millions, if not billions, on their access and transport infrastructures, doing such a good job that they have now been rewarded with the gift of commodity. Networks are capital-intensive resources, yet the revenues they yield for access and transport are in rapid decline—some would say free fall. They need help, and they need it now. The manufacturers are faced with a similar conundrum. Advances in semiconductor technology allow them to create entire systems on a chip that have the capability to process multiple disparate protocols. This almost seems too good to be true for both the embattled incumbent providers and the manufacturers. Here is a revenue formula that works! By building multiservice networks using lower-cost technology, hybrid solutions that serve a wide array of clients can be created. However, it’s a bit more complicated than that. In the first place, incumbent service providers lack long-term experience with multiservice, multiprotocol networks. Second, many of the companies that are designing and manufacturing the multiservice edge devices are new, unknown, not yet standardized, and lacking in one critical element: the trust of the marketplace. Finally, if the rollout of such an innovative and even radical new service offering is not handled well, it can further confuse the market, generating greater levels of distrust and discouraging investment. Perhaps an example is in order. Ethernet’s ascendancy to the role of heir apparent to the burgeoning metro broadband market is a great thing technologically, as is the early perceived success of such innovations as resilient packet ring and optical burst switching. However, as good as these solutions may be, they confuse the market as players ask questions about the relative viability of Ethernet versus legacy transport, SONET and SDH versus RPR, and the apparent functional universality of IP in the LAN, MAN, and WAN.
Cisco’s Central Role In 1998, Cisco Systems acquired Cerent, a manufacturer of ADMs targeted at the optical network. Cerent’s charter, described in a press release issued Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
32
at the time of the acquisition, was “to provide next generation SONET ADM equipment that is a fundamental building block in voice and data networks and used to add and remove lower speed traffic from higher speed optical rings. Service providers will use Cerent’s product in the access portion of networks.” These boxes provided transport for both voice and data services, one of the first realized examples of technology convergence, and a compelling reason for Cisco to acquire them. Companies in the industry began to refer to these boxes as multiservice access platforms, a name that soon gave way to multiservice access devices. Because of their multifunctional architecture, these systems are less costly, less power-dependent, and have a smaller footprint than their predecessors—critical issues for competitive providers that must work within the confines of a collocation environment. They are designed to seamlessly offer both transport functions and higherlevel service. They can do this because of the capabilities of new chipsets that incorporate multiple layers of functionality. Although ideal for the aggregation and transport of circuit-based traffic (voice, some data), traditional SONET/SDH ADMs do not lend themselves to the efficient transport of bursty packet data such as that generated by IP or LAN environments. By aggregating traffic at the edge from multiple sources, networks can be made significantly more efficient and cost effective. Consider the typical access network. Studies indicate that even in the enterprise data space, the local loop is woefully underutilized. As a full-time dedicated resource, this is a very expensive network component for both the customer and the service provider. If technologies exist to drive traffic into that loop to statistically increase its utilization, so much the better. Other factors are equally important. As functionality has moved from the core to the edge, certain key capabilities have benefited greatly from the shift. Some of these are described here.
Route Management The arrival of route control protocols like MPLS permits optimal route selection to be performed at the edge of the network instead of relegating the responsibility to core transport routers. This results in far more efficient network utilization but also yields a route choice—which in turn leads to redundancy and route diversity.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
33
Security Because enterprise firewall routers are typically standalone devices and by design are found between the private enterprise network and the public transport network, it only makes sense that the security function would naturally migrate from the core of the network to the edge and become the responsibility of the end user.
Data Archiving and Caching The growth and interest in SAN has driven interest in data access to the edge and beyond as ASP architectures have emerged that place the data stores beyond the realm of the network core. Additionally, IT planners have come to realize that if caching stores are designed into the network architecture that enable frequently accessed database records to be cached locally, the impact on the transport network can be reduced substantially. Instead of retrieving data from a remote location, the data is archived locally and retrieved from a cache server.
Policy Enforcement When policies are enforced from a centralized location (a network core), all traffic tends to be treated equally. When queuing and delay policies are established locally (at the edge), however, they tend to be customized to local traffic behavior patterns. Thus, the decision to enforce policy at the edge rather than at the core tends to make for a more efficient network.
VPNs Anytime a public network can be used to deliver secure private service, it should be done. VPNs enable a service provider to, in effect, “resell” the same physical network resource over and over again. VPNs are possible because of the capability of edge devices to “tunnel” through the public network infrastructure, creating a virtual dedicated channel for customer-tocustomer traffic.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
34
Of course, the multiservice concept does have disadvantages. First of all, the devices tend to be complex, which often leads to expense. Second, although the complexity of these boxes makes it possible for them to offer every service at every network location, every service isn’t needed at every network location. As a result, the service provider often pays for a capability that they do not require. Overall, however, the benefits of a multipurpose edge device far outweigh the liabilities of complexity and cost. As metro continues to evolve and grows to become a major market segment, the multiservice capability will become central to the success of all levels of the networking food chain, particularly for the service provider. Let’s stop for a moment and restate the advantage of this architecture. The service provider aggregates traffic via a single connection to a multiservice edge device. The customer enjoys low cost, low complexity, and a high degree of connectivity. In short, everyone wins.
The Metro Network: Access Access refers to the ability to connect to the resources offered by a metro network. As Figure 1-14 illustrates, any number of access options are available, including traditional dial-up, ISDN, DSL, cable modems, various forms of Ethernet, wireless, Frame Relay, and traditional dedicated private line such as T1 and E1. Keep in mind that access occurs at the edge of the network and that the edge is responsible for a number of functions, including traffic discrimination, concentration, QoS determination and enforcement, and protocol interworking. The edge is also the place where IP is first found in the network, because it is at the edge where other protocols are packaged for transport across wide area IP networks, the growing standard for network-to-network interconnection. Metro networks have only recently become a “standalone domain” within the hierarchy of network architectures. This “coming of age” of the metro space is a result of the natural evolution of both networks and the corporations that use them. During the past 20 years, corporate structures have evolved from centrally managed (and clustered) models to more distributed models. They have come to realize that to be competitive they must be physically located as close to their customers as they can possibly be, a philosophy that conflicts with the concept of a centralized business operation. Furthermore, they have found themselves affected by quality of life and
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
35
Figure 1-14 Access comes in many flavors, including wireless, DSL, ISDN, cable, and a variety of others.
environmental concerns such as the demand from employees to telecommute from home and Federal requirements such as the United States’ 1990 Clean Air Act. The Act attempts to reduce airborne pollutants, the corporate response to which has been to allow workers to work from home, thus reducing vehicle emissions overall. The result of this is that networks have had to evolve to ensure that employees of distributed corporations enjoy connectivity characteristics that are of the same quality they enjoyed when working at their single business location. The more or less simultaneous development of SONET and SDH, cost-effective ring architectures, and bandwidth management applications, combined with widely available and cost-effective high-speed access technologies, means that metro networking is effective and that it has helped to redesign corporate interconnection and communication models. Eight access technologies are the most successful in metro applications: 56 Kbps dial-up modem, ISDN, DSL, cable, Ethernet, wireless, Frame Relay, and private line.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
36 56 Kbps Dial-Up
Even though it is viewed as a true legacy solution, 56K dial-up access continues to be widely used, even by remote corporate employees. DSL, ISDN, cable, and wireless are not always available, so 56K continues to enjoy widespread use. The recent release of the V.92 modem standard, which improves on its V.90 predecessor by offering new services such as Quick Connect, Modem-on-Hold, and PCM Upstream.2
ISDN ISDN, sometimes referred to as “the technology that took 15 years to become an overnight success,” is now enjoying something of a renaissance because of the failure of some of its technology peers to perform. When DSL first arrived on the scene, it was viewed as the solution that would finally drive a stake into the heart of ISDN. However, because of deployment issues, performance problems, and availability limitations,3 DSL has been slow to succeed in many markets. As a result, ISDN has enjoyed a much higher uptake rate in the past 24 months. Even though it is limited to 128 Kbps (by bonding the two B-Channels into a single channel), it works, is internationally standardized, and is widely available at a (for the most part) reasonable price. Current compression technologies make 128 Kbps a reasonable solution for moderately bandwidth-intensive applications, including video.
DSL DSL, when available, is a very good access solution. With downstream bandwidth ranging from 128 Kbps to as high as 52 Mbps (depending on the version chosen), it offers a variety of access solutions for even the most
2
Quick Connect reduces the typical connect time by 50 percent or more by “memorizing” the line characteristics to reduce the length of successive handshake procedures. Modem-on-Hold enables a user to receive an incoming call while maintaining a previously established connection to the Internet. PCM Upstream increases the upstream data rate from 33.6 Kbps to a maximum of 48 Kbps, a 30 percent increase.
3
Bellsouth is the exception: In January 2002, they announced that the number of working installs of DSL (more than 620,000 in territory) had far exceeded their and the market’s expectations.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
37
bandwidth-hungry applications. Although it has enjoyed its greatest success in the residence marketplace, it is also widely used for corporate interconnections. For example, ISPs often use DSL as the backbone connector between their router pools and the Incumbent Local Exchange Carrier (ILEC) access network. This is a technology that will continue to grow in importance; watch it closely.
Cable Cable is a bit out of place in the context of enterprise access, but because it represents a viable broadband access solution for the small office, home office (SOHO) and telecommuter, it would be irresponsible to ignore it as an option. Cable offers asymmetric access, with a far higher downstream channel (roughly 1 Mbps) than its upstream counterpart. This design stems from historical usage; most cable modem users download large files from web servers using relatively small upstream commands that yield massive amounts of graphics-heavy content downstream. As home workers become more common, however, this model may begin to show its limitations as their requirements to upload large files grow. Remember also that cable is a shared downstream medium. The more users that share the channel, the less bandwidth is statistically available for each user. Thus, it suffers from its own success in the market.
Ethernet In the enterprise access domain, Ethernet has gained a degree of notoriety among its various access technology peers by effortlessly morphing into multiple forms as the demand for different solutions has evolved. Originally conceived as a 1 Mbps LAN data-link-layer protocol, Ethernet has expanded beyond both the LAN world and its multimegabit limitations.4 Such companies as Telseon, Yipes, Atrica, and others are now deploying Ethernet as a transport solution largely because of its popularity, simplicity, availability, and bandwidth. Ethernet is now available in 10 Mbps, 100 Mbps
4 A word about nomenclature: Ethernet is actually the name coined by Bob Metcalfe in 1976 for his concept of a distributed packet network architecture—for all intents and purposes a product name. The technology (protocol) that defines Ethernet is called Carrier Sense, Multiple Access with Collision Detection (CSMA/CD).
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
38
(Fast Ethernet), 1 Gbps (Gigabit Ethernet), and 10 Gbps versions. When deployed as a point-to-point transport option, Carrier Sense Multiple Access with Collision Detection (CSMA/CD) is not used, because no collisions must be managed. CSMA/CD manages the shared medium by detecting and correcting collisions that occur when two stations transmit simultaneously.
Wireless Wireless access is, in fact, another option that has resulted from the limitations of wired alternatives. The two most successful options today are the Local Multipoint Distribution Service (LMDS) and the Multichannel, Multipoint Distribution Service (MMDS). LMDS operates in the 28 to 31 GHz band, while MMDS operates in the 2.5 to 2.7 GHz range. LMDS offers 155 Mbps over distances of up to 10 miles, while MMDS offers a much lower 10 Mbps, but over a distance of up to 35 miles. Equally important has been the success of 802.11b, the 11 Mbps wireless Ethernet standard that also goes by the name of Wi-Fi (for Wireless Fiber or Wireless Fidelity.)
Frame Relay Frame Relay seems to have dropped off the face of the earth in many cases; it just isn’t discussed much anymore. Nevertheless, it continues to sell well as a switched alternative to dedicated private line. The primary advantage it offers over private line is its pricing algorithm; no distance component is included in the scheme, which means that Frame Relay offers distanceinsensitive pricing. Under normal circumstances, this would not be an issue in metro environments, since most distances are relatively local. The breadth of metro areas, however, is beginning to blur a bit. In the Los Angeles market, for example, it is not uncommon for a metro network to require runs of as far as 80 miles, a distance that could result in a prohibitively expensive circuit when price is based on circuit miles. Frame Relay also offers access speeds ranging from 56 Kbps to 45 Mbps.
Private Line Of course, a market for dedicated private line still remains. The price of a T1 or E1 has plummeted in recent years; a circuit that cost $45,000 per year
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
39
five years ago costs $4,000 today. The result is that the popularity of dedicated facilities, particularly given renewed concerns about security, has gone up as the price for such circuits has gone down. Metro access options will continue to diversify in response to growing requirements for bandwidth and QoS guarantees from an increasingly demanding customer base. The metro network space itself will continue to evolve in lockstep with the corporations that make use of its capabilities and will be called upon to carry a growing diversity of application content to the transport network.
Anatomy of the Metro Network: The Core Core devices, on the other hand, operate within the transport region of the metro network and are responsible for carrying out the service requests that originate within the edge domain—specifically the high-speed transport of data packets. Devices found here include large IP routers, ATM switches, and hybrid platforms that include MPLS and other newer protocol suites. Within the metro environment, transport refers to the process of moving traffic from one node in the metro network to another, but always within the metro space. For example, a corporation might have multiple business locations within a metropolitan area, all of which must be interconnected to provide intra-enterprise transport that is seamless, application independent, and completely transparent. The characteristics of such a multipurpose transport network are “unlimited” bandwidth, rapid provisioning of bandwidth to users, and QoS awareness. QoS awareness simply means that the network is aware of the fact that different applications place varying demands on network resources and is able to adjust to and satisfy those demands in real-time or near real-time. Early metro transport networks relied on legacy copper infrastructure for the most part, although some microwave was also used for building-tobuilding interconnections. As bandwidth demand grew and the diversity of bandwidth-hungry applications and numbers of users climbed, copper began to show its limitations as a transport option. It is still used for some applications (“If it ain’t broke, don’t fix it”), such as simple multichannel voice installations for private branch exchange (PBX) networks, but for data and multimedia transport it no longer suffices.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
40
Beginning in the mid-1980s metropolitan fiber networks began to appear, thanks largely to the efforts of such companies as Metropolitan Fiber Systems (MFS, now part of WorldCom) and Teleport Communications Group (TCG, now part of AT&T). These companies came into existence with the sole intention of competing with the incumbent providers by building dual-entry optical rings throughout metropolitan areas and selling services on the value of their support and survivability. The model they established is the most widely accepted model today and the basis for most carriers’ metro networks. The fact that their networks were dual-homed, meaning that all served buildings were connected to both the primary and secondary ring, which in turn entered the buildings from two separate sides of the building (route diversity), meant that service interruptions were almost nonexistent. This ring architecture is primarily SONET- or SDH-based today, although other architectures have recently emerged. SONET and SDH networks typically comprise two rings that transmit in opposite directions. In the event of a failure of the primary ring, a switchover occurs to the secondary ring, which then carries all live traffic. The switchover takes place within 50 milliseconds and is transparent to the user. If both rings are breached, the ring reconfigures into a toroidal shape, losing its capability to survive another fiber cut but preserving the capability to transport traffic. Ring topologies will be discussed in greater detail later in the book. SONET and SDH have found themselves under fire of late as some network professionals have tried to relegate them to the boneyard of legacy technologies as newer technologies have arisen. One commonly heard complaint is the perception that SONET and SDH are overhead heavy, particularly when operating in concatenated mode. True enough, but that overhead is highly functional and so far nothing new has come along that offers such a complete package with less overhead required to do it. New technologies have arrived, however, and they are enjoying some degree of success. One of these comes to the table from Cisco and is called the Spatial Reuse Protocol (SRP). SRP enables devices such as routers to be interconnected by dual fiber rings using SONET and/or DWDM. The rings offer redundancy and operate at 10 Gbps with a ring-to-ring switchover speed of less than 50 milliseconds. In MANs, SRP dramatically lowers the cost of network deployment for corporations or ISPs looking to interconnect multiple sites by eliminating the need for an expensive ATM switching infrastructure. The one thing SRP does not adequately offer today, however, is a well-defined strategy for QoS, something ATM does extremely well.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
41
Nevertheless, SRP has found a home in the optical world because of its use in RPR, mentioned earlier. RPR is a network transport scheme for fiber rings. The IEEE began the 802.17 RPR standards project in December 2000 with the intention of creating a new MAC layer that offers the same protection capabilities that SONET and SDH make possible, without the overhead. Fiber rings are widely used in both MAN and WANs; these topologies, unfortunately, are dependent on protocols that are not scalable for the demands of packet-switched networks such as IP. The 802.17 RPR working group promotes RPR as a technology for device connectivity. Issues currently being addressed are bandwidth allocation and throughput, deployment speed, and equipment and operational costs. Both RPR and SRP will be discussed in greater detail later in the book.
Optical Burst Switching A related technology is optical burst switching (OBS). OBS supports realtime multimedia traffic across the Internet, a natural pairing since the Internet itself is bursty. OBS is particularly effective for high-demand applications that require a high bit rate, low latency, and short duration transmission characteristics. OBS uses a “one-way reservation” technique so that a burst of user data, such as a cluster of IP packets, can be sent without having to establish a dedicated path prior to transmission. A control packet is sent first to reserve the wavelength, followed by the traffic burst. As a result, OBS avoids the protracted end-to-end setup delay and also improves the utilization of optical channels for variable bit rate services. By combining the advantages of optical circuit switching and those of optical packet or cell switching, OBS facilitates the establishment of a flexible, efficient, and bandwidth-rich infrastructure.5 Another transport technology that has come booming into the forefront of technologists’ minds in the last year is Ethernet. Although positioned as an alternative to SONET and SDH, it is important to remember that
5
For more information about RPR, please visit the 802.17 Alliance Web site at http://grouper. ieee.org/groups/802/17/. For information about OBS, please see the article posted at the Light Reading Web site at www.lightreading.com/document.asp?doc_id⫽9016&page _number⫽8.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
42
SONET and SDH are physical-layer (layer one) protocols, while Ethernet (CSMA/CD) encompasses layer two as well. SONET and SDH are transmission technologies; Ethernet is a framing and switching technology.6 Ethernet can be deployed as a transport technology and can certainly be transmitted over optical fiber, even carried over SONET and SDH. What it brings to the transport world is simplicity, low cost, scalability, and broad acceptance and understanding. What it lacks, and what SONET and SDH offer, is protection, resulting in QoS preservation. This is the reason that 802.17 and the not-yet-mentioned X.86 standards are so important. 802.17 provides the means to deliver the robustness and survivability typically available only in SONET/SDH rings via Ethernet, while X.86 offers a standard scheme to map Ethernet frames into SONET/SDH transmission streams. So what does this mean? It means that SONET and SDH are not going away any time soon: Too large an embedded base has been established for that to happen. It does, however, mean that for the near term, we will continue to see side-by-side coexistence of Ethernet with SONET and SDH, particularly in the metro network domain.
Freespace Optics Another technology that should be watched is freespace optics. Freespace optical solutions rely on open-air laser transmission between buildings to create low-cost metropolitan networks. Most industry estimates today claim that more than 80 percent of all business buildings are not served by fiber. Freespace optics, therefore, would seem to be a good alternative solution and can be used as mesh alternatives. Several companies have entered the freespace game, including AirFiber with its 622 Mbps OptiMesh™ product and Terabeam, which provides wireless optical-like connectivity at 5, 10, and 100 Mbps. Both companies offer high degrees of survivability and reliability.
6
We should note here that although Ethernet is used today as a transport technology, CSMA/CD is not. When Ethernet is deployed for transport, only its simple data-framing structure is used: Neither collision management nor the other media management capabilities of the protocol are used.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
43
Asynchronous Transfer Mode (ATM) Although many criticize ATM as an overhead-heavy legacy solution, it continues to be installed at a steady pace around the world because of its capability to assign and maintain guaranteed levels of service quality at all levels of the network—local, metro, and wide area. It is a comparatively expensive solution, but when customer service quality is at risk, cost becomes less important. Commonly seen in wide area installations, ATM has begun to show up in the metro environment as well. Its price point is dropping, making it more palatable to network designers. IP is also popular because of its universality, but typically only when transported by another protocol capable of preserving QoS.
Metro Topologies Within the metro domain, three network topologies or architectures have emerged that are vying for a place at the technology table: point-to-point, ring, and mesh. Each of these have advantages and disadvantages, including design challenges, installation issues, the capability to monitor and survey the overall network (or not), and concerns over engineering complexity and design. Because all three of these topologies will be evident in our studies of the metro network throughout the book, we will discuss them briefly here.
Point-to-Point Architectures Point-to-point physical networks are cost effective under certain circumstances such as short-reach installations (as many metro network segments are) and where the single span of the circuit can be enhanced through the use of DWDM as a way to provide bandwidth multiplication. In many instances, companies already have dedicated facilities in place; as long as they provide adequate bandwidth and offer redundancy through carefully laid-out network plans, they will continue to suffice.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
44
Ring Architectures As we mentioned earlier, rings represent the current topological standard for metro networks, although that preference is shifting in favor of alternative approaches. Rings have been in widespread use since the mid-1980s when SONET and SDH first made their way onto the networking scene. Today, rings are commonly used because of the enhanced survivability that they provide. Ring problems can be caused by electronic failures, digital cross-connect and multiplexer database failures, internal power failures, aerial cable failures, and, of course, the infamous “backhoe fade” that results from an underground cable cut. The first three are difficult to protect against, although hardware designers typically build in component redundancy to reduce the chances of a device-related failure. More than 75 percent of all optical network failures, however, result from fiber breakage, either aerial or underground. As a result, anything that can be done architecturally to protect against physical network disruption will go a long way toward ensuring the survival of the overall network. The most common solution is to deploy redundant paths in the most critical spans of the network, and this is most commonly done using ring topologies.
The Unidirectional Path-Switched Ring (UPSR) The unidirectional path-switched ring (UPSR) is comprised of two fiber rings interconnecting the add-drop multiplexers that make up the network connectivity points. One fiber serves as the active route, while the other, which transmits in the opposite direction, serves as a backup. In the event of a fiber failure between two adjacent nodes, the SONET or SDH overhead bytes convey the failure information from device to device around the ring, one result of which is that the traffic is switched to the backup span within 50 milliseconds. The backup span then carries the traffic, this time in the opposite direction, ensuring the integrity of the ring. Unfortunately, this architecture results in a problem. Consider the ring shown in Figure 1-15. Under normal operating conditions, traffic flows from node one to node two to node three and so on. Traffic going from node two to node three only has to traverse a single hop. The other direction, however, is a very different story. Traffic from node three to node two must traverse a four-hop route, resulting in an asymmetric two-way transmission path. For geographically small rings, this is not a problem. For larger rings, howDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
Figure 1-15 Normal traffic flows in an optical ring
45 2
1
3
4
ever, it can be a significant problem because of synchronization and latency concerns. For example, an application, expecting symmetric transmission and reception, might adjust its timers for equal arrival and departure rates. If it does this, however, it will see data constantly arrive early, while the other end will see it arrive late—or vice versa. Clearly, a better solution might be in order.
Bidirectional Switched Rings Four-fiber, bidirectional switched rings eliminate the asymmetric problems that characterize unidirectional two-fiber rings. These bidirectional rings can be engineered in two ways: as span-switched rings or line-switched rings. Both provide high degrees of protection for data traveling on the ring, and both send traffic bidirectionally to ensure symmetrical delay in both transmission directions. Span-switched rings recover from span failures by switching the bidirectional traffic on the active pair of fibers to the backup pair, but only between the nodes where the failure occurred. This is clearly a better overall design than the two-fiber UPSR, although it does have one common failing: All too often the active and backup fiber pairs are found in the same
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
46
conduit, which means that a truly diligent backhoe driver will take down the ring by cutting all four fibers. An alternative that offers better survivability is the bidirectional lineswitched ring (BLSR). These are complex architectures that require significant bandwidth management and control. In a BLSR, half the traffic is sent on the clockwise ring, while the other half is sent on the counterclockwise ring. This results in a much more efficient use of bandwidth and significantly improved performance. If all four fibers are cut between two adjacent nodes, both the active and the protect paths wrap to preserve the integrity of the ring and the data that it carries. Thus, the BLSR is the most popular configuration in the SONET world, although UPSRs are still more common outside of North America. In fact, four-fiber BLSRs (4F BLSRs) are often seen deployed for long-haul applications and are usually diversely routed as additional protection against physical failure. Even in the United States, where four-fiber rings have been the norm for some time, two-fiber rings (2F BLSRs) are becoming more common. Table 1-1 outlines the characteristics of the three different ring types.
The Two-Fiber BLSR Option Within metropolitan areas, the 2F BLSR has become a common deployment alternative. It guarantees survivability by “gerrymandering” the available bandwidth. Signals are transmitted on both fibers simultaneously. Each multiplexer on the ring is configured to seek its primary signal from one ring or the other, and each span between multiplexers carries the config-
Table 1-1 UPSR, 2F BLSR, and 4F BLSR
Characteristic
UPSR
2F BLSR
4F BLSR
Delay
Asymmetric
Symmetric
Symmetric
Deployment
Metro
Metro
Long-Haul
Multiple failure protection
No
No
Yes
Initial cost
Medium
Medium
High
Augmentation cost
Low
Medium
Low
Complexity
Low
High
Medium
Efficiency
Medium
Medium
High
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
47
ured capacity for both active and protect traffic to ensure bandwidth availability in the event of a catastrophic failure of the ring. This particular model has become more and more common.
Mesh Architectures Mesh networks are defined as networks in which every node on the network is connected to every other node by a collection of point-to-point links. These networks can be partially meshed, as shown in Figure 1-16, or fully meshed, as shown in Figure 1-17. The choice of partial or full-mesh connectivity is a function of desired survivability levels, the nature of the data to be transported, and cost. Full-mesh networks are expensive to deploy but yield the greatest amount of redundancy for obvious reasons. The primary advantages of mesh topologies are twofold: first, they enable all connected users access to all the available bandwidth in the network, and second, routes across a meshed network can be configured rapidly. After all, a meshed network is really nothing more than a collection of nested ring networks, as shown in Figure 1-18. As a result, they offer the advantages of
Figure 1-16 A partially meshed network
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
48 Figure 1-17 A fully meshed network
both point-to-point and ring architectures. Thus, all the desired characteristics, such as service deployment speed, redundancy, robustness, least-cost routing, and flexibility, are available in a single topological design. The decision to use rings versus meshes in the metro network largely takes place in discussions about the core of the metropolitan network. After all, the capability to have redundant routes between nodes is primarily a metro transport issue that affects cost and service availability. Meshes are deployed primarily in the core, while rings are found more commonly today at the network edge, serving as traffic aggregation paths for the various access devices (add-drop multiplexers) that connect enterprise end users to the metro backbone. The access environment typically has less deployed fiber than the transport core, so access rings are cost-effective solutions since they can be shared among many different users. It is interesting to note that a gradual migration to mesh topologies is beginning to appear among the long-term incumbent network players. They recognize that deployment speed and accuracy are critical differentiators in their ever more competitive world; the capability of mesh networks to be dynamically, rapidly, and accurately provisioned is a powerful advantage that is not lost on the major competitors. Of course, there will continue to be
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
49
Figure 1-18 Nested rings
a place for both ring and mesh topologies. In the long term, however, meshes will most likely predominate. Mesh topologies are typically encountered in WANs because they can easily be deployed in that environment. They are not typically seen in metro environments, but that, however, is changing. Because of the complex route diversity that mesh networks offer, they are beginning to be taken seriously in metro networking. They are extremely flexible and after all are really nothing more than an interlaced collection of point-to-point connections that can be managed as a series of interconnected rings. They offer higherspeed provisioning, much better use of available bandwidth (since all users have access to all bandwidth with nothing reserved for failure compensation), and no restrictions on topology or growth. They enable network managers to perform highly granular traffic engineering from any point on the network to enable the high-speed provisioning of services.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
50
The most common mesh medium is optical fiber, although T1, E1, and other Plesiochronous Digital Hierarchy (PDH) technologies are also used. Traditional microwave has long been used in cities for point-to-point interconnections, although it is typically a second choice due to its susceptibility to environmental fade, its licensing requirements, and its tendency to quit working when a building sprouts up in the middle of the shot. Watch closely: Mesh metro networks will become much more widely deployed in the months ahead.
Summary Let’s go back and review the origins and characteristics of metro networks. In the enterprise domain, a number of factors have emerged that drive the demand for metro networks. First, there has been a great deal of growth in the use of intracorporate networks, the so-called intranet model. Second, demand for bandwidth from complex applications has also grown exponentially. Consider, after all, the graph shown in Figure 1-19. Voice growth is relatively flat, while data growth is aggressive. Broadband has become a high-demand concept, including the various forms of DSL, fiber-to-thewhatever, and so on, and the demand for it is becoming as common in the metro space as it is in other network regions. Applications, too, have
Figure 1-19 Voice versus data traffic growth
Data
Voice
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
51
emerged that drive demand for bandwidth. These include SANs, Ethernet LAN-to-Ethernet LAN interconnections, and growing concerns about survivability, redundancy, robustness, and disaster recovery/avoidance. The demands of the evolving marketplace include the preservation of legacy applications, route redundancy, network protection, rapid and accurate provisioning, and intelligent traffic distribution. In short, legacy access and transport technologies (Ethernet, Fibre Channel, T1/E1, and SONET/SDH) when overlaid with such demands yield the characteristics required in a metro network. Consider Figure 1-20, which details the architecture of the traditional metro network. At the lowest layer, we find the long-haul and regional transport capabilities that typically operate at high bandwidth—nominally 10 Gbps (OC-192/STM-64), perhaps faster. Known as the long-haul optical core, this network segment is designed for the high-speed transport of massive amounts of largely undifferentiated data. The next level up in the hierarchy is where we find the metro edge and metro core. Here we find transport options, including Fast and Gigabit Ethernet, DS3, and some SONET/SDH transport. As the name implies, this is where metro aggregation and transport occur. In this region, we find redundant optical rings interconnecting enterprise locations. Finally, at the highest level of the network hierarchy, we find metro access. These technologies include a wide array of transport options from 64 Kbps DS0 to 155 Mbps OC-3/STM-1. Access includes passive optical network connections, SONET/SDH rings, and rings made up of ATM switches that provide aggregation services. So what are the general characteristics of a typical metro network? First, it must be cost effective. It must be relatively inexpensive to deploy and equally inexpensive for the end user. After all, it touches the customer’s
Figure 1-20 The typical metro network environment showing subtending rings
IP
PSTN LD PoP NxOC-48/192 or NxSTM-16/64
Metro Core Ring Access Rings
NxOC-48 or NxSTM-16 ATM IP
TDM
ATM
TDM IP
ATM
TDM IP
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Part 1
52
premises network, which is probably low-cost Ethernet, and the long-haul network, which in today’s marketplace is equally low cost. Next, the metro network must be designed so that adequate bandwidth is available to avoid blocking and delay problems. Some blocking and delay are normal, anticipated, and, contrary to popular belief, required to serve as cost control (metering) parameters. After all, if bandwidth is perceived by the user community to derive from a bottomless barrel, they will behave accordingly and will give precious little consideration to the very real need to conserve bandwidth. Next, a metro network, because it straddles the line between the end user and the network over which the user’s traffic will be transported, must be able to offer differentiable levels of QoS to accommodate the many different cost, performance, and service requirements that customers will clamor for. A metro network must be scalable for the simple reason that the environment it serves will grow and evolve. Metropolitan areas change constantly as they expand, contract, and absorb suburban areas. As a result, a metro design must take into account the fact that the network will change and must therefore be built with that eventuality in mind. Furthermore, for economic reasons, the network should be designed to reuse the existing infrastructure to the degree possible, as long as it is not at the expense of service quality. Given the Byzantine depreciation schedules that service providers are often required to abide by for their capital acquisitions, any design that enables in-place capital assets to be fully depreciated will have a sincere advantage over those that fail to take this factor into consideration. Next, and perhaps most important, the network must be able to survive physically disruptive events. If a router fails, a switch dies, or a fiber route becomes unusable due to a cable cut, the metro network must be able to simply shrug its shoulders, consider a list of options, and continue with business as usual. Finally, the metro network must be protocol, service, and application independent. Agnosticism is an important construct in modern networks because it speaks to the ongoing convergence phenomenon. Service providers have a strong desire to simplify and therefore reduce the cost and complexity of the network infrastructure they must operate, administer, maintain, and provision. Any design that makes it possible to transport multiple complex traffic types across a single, converged network infrastructure without impact on the end-to-end service quality will be richly rewarded. Consider, for example, the plethora of interfaces and protocols that service providers must contend with. A modern network must be able Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
A Lesson in Medieval History
53
to interoperate with the following interfaces (and this is by no means an exhaustive list): ■
300 bps Teletype (TTY) (yes, it’s still around)
■
300 to 1200 bps telemetry
■
9.6 Kbps lottery/ATM machine
■
14.4 to 56 Kbps asymmetric dialup data access
■
56 Kbps symmetric dialup data access
■
64 Kbps TDM voice
■
128 Kbps bonded ISDN
■
128 to 512 Kbps video and DSL
■
1.544 to 2.048 Mbps T1/E1
■
45 Mbps to 40 Gbps optical interfaces
That same network must be able to handle a wide variety of protocols, including Phase Shift Keying (PSK), Differential Phase Shift Keying (DPSK), Frequency Shift Keying (FSK), Amplitude Shift Keying (ASK), Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (QAM), Discrete Multi-tone (DMT), Carrierless Amplitude/Phase modulation (CAP), I.430, Synchronous Data Link Control (SDLC), Link Access Procedure for the D-Channel (LAPD), Q.931, IP, Link Access Procedure to Frame Mode Bearer Services (LAPF), Q.921, ATM, SONET, SDH, Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile Communications (GSM), CDMA, 802.3, 802.5, 802.11, and a host of others. Keep in mind that the network becomes far more diverse and heterogeneous as it gets closer to the customer, and since the metro network often serves as the aggregation point for user traffic before it is classified and handed off to the core, it must be able to handle a wide variety of traffic types and physical interfaces. Because of the infrastructure that is becoming most common in the metro environment, these networks are often referred to today as Metro Optical Networks (MONs). Optical technology has long been considered a transport option for subsea cables and transcontinental networks because of the enormous bandwidth required for coast-to-coast call volumes. Today, because of the burgeoning bandwidth requirements of multimediaenhanced applications, that same capacity is in demand by metro customers. In Part 2, we begin with a discussion of the MON world.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
A Lesson in Medieval History
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Source: Metro Area Networking
PART
2 The Metro Network
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
56
In this part, we explore the evolution and development of metropolitan networks with a focus on metropolitan optical networks (MONs). As we will see, “metro” means different things to different constituencies, so we will make every effort to clearly define the network region where we find metro deployments.
What Is a Metro Network? As the Internet continues to grow in chaotic and unexpected ways, and as the Internet user base becomes more technologically informed and focused on applications, those very applications undergo innovative evolution as they place growing demands on the network for very high speed, scalable, flexible, and protocol-transparent bandwidth services. At the same time, advances in Dense Wavelength Division Multiplexing (DWDM) technology are allowing new network models to be created. Once found only in the long-haul network, DWDM is now evolving so that it provides tremendous bandwidth granularity in the metropolitan and access networks. The result of DWDM’s incorporation in the metro has caused the industry to refocus on applications, with a goal to offer the same benefits in that environment as those that have long been available in the long-haul space. The current literature defines MONs as those that provide connectivity and transport to large metro areas that have a high concentration of business customers and that span distances of no more than 10 miles. As we stated before, they provide the bridge between the long-haul environment and the access environment, and interconnect a wide array of protocols from both enterprise and private customers on access networks to diverse backbones. This seeming disparity of functionality results in a remarkable collection of design, engineering, and deployment challenges due to several factors: the significant installed base of Synchronous Optical Network/ Synchronous Digital Hierarchy (SONET/SDH) that is common in existing metro area networks, the functional and performance disparities between the access and transport interfaces, and the need to incorporate new technologies and services while protecting legacy offerings, most notably those based on traditional Time Division Multiplexing (TDM) technologies such as T1/E1 and SONET/SDH. These networks were created to transport a relatively limited collection of traffic, specifically voice and private-line services. Those services, largely
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
57
point-to-point in nature, dominated the technology base for a very long time, but as the metro marketplace began to emerge as a viable standalone entity, they began to show their limitations. The need arose to simplify the network and make it more flexible and quickly provisional because of the nature of the metro customer. At the same time, these networks had to provide volumes of bandwidth, and that bandwidth had to be available more or less instantaneously. T1/E1 certainly offered bandwidth, although SONET and SDH offered vastly more. The problem with SONET and SDH was that although they offered bucketloads of bandwidth, they were not flexible nor were they efficient. The solution lay in the so-called multiservice optical network, which gave service providers the ability to accomplish all the requirements just mentioned: quick provisioning, accurate billing, flexible deployment, low-cost solutions, and greater network intelligence. All three service regions of the metro marketplace—the service provider, the customer, and the hardware manufacturer—benefit from the migration to the all-optical metro network. The opportunities to provision new customer groups and to offer diverse classes and quality of service (QoS) are rich and to a large extent untapped today. Some players are succeeding in the metro market because they have figured out the relationship between technology and the services made possible by the technology and have directed their efforts accordingly. Those that understand that customer-oriented services drive revenues far more than readily available bandwidth are well positioned, whereas those that have made technology plays without well-thought-out application and solution plans are in peril. Some have already fallen; others will undoubtedly follow. Others are enjoying growing revenue streams and will continue to do so. Companies that create well-targeted, timely, and cost-effective solutions delivered over mesh optical metro networks that support a variety of revenue-generating services will enjoy longevity from the long-term interests of broad service provider markets.
Metro Touch Points Metro networks sit squarely between the long-haul and access regions of the overall network, as shown in Figure 2-1. We will examine each of these segments because in some ways the lines of functionality between them blur, making it difficult to determine where one ends and the next begins.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
58 Figure 2-1 The networking hierarchy. Metro serves as an intermediate region between core and access.
Long-Haul Networks Service providers with national or global scope typically provision long-haul networks. Their networks range from regional (tens of route miles) to global (thousands of route miles) and are used to interconnect disparate metro networks as a way of providing multinational connectivity among a group of regional networking domains. Historically, their principal differentiator has been transport capacity (megabits of provisionable bandwidth) as measured by the capabilities (and limitations) of the underlying transport technology—typically SONET or SDH. To deal with the problems of fiber (and therefore bandwidth) exhaust, most large carriers have deployed DWDM as an effective bandwidth multiplication technique. The high labor cost involved in the provisioning of long-haul fiber cables resulted in a significant degree of interest in DWDM when it was first announced. DWDM enabled service providers to augment available bandwidth by adding channels rather than by adding fiber, resulting in enormous cost savings. The problem is that as the channel count on a single fiber strand increases, a variety of transmission impairments—crosstalk, if you will—arise and get worse as the channel count climbs. Optical engineers have created clever techniques for dealing with these impairments, including chemically enhanced fibers, optical amplification techniques, and more powerful lasers. Eventually, however, if the distance is too great or too much amplification takes place (resulting in amplified noise along with the Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
59
desired signal), the optical signal must be converted to electrical, cleaned up, regenerated, converted back to optical, and retransmitted. This complexity translates into a significant expense, the result of which is that service providers contemplating the installation of a long-haul optical network treat it as a strategic, long-term investment. Because of technology innovation, however, long-haul networks are growing in capacity and migrating toward terabit core architectures based on high channel count DWDM. Soon they will offer an additional layer of intelligence that will incorporate wavelength switching and routing, differentiable QoS, and survivability guarantees.
Access Networks As the name implies, access networks are found at the edge of the MON and typically support a wide array of protocols. Access network bandwidth ranges from subrate services such as DS1, DS3, OC-3/STM-1, OC-12/ STM-3, 10 Mbps Ethernet, and 200 Mbps Enterprise System Connectivity (ESCON) to higher-speed services such as OC-48/STM-16 and OC192/STM-48. The customers for these services are as far ranging as the services themselves: residential Internet users, small office/home office (SOHO) subscribers, telecommuters, small businesses, large corporations, government agencies, and educational institutions. To support the requirements of such a diverse customer base, these access networks must support a significant number of applications, which in turn require a significant number of access protocols. These include the Internet Protocol (IP), Asynchronous Transfer Mode (ATM), SONET/SDH, Ethernet, Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet, traditional TDM voice, digital video, Fiber Distributed Data Interface (FDDI), Enterprise System Connection (ESCON), Fibre Channel Connectivity (FICON), and Fibre Channel. The optical metro market segment is a dynamic, chaotic, and potentially lucrative opportunity for the service provider willing to make a play there. It is driven by evolving end user applications based on high-speed access to databases and high-speed access technologies such as Digital Subscriber Line (DSL), cable, fixed wireless, and, eventually, third generation (3G). Although the number of transported protocols is large and growing, one fact is key: IP as the protocol of choice is becoming more and more obvious. Because IP is bursty and asymmetric, and it sports a naturally unpredictable behavior, its use poses special challenges to service providers accustomed to the naturally well-behaved nature of the Public Switched Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
60
Telephone Network (PSTN). Furthermore, new applications have emerged that place large and unpredictable loads on existing networks, including local area network (LAN)-based videoconferencing, telemedicine applications, Webcasting, and Integrated Services Digital Network (ISDN)-based videoconferencing. Others will emerge over time, and the one characteristic they will share is a growing hunger for bandwidth. Two key forces drive access networks: evolving applications with diverse service-quality demands and a range of network architectures. Equally important is transparency, otherwise known today by the much overused term protocol-agnostic. From a service provider’s point of view, transparency is perhaps the most important characteristic of metro networks because it guarantees the ability to build multiprotocol networks. A phenomenon exists that is well known among electrical engineers called skin effect. Skin effect speaks to the fact that current does not flow in the core of a conductor. Instead, it flows on the surface, because of the reduced electrical resistance due to the far greater surface area there. This is why stranded wire is a greater conductor than solid: the multiple strands of wire provide enormously greater surface area than a single solid conductor. The analogy works well in our discussion of metro networks: Far more “market opportunity surface area” is available at the edge of the network cloud than there is at the core, and although the core marketplace continues to be important, the opportunities, the growth, and the money lie at the edge. As we discussed in Part 1, “A Lesson in Medieval History,” the industry has segmented itself into functional layers that satisfy the changing demands of a diverse application set. A food chain is at work through which the various players combine their efforts in a form of value-added service to satisfy customer demands. The collective efforts of the various manufacturing layers and those of the service providers result in the foundation of what is required to create value for the customer. That value derives from reliable hardware, capable software, targeted applications, and a focus on the customer’s value chain.
The Metro Area Itself Metro networks move traffic within the metro domain, to and from business locations, interoffice facilities, and long-haul network provider points of presence. They are driven both by changing customer requirements and the technology required to support them. They also offer a variety of networkDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
61
ing protocols and bandwidth to match those offered by the access region of the network. Because it is what they know best and have most widely installed, service providers use SONET or SDH for metro transport, relying on either point-to-point connectivity or add-drop multiplexer (ADM) ring architectures. These connections are either permanently or semi-permanently connected and range in bandwidth from OC-3/STM-1 to OC-48/STM-16. Because of the complex structure of SONET/SDH, equally complex mappings are required to encode protocols into SONET/SDH frames. Keep in mind the conditions under which SONET and SDH were created: It was a time of telephone monopoly, when traffic largely comprised voice with a bit of data mixed in for color. Networks, traffic, protocols, and applications were far simpler back then than they are now, and the rigid framing structure of legacy SONET and SDH was perfectly fine for the limited requirements of the traffic of the time. As networks and the traffic they move have evolved, however, it has become clear that SONET or SDH do not offer the efficiencies necessary for these evolving networks. Furthermore, because of their rigid framing structures, SONET and SDH do not offer flexible service definitions and suffer from long provisioning cycles.
The Evolving Metro Network Applications, bandwidth, protocols, QoS, flexibility, service diversity—these drivers are growing and changing in response to the evolving metropolitan environment, which in turn is shifting in response to significant changes in the access and long-haul regions of the network. For example, the remarkable growth in DWDM channel capacity, combined with the dramatic rise in the use of IP in the access domain, has brought sharp focus on metropolitan networks and has made the region fiercely competitive. And although demands have gone up and competition has grown rapidly, the existing legacy TDM infrastructure offers a variety of challenges for service providers looking to meet the efficiency, scalability, and flexibility requirements of customers. Customer demands have also grown more compelling over time. As applications have evolved, enterprise customers have demanded more and more bandwidth, ultimately rising to demands for OC-48 (STM-16) connections that terminated at the business location on the back side of large IP routers and ATM switches. This was unheard of; line speeds at this level of bandwidth had never been demanded before. Furthermore, it became Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
62
somewhat clear to service providers and manufacturers alike that the distinction between the access and metro domains of the network were beginning to blur. To address this ongoing functional evolution, a migration to a scalable, high-capacity architecture was needed for the network. As it dawned on service providers and manufacturers that a key differentiator among competitors was QoS, the functional components of QoS became crucial: bandwidth on demand, service-level differentiation, cost, transparency, and rapid provisioning. It was clear from the beginning that SONET and SDH could not offer these characteristics at the levels required to maintain a competitive position in the metropolitan area network (MAN). As demand grew and tension among the players increased, it became clear that metro-based DWDM was a reasonable solution for the provisioning of high bandwidth. By adding multichannel transport to MONs, service providers found that they could offer flexible, manageable, scalable, protocol-independent services that were also cost effective. This represented the creation of true multiservice optical networks (MONs). Most metro players have already made the leap to DWDM, and those that remain will be forced to do so eventually, because DWDM is the most cost-effective answer to high-speed, multichannel provisioning. Of course, DWDM presents a challenge to service providers. It was primarily designed for long-haul, high-bandwidth, circuit-switched networks where bandwidth was at a premium and where the capability to conserve it or manage it cost effectively was of paramount importance. As demand for metro connectivity has grown, an interesting functional disparity between the legacy circuit-switched networks and the modern packet-based metro networks has emerged. Legacy long-haul networks largely rely on SONET or SDH for high-bandwidth transport; unfortunately, the large ADMs used in that environment do not scale well in the metro arena. Adding DWDM to a SONET/SDH ring may add bandwidth, but it also adds an inordinately high degree of complexity to a network that by all rights should be simple. Although many believe that metro networks are nothing more than longhaul networks built to a Lilliputian scale, they are not. Metro optical networks offer significant capabilities that are designed around the unique requirements of the metro environment. Without these qualities, MONs are not cost effective. These characteristics include ■
Diverse protocol support Because metro networks are close to the customer, they must be able to support a wide range of both access and
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
63
transport protocols. Equally important, they must be extremely dynamic and adaptable so that they can keep up with the often unpredictable requirements of the user community. Convergence plays an important role here; the degree to which the network can support diverse payload types from a single deployment platform is a direct measure of the degree to which the network will deliver a competitive advantage to its user community. And because MONs tend to be protocol and device independent, they support legacy installations as well as newly introduced connectivity solutions. This capability to blend the old with the new leads to significant cost reductions due to the elimination of redundant interface equipment and maintenance and provisioning organizations. It also leads to consolidated (and therefore much less complex) network management (by eliminating layers and equipment), simplified network management, and reduced collocation issues. ■
Transparency Although it sounds like a bad joke, signal transparency at the physical (optical) layer is critically important to multiservice access, metro, or long-haul networks. Because the network tends to be the least common denominator in transport, it must be able to handle a diverse range of protocol types, particularly on the access side. By extending the involvement of optical to the edge of the network, service providers can simplify their networks, reduce provisioning time, limit channel latency issues, and reduce costs because of the growing simplicity of the network. For example, expensive optical-to-electrical transceivers result in significant improvements in scalability as well as drastic reductions in cost. Because optical transport can eliminate the dependency on subrate metallic channel grooming, both cost and operational efficiencies result. It is no wonder that metro providers like Telseon and Yipes have made transparency a key differentiator in their networks. It is also interesting to note that some companies building products for the metro market have recognized the expensive protocol disparity that exists and have done something about it. Consider, for example, the low-cost media converters built by Metrobility (www.metrobility.com).
■
Mesh network support In a prior book on optical networking, I applauded the merits of companies like Astral Point (www.astralpoint.com), recently acquired by Alcatel, for their innovative bandwidth provisioning and management systems. Figure 2-2 illustrates how they work. A network manager brings up a spider drawing of the network on a management console and clicks the
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
64 Figure 2-2 Automated network provisioning. The network manager clicks an origination point (A) and then selects the circuit endpoint (Z). The circuit is instantly provisioned at the appropriate bandwidth level.
Z
A
circuit origination point (1). A pull-down menu appears from which the circuit bandwidth is selected (2). A window appears, instructing the network manager to click the circuit endpoint (3). At this point, the bandwidth is provisioned and the circuit is up and running—no waiting and no provisioning interval. Mesh networks lend themselves to this kind of model because they are designed to provide virtually limitless alternate paths between circuit endpoints. Traditional metro networks have always been based on ring architectures. Recently, however, mesh architecture have begun to appear, challenging the supremacy of rings. Rings are innovative solutions to network challenges, but they do have limitations. First, in spite of all the capabilities they bring to the network, they are not particularly flexible when it comes to physical deployment. Users are typically required to transport their traffic along the single path that the ring provides, even if that path offers a less than efficient path from the source to the destination. In many cases, this poses no problem, but for the many delay-sensitive applications that are emerging on the scene such as voice over IP (VoIP), interactive and distributive video, and others, the added delay can change the perceived QoS, especially if a ring switch has occurred that adds even more end-to-end delay. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
65
In response to this evolving perception, a new architecture has emerged on the scene. Interestingly enough, it is not a new model, but rather one that has been around for a long time. Mesh architectures are suddenly enjoying great attention as the next generation of networking to inherit the crown from the pure ring. This model, shown in Figure 2-3, offers the multiple route capabilities of a dedicated network span alongside the survivable nature of a ring. As the figure shows, the bulk of the network is a collection of point-to-point facilities that provide the shortest distance transport between any two end points. However, the mesh can easily be seen to comprise a collection of interconnected rings, and the large number of alternate routes means that survivability is assured alongside guarantees of least-hop routing. In the real world, fiber has now been deployed so extensively and universally that the ability to build mesh networks is no longer a problem. The real issue with SONET and SDH as they evolve to accommodate the needs of the so-called next-generation network is that both must be modified to transport the variety of data types that have emerged as viable revenue components in the emerging metro optical network. SONET and SDH were designed to address the relatively predictable 64 Kbps transport needs of voice networks that dominated the attention of service providers in the pre-Internet world. However, with the arrival of the World Wide Web in the 1990s, transported traffic became a mix of predictable voice and unpredictable, chaotic, latency-friendly packet data. As a result, SONET and SDH
Figure 2-3 A mesh-ring hybrid network. This architecture offers the resiliency of a ring with the flexibility of a mesh.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
66
were no longer as capable as they once were for meeting the demands of all service types, particularly given the interest in predictable QoS as the principal differentiator among access and transport providers. Such qualities as security, latency, granular bandwidth provisioning, dynamic time-of-day provisioning, multiple levels of service protection, and a host of others have garnered the attention of service providers in general, particularly as they have begun to managerially segment their networks into local, metro, regional, and long-haul quadrants. It is this differentiable QoS capability that not only provides differentiation among the players in a commodity market, but it also offers new opportunities for revenue generation. Because of the original services that they were designed to transport, SONET and SDH comprise large, multinode rings that interconnect to other rings as well as to point-to-point transport facilities. These architectures are well understood, fully functional, and widely deployed; thus, the cost of maintaining them on an ongoing basis is comparatively low. They provide ideal carriage for the limited requirements of circuit-switched voice, offering not only low-latency transport but survivability as well. If a failure occurs due to a fiber disruption, service can usually be restored in less than 50 milliseconds, which means that voice traffic is not affected. As the traffic mix has evolved, however, the limitations of SONET and SDH have become more obvious. Each ring in a SONET or SDH network is limited to a certain number of nodes, and each ring cannot exceed a certain maximum circumference if transport QoS is to be assured. Thus, if added capacity in the network is needed, the solution is to add rings, clearly an expensive and time-consuming process. This stacked ring model also has the disadvantage of being disparately managed, meaning that each ring must be provisioned and managed on an individual basis, making the job of the network manager more difficult. Furthermore, SONET and SDH do not offer particularly flexible bandwidth allocation capabilities. Originally created to transport 64 Kbps voice, neither of the two adapts well to the transport of data traffic that has wildly variable bandwidth requirements, in terms of both bandwidth assignment and predictability. Think about it: In a SONET network, bandwidth jumps from 51.84 Mbps (OC-1) directly to 155.52 Mbps (OC-3) with no intermediate level. Customers wanting to make a minor upgrade must increase their purchased bandwidth threefold, much of which they will probably not use. Because SONET and SDH rings typically reserve as much as half of their total available bandwidth for redundancy purposes, they are terribly inefficient. The mesh model discussed earlier represents the solution to this set of problems. In the last three years, optical networking has evolved in three Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
67
significant areas: the development of true all-optical switching and intelligent routing, the extensive proliferation of fiber throughout most carriers’ operating areas, and the return of the mesh network. In a ring network, nodes are connected to one another in such a way that they do not have a direct interconnection to one another; all node-to-node traffic (other than between adjacent nodes) must flow along a rigidly deterministic path from a source node to a destination. In a mesh network, every node in the network is connected to every other node in the network, thus allowing shortest hop routing throughout the network between any two end points. The advantages of this design are rather strong. First of all, distance limitations in mesh networks are largely eliminated because paths are created on a shortest-path basis between nodes rather than all the way around a ring. As a result, nodes represent the bottleneck in mesh networks rather than the fiber spans themselves, which means that network operators can increase capacity simply by adding nodes on a demand basis and increasing transported bandwidth across the installed fiber infrastructure. This eliminates the stacked ring problem and dramatically improves upgrade intervals, an area of some concern for most service providers. Perhaps the greatest advantage of mesh networks is management. Unlike SONET and SDH where rings must be managed on a ring-by-ring basis, mesh networks are designed to accommodate point-and-click provisioning, described earlier, which shortens installation intervals from months in many cases to hours. The service focus for these topologies is primarily on the metropolitan marketplace. The mesh network also enables carriers to design “distributed protection” schemes, which in turn enable them to use their available bandwidth much more efficiently. SONET and SDH rely on redundant rings to provide 100 percent survivability, which on the one hand is great because it provides 100 percent redundancy, but on the other hand wastes 50 percent of the available bandwidth because of the reservation of an entire ring for the eventuality of a rogue backhoe driver with a map of network routes in his back pocket. Because of the tremendous flexibility of mesh topology, entire routes do not need to be reserved. Instead, network designers can allocate backup capacity across a collection of routes, thus preserving the integrity of the network while at the same time using the available bandwidth far more efficiently than a ring. Furthermore, most carriers have plans to offer a variety of protection levels to their customers as one of many differentiable services. SONET and SDH, with their 100 percent, always-on protection schemes, do not lend themselves to this capability as a mesh architecture, whereas a mesh can Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
68
be provisioned in any of a variety of ways. These include 0⫻1 protection (no protection at all), 1:N protection (one protect path that handles the potential failures of multiple paths), and 1:1 protection (dedicated protection à la SONET and SDH rings). 0⫻1 protection is obviously the most economical, while 1:1 protection is the most costly since it offers 100 percent protection against network failures. Obviously, mesh networks are far more complex than their ring counterparts and are therefore significantly more difficult to manage. They require a level of network management intelligence that is quite a bit more capable than that provided by the SONET and SDH overhead bytes. Both ring and mesh networks have their advantages and disadvantages, as we have just discussed. Furthermore, SONET and SDH enjoy an enormous embedded base of installed networks and service providers that have made large capital investments to build them and are loathe to discard those investments easily. Not only must hardware be modified, but the evolution from ring to mesh involves modifications to provisioning systems, billing systems, operations support, provisioning, and personnel training as well. The result of this is that most industry analysts believe that the end result is the evolution of hybrid networks that sport the best of both ring and mesh architectures. Because of the increasingly bursty (and therefore unpredictable) nature of metro area traffic, the ability of network designers and traffic engineers to optimize the network for the loads is proving to be an interesting and often vexing problem. Even though metro networks tend to be relatively small geographically, the amount of traffic generated within them is growing at a rapid clip, and the boundaries of the typical metro network are expanding apace. As a result, service providers are seeking solutions that will augment their existing services and that will extend the service area of legacy infrastructures by taking into account such variables as customer service demographics, variable traffic demands, and time-of-day variations in load. Unfortunately, this type of real-time adaptation of the network requires flexible protocols that can accommodate the requirements of such a technologically chaotic environment. In most metro networks today, the predominant topology is ring-based and usually depends on SONET/SDH physical layer protocols to frame the transported payload. To add rudimentary flexibility in response to evolving service demands, network designers have in some cases augmented existing ring topologies with DWDM as a bandwidth mediation mechanism. In some network designs, optical ADMs have the capability to selectively “route” individual wavelengths (lambdas) from the source port to the destination port, thus adding yet another layer of flexibility. The problem with Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
69
these innovations is that they still depend on legacy ring architectures and are therefore an intermediate stage between legacy installations and future network architectures. Generally speaking, Optical Add-Drop Multiplexer (OADM)-based network designs require significant, complex network preplanning and are not particularly flexible. Instead, they offer massive amounts of bandwidth, which to a certain extent can substitute for flexibility. Although these hybrid arrangements have become somewhat popular as a transition technology, in reality they are not particularly scalable. SONET/SDH rings are rather rigid in terms of the way in which they manage on-ring bandwidth and therefore do not scale well when placed into service with other rings. One response to this collection of challenges is DWDM-enhanced mesh networks. Both carriers and hardware providers have developed interest in this combination because it takes best advantage of a network model that is effectively a wavelength-switching design, enhanced by the flexibility of mesh connectivity. This leads to the next generation of network device intelligence in the form of the optical cross-connect (OXC). In OXC installations, network paths can be established rapidly and are both protocol and bandwidth independent. Furthermore, they can be used in both point-to-point configurations and in ring-based ADMs. Because the dominant protocols that will ride over these optical connections are (and will continue to be) ATM and IP, both of which rely on mesh networks to achieve their significant advantages, mesh networks represent a more sensible approach to interface with these protocols at layers two and three. Mesh networks are more significantly more bandwidth efficient than ring-based architectures. To service providers, they represent a topology that they are quite familiar with and that requires little in the way of upfront provisioning, since all “routes” are preestablished by the very nature of the physical network. Furthermore, they scale well, giving the network provider some semblance of control over their incremental costs. In short, mesh networks offer quite a few advantages, most of them related to their capability to create a smooth transition from legacy infrastructures toward a future network design. As an example, legacy rings equipped with traditional OXCs can be used to offer standard SONET/SDH add-drop functions, but they can also be reconfigured when appropriate to create a “mesh of rings” during the migration stage. Mesh networks provide the following advantages: ■
Rapid provisioning In legacy SONET/SDH networks, provisioning is a complex, multistage process that commonly takes weeks and is often fraught with errors. Furthermore, the less flexible nature of
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
70
SONET/SDH does not allow for “quick and easy” provisioning activities. Because the metro environment has become so competitive, tools have been developed that are software-based and that facilitate rapid, automated provisioning. In mesh networks that are enhanced with DWDM, the individual wavelengths and the connection points (switching, add-drop, wavelength management) are the resources that must be managed. To ensure that the network is as efficient as possible and to protect (and hopefully augment) service provider revenues, intelligent management processes for wavelength provisioning are often deployed. These capabilities result in very fast connection intervals and manage such functions as end-point identification, route computation, and accurate, low-latency route setup. They also manage such parameters as delay, traffic priority, link protection, and channel quality as a way to deliver QoS. As IP traffic continues to expand in volume relative to circuit-switched traffic, the cross-sectional profile of network resource utilization will change, and will become significantly more unpredictable and bursty than that of its predecessor. As a result, it makes sense to use existing IP-based route control protocols within these optical networks. Multiprotocol Label Switching (MPLS) is the first of these to be used as a “shim” protocol between IP and ATM in the protocol stack, with the intent to eventually displace ATM where feasible; in the optical environment, multiprotocol lambda switching (MPlS) has been designed to accommodate the unique requirements seen in the MON environment. A network that is “data-aware” (to use a common expression) must use IP traffic-engineering to manage such disparate tasks as routing and protection. It must also provide manageable integration of IP with the DWDM sublayer for effective bandwidth utilization. One key advantage is that the so-called short-reach optics deployed on modern high-speed routers can be connected directly to DWDM cross-connect devices such as the Lucent LambdaRouter, allowing more effective automated traffic engineering. These user-tonetwork interfaces (UNI) enable metro providers to design highly responsive IP networks, including the one performance indicator that is most visible to the customer, provisioning intervals. They translate into greater market share, increased revenue, improved customer satisfaction, and lower overall costs. ■
Network survivability Because of the broad, diverse range of protocols, applications, and network-based services used by the various
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
71
communities of users within the metro space, and because of the granular (and varied) demand for differing levels of service quality among various customer groups, service providers must craft different QoS and network performance criteria for those different customers. Service level agreements (SLAs), particularly for voice and video services, have once again become a major area for discussion. Even though the bulk of all packets transported across the Internet consists of short, Transmission Control Protocol (TCP) acknowledgement (ACK) and nonacknowledgement (NAK) packets, a variety of delay-insensitive customer traffic components still make up a reasonable percentage of the overall traffic model, including IP, fax, e-mail, web pages, and so on. As a result, some customers will be perfectly happy to put up with slightly lower quality service in exchange for a smaller invoice at the end of the billing cycle. As we observed earlier, both ring and mesh topologies will continue to coexist in the metro, although mesh networks will dominate over time. Topologically, mesh networks are really nothing more than a collection of nested rings (see Figure 2-3). As with ring networks, survivability comes in two forms: restoration and protection. Survivability functions are classified into the same two forms as well. Restoration refers to real-time, dynamic functions that take place after a network fault and that serve to recover from the fault. They tend to be reactive mechanisms. Protection, on the other hand, refers to those proactive measures taken to prevent failures from mesh networks that can match SONET/SDH 50-millisecond recovery intervals and have the capability to recover from multiple fiber cuts or node faults. Because of the varying demands from customers for bandwidth and QoS, mesh topologies are ideally positioned. They can provide dedicated paths for delay-sensitive traffic or shared resources for those traffic components that are less sensitive to delay. ■
Network management and OSS Operations Support Systems (OSSs) provide three key areas of functionality: billing and customer care, assurance, and fulfillment. Billing and customer care include such factors as fraud prediction and management, billing mediation, bill rating, tariff management, and interactive customer care. Assurance handles security, trouble tracking and management, performance tracking, service management, and fault identification, tracking, and management. Finally, fulfillment manages flow-through provisioning, inventory, service activation, access and transport engineering, OSS interoperability, network policy management, and voice provisioning.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
72
Most service providers today have historically focused their efforts on increasing the capacity of their networks rather than on improving operational efficiencies and tend to view network management and OSS functions as a necessary evil expense that is one of the most onerous costs of doing business. What the service providers don’t realize is that well over half of their total cost of doing business can be positively affected through reasonable and a well-thought-out investment in network management tools and OSSs. This is as true in the evolving metro world as it is in voice and legacy data. Today, a variety of functional areas are poised to grow in the OSS domain. These include customer self-management, network resource management, converged service billing, and on-demand services and provisioning. In 2001, service providers spent $9 billion on OSS services and software, and the numbers are expected to grow. These systems offer a number of distinct advantages to the service provider. More than anything else, they enable the service provider to operate much more efficiently, which in turn translates into reduced costs and higher revenues; these translate into improved profits. In spite of the new protocols and services that the market is demanding, service providers require the same capabilities that they always have: standards-based management systems, bit-rate and protocol-independent management systems, support for integrated technology solutions, and the capability to monitor performance, fault isolation, and accounting activities, all of which fall under the broad umbrella of Operations, Administration, Maintenance, and Provisioning (OAM&P). ■
Subrate (shared lambda) provisioning Although the demand for high-speed optical transport continues to grow, metro network service providers must also provision lower-bandwidth solutions for those customers that do not require high-bandwidth solutions. These include such services as DS-3, OC-3, OC-12, 200 Mbps ESCON, and a variety of others. This creates a challenge for the provider because although optical transport technologies offer a high degree of bandwidth granularity, legacy technologies such as SONET and SDH really do not. If an entire wavelength must be assigned to a customer to satisfy lowbandwidth demands, the approach is clearly wasteful. It is significantly more efficient to provision fractional wavelengths and to aggregate them as required into a single channel. Both data traffic and legacy circuit traffic can be transported in the same lambda at the ingress side, thus dramatically improving the efficiency of the overall system.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
73
This also has another positive impact on the service provider; it enables them to “pay as you grow” so that they can intelligently augment the network as it makes financial sense, rather than doing an entire buildout from day one. ■
Reliability Service interruptions in MONs can cause serious service disruptions because of the numbers of users that exist on the networks. The high concentration of disparate customers found in MTUs can result in widespread damage if a network fails in the metro environment. As a result, MONs must provide high reliability if they are to be taken seriously.
■
Cost DWDM technology becomes important in the metro space because it has the capability to consolidate traffic—and therefore cost— onto a single shared facility that offers appropriate service granularity to the customer as required. Cost can rapidly become a major issue, because for the most part these companies already have a significant investment in SONET/SDH infrastructure, which has already proven itself with tremendous economies of scale. The real benefit in the metro arena comes when service providers, in concert with hardware vendors, offer end-to-end solutions.
Metro Demographics For a very long time, the metro geography was dominated by large corporations that occupied single-tenant buildings. Today that model has changed drastically. Most corporations in major metro areas now occupy a large number of smaller buildings that are located at the periphery of the metro area (where the customers are) instead of a single monolithic facility. Of course, the employees in those far-flung facilities require that their connectivity solution be functionally seamless, such that there is no service difference between the network they had when they were all in the same building and the network they now have while scattered across the landscape. This means that metro technologies must be up to the task of delivering this degree of “seamlessness.” Although numerous legacy technologies can offer the level of connectivity required, they tend to be expensive because they are designed for large installations across which the cost of deployment can be amortized. As a result, they do not always scale well economically when deployed in metro
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
74
networks. Other solutions, discussed in Part 3, provide a better answer to metro connectivity.
Regulatory Impacts The “reworking” of the telecommunications industry that began with the divestiture of AT&T in 1984 reaches far beyond the borders of the United States. It has become a global phenomenon as companies move to compete in what has become an enormously lucrative business. Customers, however, have been quick to point out that technology is a wonderful thing, but unless the provider positions it in a way that makes it useful to the wouldbe customer, it has very little value. Customers expect service provider representatives to have relevant technical knowledge as well as knowledge about them as customers: business issues, competition, major segment concerns, and so on. Furthermore, the level of customer satisfaction or dissatisfaction varies from industry segment to industry segment. Incumbent Local Exchange Carriers (ILECs) are too rigid and expensive. Competitive Local Exchange Carriers (CLECs) must compete on price, but they must also show a demonstrated ability to respond quickly and offer OSS/Network Management (NM) capabilities as well as, show staying power. Ninety-two percent of all business customers want to work with an account team when purchasing services, yet account teams are not creating long-lasting relationships or loyalty in their day-to-day dealings with customers. Eighty-eight percent of those customers buy their services from the local provider, but only 53 percent say that they would continue to use them if given the choice. According to numerous studies, the single most important factor that customers take into consideration when selecting a service provider is cost. Yet the most important factor identified for improvement is customer service. The most daunting challenge that has historically faced service providers is the requirement to provide true universal service, both in rural areas as well as in metropolitan and suburban areas. The American Communications Act of 1934, signed into law by President Roosevelt, mandated that telephony service would be universal and affordable. To make this happen, AT&T agreed in the 1940s to offer low-cost service with the tacit approval of the Justice Department to charge a slightly higher price for long distance, some business-line services, and value-added services as a way to offset the cost of deploying high-cost rural service and to support lowDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
75
income families. These subsidies made it possible to offer true universal, low-cost service. Today, 60 to 70 percent of the local loops in the United States are still subsidized to the tune of anywhere from $3 to $15 per month. As a result, the incumbent service providers often charge significantly less for the service they sell than it actually costs them to provide it. The problem with this model is that only the ILECs have the right to enjoy these subsidies, which means that CLECs are heavily penalized right out of the starting gate. Couple that with the fact that 40 percent of all CLEC revenues go to the ILECs for access charges. As a result of these and other factors, CLECs typically ignore the residence market in favor of the far more lucrative business markets. Business markets are significantly easier and less costly to provision than residence installations because of the dominance of multitenant buildings (MTUs). Clearly, the metro market is a desirable place to be. Of course, there is an added issue: ILECs control more than 60 percent of all metro spending. The regulatory environment in many countries fails to address the disparity that exists between incumbent providers and would-be competitors. Recent decisions, such as the United States’ Communications Act of 1996, consisted of a series of decisions designed to foster competition at the local loop level. Unfortunately, by most players’ estimations, it has had the opposite effect. New technologies always convey a temporary advantage to the first mover. Innovation involves significant risk; the temporary first mover advantage allows them to extract profits as a reward for taking the initial risk, thus allowing innovators to recover the cost of innovation. As technology advances, the first mover position often goes away, so the advantage is fleeting. The relationship, however, fosters a zeal for ongoing entrepreneurial development. Under the regulatory rule set that exists in many countries today, incumbent providers are required to open their networks through element unbundling and to sell their resources—including new technologies—at a wholesale price to their competitors. In the minds of regulators, this creates a competitive marketplace, but it is artificial. In fact, the opposite happens; the incumbents lose their incentive to invest in new technology, and innovation progresses at “telco time.” Under the wholesale unbundling requirements, the rewards for innovative behavior are socialized, while the risks undertaken by the incumbents are privatized. Why should they invest and take a substantial economic risk when they are required by law to immediately share the rewards with their competitors?
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
76
Ultimately, the truth comes down to this: Success in the access marketplace, translated as sustainable profits, relies on network ownership— period. Many would-be competitors such as E.spire and ICG bought switches and other network infrastructure components, built partial networks, and created business plans that consciously relied on the ILECs for the remainder of their network infrastructure. Because of the aforementioned subsidies, they quickly learned that this model could not succeed, and many of them have disappeared. Consider that when WorldCom bought Metropolitan Fiber Systems (MFS), they weren’t after the business; they were after the in-place local network that MFS had built, which would enable WorldCom to satisfy customer demands for end-to-end service without going through the cost of a network build-out. They paid more than six times the value of MFS’ inplace assets for the company. The message? Network ownership is key. Two major bills currently before the U.S. Congress (Tauzin-Dingell, HR 1542, and Cannon-Conyers, HR 1697) aim to reposition the players. 1542 makes it easier for ILECs to enter the long-distance, Internet, and data businesses. 1697 tightens controls over their entry and applies significant fines for failure to open incumbent networks to competitors. 1542 has already passed the Senate, but a major battle is expected in the House of Representatives. Most pundits believe that the industry needs less government controls and more competition; the FCC appears to agree. Many believe that high-speed data and Internet access should have been exempted from the Communications Act of 1996’s mandates and that it should have only targeted traditional voice services where the ILECs have clear monopoly positions. They contend that unbundling and wholesale requirements should not be required for nonvoice services. Recent decisions on the part of the FCC aim to bring about the changes that are needed. Both cable data and DSL are on their way from being classified as telecom services to being reclassified as information services by the agency, a move that would exempt them from 271 unbundling requirements.
Likely Regulatory Solutions So what are the possible solutions? One is to eliminate the local service subsidies and enable the ILECs to raise rates so that they are slightly above the actual cost of provisioning service. Subsidies could continue for highcost rural areas and low-income families (roughly 18 percent of the total) Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
The Metro Network
77
but would be eliminated elsewhere. New entrants would then have a greater chance of playing successfully in the local access business. The subsidy dollars, estimated to be in the neighborhood of $15 billion, could then be redeployed to finance universal broadband access deployment. The monies could be distributed among ILECs, CLECs, cable companies, Internet service providers (ISPs), wireless companies, and DSL providers to facilitate broadband. A second solution is to call for the structural separation of the ILECs, which would result in the establishment of retail and wholesale arms. The retail arm would continue to sell to traditional customers, while the wholesale arm would sell unbundled network resources to “all comers.” The result would be enhanced innovation; the downside would undoubtedly be strong resistance from the ILECs. The new regime at the FCC, led by Michael Powell, has indicated that it wants less government intervention in the telecommunications marketplace rather than more, a good thing in light of the current industry. One could argue that well-intended regulatory strictures have in fact done damage. Consider the case of WorldCom. The company’s original plan in the late 1990s was to challenge local service providers all over the world by creating a broadband voice and data IP network through acquisitions and mergers. The regulators, concerned by WorldCom’s aggressive plans, felt that the intended company looked too much like a monopoly. They forced the divestiture of MCI’s Internet company to Cable & Wireless and rejected the proposed merger with Sprint because of fears that they would control 80 percent of the long-distance market. This decision was made while longdistance revenues were plummeting due to the influence of such disruptive technologies as multichannel optical transport and IP. The result is two badly weakened companies that have not yet recovered—and may not. In fact, they could be prime acquisition targets by the ILECs. Another example is AT&T itself. AT&T was expected to be a big winner in the local broadband access game following its acquisitions of cable properties for its plans to deliver high-speed Internet and interactive services. Many analysts expected a market cross-invasion between the ILECs and cable providers, but it never happened. Cable providers concentrated on adding Internet service and additional channels; telephone companies concentrated on penetrating the long-distance market. Furthermore, when talk of open access and loop unbundling began to be targeted at the cable industry in 2000, AT&T’s hopes of a competitive advantage through cable ownership were dashed. ILECs were also expected to work hard to penetrate each other’s markets, but this never happened either. Who better than the ILECs knows Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
The Metro Network
Part 2
78
that network ownership is the most critical factor for success in the local access game? If you control the network, you control the customers. More importantly, if you don’t have that control, don’t get into the game. In the metro market, which is highly dependent on high-speed access technologies such as DSL (and to a lesser degree, cable and wireless), these regulatory decisions represent pivotal points in the evolution of the metro domain. If the FCC chooses to reduce the regulatory pressure on the incumbents, customers will invest in bandwidth at the edge, driving traffic into the metro, which will in turn drive traffic into the network core.
Summary Metro networks have evolved over a relatively short period of time in response to changing corporate topologies and demographics, different customer requirements, shifts in network economics, and modifications of regulatory policy. Companies have recognized that the closer they are to their customers, the more effectively they can deliver service to those customers. As a result, specialized metro networks have evolved that satisfy the unique demands in this odd region that lies between the access networks and the network core. In Part 3, we continue our discussion of metro, this time with a focus on the five technology components that make up the metro arena: customer premises, access, transport, switching, and interfaces.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Source: Metro Area Networking
PART
3 Enabling Technologies
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
80
In this part, we examine the technologies that enable the metro networking environment. We divide these into five categories and will examine each in turn: premises, access, transport, switching, and interfaces. Premises technologies are those used by the customer for intracorporate communications such as local area networks (LANs, most notably Ethernet). In the metro networking arena, premises technologies play an important role because they generate and terminate the content that ultimately drives the demand for bandwidth at the edge of the network. Today the single biggest driver at the premises level is Ethernet. Described briefly in an earlier part of the book, Ethernet has cast off its LAN limitations and is now running freely about the network, performing all sorts of tasks for which it was never intended—yet doing them exceptionally well. It has been so successful as a point-to-point transport scheme that a new type of carrier has emerged, offering carrier-class Ethernet for long-haul and metro applications. We begin our discussion, then, with Ethernet.
Introduction Ethernet is the world’s most widely deployed LAN technology. Originally, the commercial version of Ethernet was designed to support 10 Mbps transport within a LAN. In the last few years, however, 10 Mbps has been supplemented with both 100 Mbps (Fast Ethernet) and Gigabit Ethernet versions, and in recent months a 10 Gbps version has been introduced. Legacy Ethernet was designed to operate over various forms of twisted pair, coaxial cable, and fiber. Furthermore, both bus and star topologies were supported, a characteristic that continues today. As we mentioned earlier, Ethernet often uses a Medium Access Control (MAC) protocol called Carrier Sense Multiple Access with Collision Detection (CSMA/CD).
Overview and Terminology In the 20 years since Ethernet first arrived on the scene as a low-cost, highbandwidth 10 Mbps LAN service for office automation applications, it has carved a niche for itself that transcends its original purpose. Today it is used in LANs, metropolitan area networks (MANs), and wide area networks (WANs) as both an access and transport technology. Its bandwidth capabilDownloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
81
ities have evolved to the point that the original 10 Mbps version seems almost embarrassing; a 10 Gbps version of the technology now exists. Today’s Ethernet product is based on the Institute of Electrical and Electronics Engineers (IEEE) 802.3 standard and its many variants, which specify the CSMA/CD access scheme (explained in a moment) and a handful of other details. It is perhaps important to note that Ethernet is a product name, originally invented and named by 3Com founder Bob Metcalfe. CSMA/CD is the more correct name for the technology that underlies Ethernet’s functionality and the 802.3 standard. The term Ethernet, however, has become the de facto name for the technology. Ethernet evolved in stages, all based upon the original IEEE 802.3 standard, which passed through various evolutionary phases of capability including 10 (Ethernet), 100 (Fast Ethernet), 1000 (Gigabit Ethernet), and 10,000 Mbps (10 Gbps Ethernet) versions. All are still in use, which allows for the design and implementation of tiered corporate Ethernet networks. A corporation, for example, could build a gigabit backbone, connected to Fast Ethernet access links, and connected in turn to 10 Mbps switches and hubs that communicate with desktop devices at the same speed. In its original form, Ethernet supported point-to-point connectivity as far as 0.062 miles over unshielded twisted pair (UTP), up to 1.2 miles over multimode fiber, and up to 3.1 miles over single-mode fiber (SMF) at a range of speeds. However, when the metro market began to emerge as a “newly discovered network region,” it began to be seen as an alternative transport scheme for both inter- and intrametro network architectures. Today, 10 Mbps is inadequate for many enterprise applications, so the new versions of Ethernet mentioned earlier have evolved and become standardized.
How Ethernet Works Ethernet is called a contention-based LAN. In contention-based LANs, devices attached to the network vie for access using the technological equivalent of gladiatorial combat. If a station on the LAN wants to transmit, it does so, knowing that the transmitted signal could collide with the signal generated by another station that transmitted at the same time, because even though the transmissions are occurring on a LAN, some delay still takes place between the time that both stations transmit and the time they both realize that someone else has transmitted. This collision results in the destruction of both transmitted messages. If a collision occurs, both stations stop transmitting, wait a random amount of time, and try again. This technique is called truncated binary exponential backoff and will be explained later. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
82
Ultimately, each station will get a turn to transmit, although how long they have to wait is based on how busy the LAN is. Contention-based systems are characterized by unbounded delay, because no upward limit exists on how long a station may wait to use the shared medium. As the LAN gets busier and traffic volume increases, the number of stations vying for access to the shared medium, which only enables a single station at a time to use it, also goes up, which results in more collisions. Collisions result in wasted bandwidth so LANs do everything they can to avoid them. The protocol employed in traditional Ethernet is CSMA/CD. In CSMA/CD, a station observes the following guidelines when attempting to transmit. Remember the old western movies when the tracker would lie down and put his ear against the railroad tracks to determine whether a train is coming? Well, CSMA/CD is a variation on that theme. First, it listens to the shared medium to determine whether it is in use. If the LAN is available (not in use), the station begins to transmit but continues to listen while it is transmitting, knowing that another station could transmit simultaneously. If a collision is detected, both stations back off and try again. To avoid a repeat collision, each station waits a random period of time before attempting a retransmission.
LAN Switching To reduce contention in CSMA/CD LANs, LAN switching was developed, a topology in which each station is individually connected to a high-speed switch, often with Asynchronous Transfer Mode (ATM) on the backplane. The LAN switch implements full-duplex transmission at each port, reduces throughput delay, and offers per-port rate adjustment. The first 10 Mbps Ethernet LAN switches emerged in 1993 followed closely by Fast Ethernet (100 Mbps) versions in 1995 and Gigabit Ethernet (1,000 Mbps) switches in 1997. Today they are considered the standard for LAN architectures, and because they use star wiring topologies, they provide high levels of management and security to network administrators.
Ethernet Services Ethernet has been around for a long time and is understood, easy to use, and trusted. It is a low-cost solution that offers scalability, rapid and easy provisioning, granular bandwidth management, and simplified network Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
83
management due to its single protocol nature. As its popularity has increased and it has edged into the WAN environment, it now supports such applications as large-scale backup, streaming media server access, Web hosting, application service provider (ASP) connectivity, storage area networks (SANs), video, and disaster recovery. Another important service is the virtual LAN (VLAN). Often characterized as a virtual private network (VPN) made up of a securely interconnected collection of LANs, a number of vendors now offer VLANs as a service, including Lantern Communications, which claims to be able to support thousands of VLANs on a single metro ring. Similarly, transparent LAN (TLAN) services have gained the attention of the industry; they enable multiple metro LANs to be interconnected in a point-to-point fashion. Many vendors are now talking about Ethernet private lines (EPLs), an emerging replacement for legacy dedicated private lines. Implemented over Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH), the service combines SONET/SDH’s reliability, security, and wide presence with Ethernet’s rapid, flexible provisioning capability. One company that sees the value in this combination is Appian Communications, already building Systems Network Architecture (SNA), video, SAN, and Voice over IP (VoIP) application support across its network architectures. Of course, Ethernet presents some disadvantages. These include the potential for packet loss and the resultant inferior quality of service (QoS). However, two new standards have emerged that will go a long way towards eliminating this problem. The IEEE 802.17 Resilient Packet Ring (RPR) standard, discussed later in this book, is designed to give SONET/SDH-like protection and reliability to Ethernet, using a data link layer protocol that is ideal for packet services across not only LANs, but MANs and WANs as well. Primarily targeted at voice, video, and IP traffic, it will restore a breached ring within 50 milliseconds. The IEEE began the 802.17 RPR standards project in December 2000 with the intention of creating a new MAC layer. Fiber rings are widely used in both MANs and WANs; these topologies, unfortunately, are dependent on protocols that are not scalable for the demands of packet-switched networks such as IP. The 802.17 RPR working group promotes RPR as a technology for device connectivity. Issues currently being addressed are bandwidth allocation and throughput, deployment speed, and equipment and operational costs. The second standard, ITU X.86, maps Ethernet (Open Systems Interconnection [OSI] layer two) frames into SONET/SDH physical layer (OSI layer one) frames for high-speed transmission across the broad base of legacy networks. Both standards are due to be ratified in late 2002 or early 2003. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
84
Ethernet: A Brief History Ethernet was first developed in the early 1970s by Bob Metcalfe and David Boggs at the Xerox Palo Alto Research Center (Xerox PARC). Originally designed as an interconnection technology for the PARC’s many disparate minicomputers and high-speed printers, the original version operated at a whopping 2.9 Mbps. Interestingly, this line speed was chosen because it was a multiple of the clock speed of the original Alto computer. Created by Xerox Corporation in 1972 as a personal computer targeted at research, Alto’s name came from the Xerox Palo Alto Research Center, where it was originally created. The Alto was the result of developmental work performed by Ed McCreight, Chuck Thacker, Butler Lampson, Bob Sproull, and Dave Boggs, engineers and computer scientists attempting to create a computer small enough to fit in an office but powerful enough to support a multifunctional operating system and powerful graphics display. In 1978, Xerox donated 50 Alto computers to Stanford, MIT, and Carnegie Mellon Universities. These machines were quickly adopted by campus user communities and became the benchmark for the creation of other personal computers. The Alto comprised a beautiful (for the time) graphics display, a keyboard, a mouse that controlled the graphics, and a cabinet that contained the central processing unit (CPU) and hard drive. At $32,000, the thing was a steal. The concept of employing a visual interface (what you see is what you get [WYSIWYG]) began in the mid-70s at Xerox PARC, where a graphical interface for the Xerox Star system was introduced in early 1981. The Star was not a commercially successful product, but its creation led to the development of the Apple Lisa in 1983 and the Macintosh in 1984. In July 1976, Metcalfe and Boggs published “Ethernet: Distributed Packet Switching for Local Computer Networks” in Communications of the Association for Computing Machinery. A patent followed with the mouthful of a name, “Multipoint Data Communications System with Collision Detection,” issued to Xerox in December 1977.
Phase Two: Xerox and DEC In 1979, DEC, Intel, and Xerox Corporations standardized on an Ethernet version that any company could use anywhere in the world. In September 1980, they released Version 1.0 of the DIX standard, so named because of Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
85
the initials of the three founding companies. It defined the so-called thick Ethernet or Thicknet version of Ethernet (10Base5), which offered a 10 Mbps CSMA/CD protocol. It was called Thicknet because it relied on relatively thick coaxial cable for interconnections among the various devices on the shared network. The first DIX-based controller boards became available in 1982, and the second (and last) version of DIX was released in late 1982. In 1983, the IEEE released the first Ethernet standard. Created by the organization’s 802.31 Committee, IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications was basically a reworking of the original DIX standard with changes made in a number of areas, most notably to the frame format. However, because of the plethora of legacy equipment based on the original DIX specification, 802.3 permitted the two standards to interoperate across the same Ethernet LAN. The ongoing development and tightening of the standard continued over the next few years. In 1985, IEEE released 802.3a, which defined thin Ethernet, sometimes called cheapernet (officially 10Base2). It relied on a thinner, less expensive coaxial cable for the shared medium that made installation significantly less complex. Although both media offered satisfactory network performance, they relied on a bus topology that made change management problematic. Two additional standards appeared in 1987. 802.3d specified and defined what came to be known as the Fiber Optic Interrepeater Link (FOIRL), a distance extension technique that relied on two fiber optic cables to extend the operational distance between repeaters in an Ethernet network to 1,000 meters. IEEE 802.3e defined a 1 Mbps transmission standard over twisted pair, and although the medium was innovative, it never caught on. 1990 proved to be a banner year for Ethernet’s evolution. The introduction of 802.3i 10BaseT standard by the IEEE made it possible to transmit Ethernet traffic at 10 Mbps over Category 3 UTP cable. This represented a major advance for the protocol because of UTP usage in office buildings. The result was an upswing in the demand for 10BaseT. With the expanded use of Ethernet came changes in the wiring schemes over which it was deployed. Soon, network designers were deploying Ethernet using a star wiring scheme (see Figure 3-1) instead of the more common bus architecture, which was significantly more difficult to manage, install, and troubleshoot.
1
A bit of history: The IEEE 802 committee is so named because it was founded in February 1980.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
86 Figure 3-1 A star-wired LAN. Each station is individually connected to the LAN switch (top) so that contention is eliminated, resulting in a far more efficient network.
In 1993, the IEEE released 802.3j (10BaseF), a technological leap for Ethernet that extended the transmission distance significantly by stipulating the use of a pair of optical fibers instead of copper facilities. With this technique, transmission distances could be extended to 2,000 meters, a distance that dramatically expanded Ethernet’s utility in office parks and in multitenant units (MTUs). 802.3j represented an augmentation and update of FOIRL, mentioned earlier.
The Arrival of Fast Ethernet In 1995, the IEEE announced the 100 Mbps 802.3u 100BaseT standard. Commonly known as Fast Ethernet, the standard actually comprises three disparate substandards, which in turn support three different transport media. These include 100BaseTX, which operates over two pairs of CAT 5 twisted pair; 100BaseT4, which operates over four pairs of CAT 3 twisted pair; and 100BaseFX, which operates over a pair of multimode optical Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
87
fibers. It was deemed necessary to offer a version for each of these media types because of the evolving customer environment; more on this will be covered later.
Two-Way Ethernet “Due to popular demand” as they say, the IEEE announced 802.3x in 1997, which provided a standard that governed full-duplex Ethernet. By allowing stations on an Ethernet LAN to simultaneously transmit and receive data, the need for a medium contention mechanism such as CSMA/CD was eliminated, allowing two stations to transmit simultaneously over a shared point-to-point facility. The standard was written to accommodate all versions of Ethernet, including Fast Ethernet. The IEEE also released the 802.3y 100BaseT2 standard in 1997, which provided a mechanism for transmitting at 100 Mbps over two pairs of CAT 3 balanced wire.
The Arrival of Gigabit Ethernet In 1998, Gigabit Ethernet arrived on the commercial scene. Like Fast Ethernet, the 802.3z 1000BaseX standard supported three different transmission mechanisms with three substandards: 1000BaseSX relied on an 850 nm laser over multimode fiber, 1000BaseLX used a 1300 nm laser over both single and multimode fiber, and 1000BaseCX was designed for operation over short-haul copper (sometimes called twinax) shielded twisted pair (STP). The IEEE also released 802.3ac in 1998, a standard that defines the extensions required to support VLAN tagging on Ethernet networks, mentioned earlier in this section. The advances continued. In 1999, 802.3ab 1000BaseT hit the market, supporting 1 Gbps transmission over four pairs of CAT 5 UTP.
The Ethernet Frame Ethernet is a layer two data link standard—in effect, a switching technique. The standard transmission entity at layer two is the frame. The frame is nothing more than a “carriage” mechanism for the user’s data, which is usually a packet. The frame, then, has a field for user data as well as a series of fields designed to carry out the responsibilities of the data link layer. These Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
88
responsibilities include framing, addressing, transparency control, and bitlevel error detection and correction. The Ethernet frame, shown in the following minitable, is designed to accomplish its task well. Each field of the frame is described in detail later. Preamble (7 bytes)
Start Frame Delimiter (1 byte)
Destination MAC Address (6 bytes)
Source MAC Length/ Address Type (6 bytes) (2 bytes)
MAC Client Data (0-n bytes)
Pad (0-p bytes)
Frame Check Sequence (4 bytes)
The Preamble field is a seven-byte sequence of alternating ones and zeroes, designed to signal the beginning of the frame and to provide a degree of synchronization as receiving devices detect the presence of a signal and prepare to process it correctly. The Start Frame Delimiter field comprises a specific sequence of eight bits with the 10101011. This field signifies the functional beginning of the frame of data. The Destination MAC Address field identifies the station that is to receive the transmitted frame. The Source MAC Address field, on the other hand, identifies the transmitting station. In 802.3, these address fields can be either two bytes or six bytes in length, although most networks today use the six-byte option. The Destination Address field can specify either an individual address targeted at a single station or a multicast address targeted at a group of stations. If the destination address consists of all “one” bits, then the address is a broadcast address and will be received by all stations on the LAN. The Length/Type field is used to indicate either the number of bytes of data contained in the MAC Client Data field or the type of protocol carried there. If the value of the field is less than or equal to 1,500, then it indicates the number of bytes in the MAC Client Data field. If it is greater than or equal to 1,536, then the field indicates the nature of the transported protocol. The MAC Client Data field contains the user data transmitted from the source to the destination. The maximum size of this field is 1,500 octets. If it is less than 64 bytes, then the Pad field that follows it in the frame is used to bring the frame to its required minimum length. The Pad field enables a “runt frame” to be augmented so that it meets the minimum frame size requirements. When used, extra bytes are added in this field. The minimum Ethernet frame size is 64 bytes, measured from the Destination MAC Address field through the frame check sequence. The Frame Check Sequence field provides a four-byte cyclical redundancy check (CRC) calculation for error checking the content of the frame. As with Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
89
all layer two error control schemes, the originating station creates the MAC frame and then calculates the CRC before transmitting the frame across the network. The calculation is performed on all the fields in the frame from the destination MAC address through the Pad fields, ignoring the preamble, start frame delimiter, and, of course, the frame check sequence. When the transmitted frame arrives at the destination device, the receiving system calculates the CRC and compares the two. If they do not match, the station assumes an error has occurred and discards the frame. The original standards for Ethernet defined the minimum frame size to be 64 octets and the maximum size to be 1,518 octets. This size includes everything from the Destination MAC Address field through the frame check sequence. In 1998, the IEEE issued 802.3ac, which extended the maximum frame size to 1,522 octets so that a VLAN tag could be included for evolving VLAN applications. The VLAN protocol enables an identifier or tag to be inserted in the frame so that the frame can be associated with the VLAN to which it pertains, so that logical traffic groups can be created for management purposes. IEEE 802.1Q defines the VLAN protocol. If the four-byte VLAN tag is present in an Ethernet frame, it is found between the Source MAC Address and the Length/Type fields. The first two bytes of the tag comprise the 802.1Q tag type, always set to a value of 0⫻8100. This value indicates the presence of the VLAN tag and indicates to a receiving station that the normal Length/Type field will be found four bytes later in the frame. The final two bytes of the VLAN tag are used for a variety of purposes. The first three bits represent a User Priority field used to assign a priority level to the information contained in the frame. The next bit is called a Canonical Format Indicator (CFI) and is used in Ethernet to indicate the presence of a Routing Information Field (RIF). The final 12 bits are the VLAN Identifier (VID) that identifies the VLAN that the frame belongs to. The format of an Ethernet frame with the VLAN identifier is shown in the following minitable: Preamble Start (7 bytes) Frame Delimiter (1 byte)
Dest. Source MAC MAC Address Address (6 bytes) (6 bytes)
Length/ Type ⫽ 802.1Q Tag Type (2 bytes)
Tag Length/ Control Type Information (2 bytes) (2 bytes)
MAC Client Data (0-n bytes)
Pad (0-p bytes)
Frame Check Sequence (4 bytes)
The Interframe Gap field defines a minimum idle period between the transmission of sequential frames. Sometimes called an Interpacket Gap field, it provides a recovery period between frames so that devices can prepare to receive the next frame. The minimum interframe gap is 9.6 Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
90
microseconds for 10 Mbps Ethernet, 960 nanoseconds for 100 Mbps Ethernet, and 96 nanoseconds for 1 Gbps Ethernet. In 1998, the IEEE approved 802.3ac, the standard that defines frame formats that support VLAN tagging on Ethernet networks.
The Special Case of Gigabit Ethernet With the arrival in 1998 of the 802.3z standard for Gigabit Ethernet, a field was added to the end of the frame to ensure that the frame would be long enough to enable collisions to propagate to all stations on the network at high transmission speeds. The field is added as needed to bring the minimum length of the frame to 512 bytes. The Gigabit Ethernet Extension field is only required in half-duplex mode, since the collision protocol is not used in full-duplex mode.
Gigabit Ethernet Frame Bursting When the 802.3z standard was released in 1998, the IEEE also added a burst mode option that enables a station to transmit a series of frames without relinquishing control of the transmission medium. It is only used with Gigabit and higher Ethernet speeds, and is only applicable in half-duplex mode. When a station is transmitting a series of short frames, this mode of operation can dramatically improve the overall performance of Gigabit Ethernet LANs. The details of burst mode operation are interesting. Once a station has successfully transmitted a single frame, it has the option to continue to transmit additional frames until it reaches a burst limit of 8,192 byte times. An interframe gap, described earlier, is inserted between each frame. In this case, however, the transmitting station populates the interframe gap with extension bits, which are nondata symbols that serve as a keepalive message and serve to identify the actual data bits by the receiving station.
A Point of Contention: Jumbo Frames In mid-1998, Alteon Networks put forward an initiative to increase the maximum size of the Data field from 1,500 octets to 9,000 octets. The initiative has been endorsed by a number of companies in the belief that larger frames would result in a more efficient network by reducing the Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
91
number of frames that have to be processed. Furthermore, the 32-bit CRC used in traditional Ethernet loses its overall effectiveness in frames larger than 12,000 octets. Alteon’s proposal restricts the use of jumbo frames to full-duplex Ethernet links only, and it describes a link negotiation protocol that enables a station to determine if the station on the other end of the segment is capable of supporting jumbo frames before it chooses to transmit them. Jumbo frames have been implemented in many systems, but they are not yet widespread. As demand grows and as IPv6 becomes more common, the technique will become more widely used.
Media Access Control (MAC) in Ethernet Both half-duplex (one way at a time transmission) and full-duplex (two-way simultaneous) transmission schemes can be implemented in Ethernet networks. Both are discussed in the paragraphs that follow.
Half-Duplex Ethernet using CSMA/CD In traditional CSMA/CD-based Ethernet, half-duplex transmissions are most commonly used. On LANs that rely on CSMA/CD, two or more stations share a common transmission medium. When a station wants to transmit a frame, it must wait for an idle period on the medium when no other station is transmitting and transmit the frame over the medium so that all other stations on the network hear the transmission. If another station tries to send data at the same time, a collision occurs. The transmitting station then sends a jamming signal to ensure that all stations are aware that the transmission failed due to a collision. The station then waits a random period of time before attempting to transmit again. This process is repeated until the frame is transmitted successfully. The rules for transmitting a frame under command of CSMA/CD are simple and straightforward. The station monitors the network for the presence of an idle carrier or the presence of a transmitting station. This is the “carrier sense” part of CSMA/CD. If a transmission is detected, the transmitting station waits but continues to monitor for an idle period. If an active carrier is not immediately detected, and the period during which no carrier is equal to or greater than the interframe gap, the station begins frame transmission. During the transmission, the frame monitors the medium for collisions. If it detects one, the station immediately stops transmitting and sends a Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
92
32-bit jamming sequence. If the collision is detected early in the frame transmission, the station completes the sending of the frame preamble before beginning the jamming sequence, which is transmitted to ensure that the length of the collision is sufficient to be noticed by the other transmitting stations. After transmitting the jamming sequence, the station waits a random period of time before attempting to transmit again, a process known as backoff. By waiting a random period before transmitting, secondary collisions are reduced. If multiple collisions occur, the transmission is still repeated, but the random delay time is progressively increased with each attempt. This serves to further reduce the probability of another collision. This process continues until one of the stations successfully transmits a frame without experiencing a collision. Once this has occurred, the station clears its collision counter.
The Backoff Process As we discussed a moment ago, the backoff process is the process by which a transmitting station determines how long to wait after a collision before attempting to retransmit. Obviously, if all stations waited the same amount of time, secondary collisions would inevitably occur. Stations avoid this eventuality by generating a random number that determines the length of time they must wait before restarting the CSMA/CD process. This period is called the backoff delay. The algorithm used to manage this process in Ethernet is officially known as truncated binary exponential backoff. We strongly urge you to memorize that name so that you can casually throw it out during cocktail parties—it’s very impressive. When a collision occurs, each station generates a random number that always falls within a specific range of values. The random number determines the number of slot times it must wait before attempting to retransmit. The values increase by an exponential factor following each failed retransmission. In the first attempt, the range is between 0 and 1. On the second attempt, it is between 0 and 3. For the third, it falls between 0 and 7. The process continues, expanding each time to a larger range of wait times. If multiple collisions occur, the range expands until it reaches 10 attempts, at which point the range is between 0 and 1,023, an enormous value. From that point on, the range of values remains fixed between 0 and 1,023. Practical limits, however, are established: If a station fails to transmit following Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
93
16 attempts, the MAC scheme issues an excessive collision error. The frame being transmitted is dropped, requiring that the application software reinitiate the transmission process. Truncated binary exponential backoff is effective as a delay minimization mechanism when LAN traffic is relatively light. When the traffic is heavy, it is less effective. When traffic is excessively heavy, collisions cause excessive collision errors to be issued, an indication that traffic has increased to the point that a single Ethernet network can no longer effectively manage it. At that point, network administrators should step in and segment the network as part of a traffic management process.
Slot Time Slot times are critical in half-duplex Ethernet networks. The time varies depending on the bandwidth of the LAN (the version of Ethernet deployed), but it is defined to be 512 bit times for networks operating at both 10 and 100 Mbps, and 4,096 bit times for Gigabit Ethernet. To guarantee the possibility of detecting collisions, the minimum transmission time for a complete frame must be at least the duration of one slot time, while the time required for collisions to propagate to all stations on the network must be less than a single slot period. Because of this design, a station cannot complete the transmission of a frame without detecting that a collision has occurred. When stations transmit frames of data across the LAN, the transmission inevitably suffers unpredictable delays because of transit delays across variable length segments, delays resulting from the electronics through which they must pass, processing delays, and hub complexities. The length of time it takes for a signal to propagate between the two most separated stations on the LAN is called the maximum propagation delay. This time period is important because it helps network designers ensure that all stations can hear collisions when they occur and respond to them. In order for a station on the LAN to detect that a collision has occurred between the frame it is transmitting and that of another station, the signal must have the opportunity to propagate across the network so that another station can detect the collision and issue a jamming signal. That jamming signal must then make its way back across the network before being detected by the transmitting station. The sum of the maximum round-trip propagation delay and the time required to transmit the jamming signal define the length of the Ethernet slot time. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
94
Slot times help to set limits on network size in terms of the maximum length of cable segments and the number of repeaters that can be in a given path. If the network becomes too large, late collisions can occur, a phenomenon that occurs when the evidence of a collision arrives too late to be useful to the MAC function. The transmitted frame is dropped and application software must detect its loss and initiate the retransmission sequence. As a result, if a collision occurs it will be detected within the first 512 bits (or 4,096 in the case of Gigabit Ethernet) of the transmission. This makes it easier for the Ethernet hardware to manage frame retransmissions following a collision. This is important because Ethernet hardware is relatively inexpensive, and because complexity adds cost, simple processes help to keep it inexpensive. In Gigabit Ethernet environments, signals propagate a very short (and in fact unmanageable) distance within the traditional 512-bit timeframe. At gigabit transmission speeds, a 512-bit timeslot would support a maximum network diameter of about 20 meters. As a result, a carrier extension has been introduced to increase the timeslot to 4,096 bits. This enables Gigabit Ethernet to support networks as broad as 200 meters—plenty for certain applications in many metro environments.
Full-Duplex Ethernet With the release of 802.3x, full-duplex Ethernet arrived on the scene, a protocol that operates effectively without the benefit of CSMA/CD. Full-duplex transmission enables stations to simultaneously transmit and receive data over a single point-to-point link. As a result, the overall throughput of the link is doubled. For full duplex to operate on an Ethernet LAN, facilities must meet following stringent requirements: ■
The medium itself must support simultaneous two-way transmission without interference. Media that meet this requirement include 10BaseT, 10BaseFL, 100BaseTX, 100BaseFX, 100BaseT2, 1000BaseCX, 1000BaseSX, 1000BaseLS, and 1000BaseT. 10Base5, 10Base2, 10BaseFP, 10BaseFB, and 100BaseT4 are incapable of supporting full-duplex transmission.
■
Full-duplex operation is restricted to point-to-point connections between two stations. Because no contention exists (only two stations are available, after all), collisions cannot occur and CSMA/CD is not
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
95
required. Frames can be transmitted at any time, limited only by the minimum interframe gap. ■
Both stations must be configured for full-duplex transmission.
Needless to say, full-duplex operation results in a far more efficient network since no collisions take place and therefore no bandwidth is wasted.
Pause Frames in a Full-Duplex Transmission Full-duplex operation includes an optional flow control mechanism called a pause frame. These frames permit one station to temporarily flow-control traffic coming from the other station, with the exception of MAC frames used to manage transmission across the network. If one station transmits a high volume of frames resulting in serious congestion at the other end, the receiving station can ask the transmitter to temporarily cease transmission, giving it the opportunity to recover from the onslaught. Once the time period specified by the overloaded station expires, the transmitter returns to normal operation. Pause frames are bidirectional, meaning that either of the peer stations on the link can issue them. Pause frames conform to the standard Ethernet frame format but also include a unique type field as well as a number of other variations on the traditional theme. For example, the destination address of the frame can be set to either the unique destination address of the station that the Pause command is directed toward or to a globally assigned multicast address that has been reserved by the IEEE for use in Pause frames. For those readers involved with bridging protocols, it is also reserved in the IEEE 802.1D bridging standard as an address type that will not be forwarded by bridges that it passes through, guaranteeing that the frame will not travel beyond its home segment. The Type field is set to 88-08 in hex to indicate to a receiving device that the frame is a MAC frame. The MAC Control Opcode field is set to 00-01 to indicate that the frame being used is a Pause frame. Incidentally, the PAUSE frame is the only type of MAC frame that is currently defined. The MAC Control Parameters field contains a 16-bit value that specifies the length of the requested Pause in units of 512-bit times. Values can range from 00-00 to FF-FF in hexadecimal. If a second Pause frame arrives before the current Pause time has expired, its parameter will replace the current Pause time. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
96
Finally, a 42-byte Reserved field (transmitted as all zeros) pads the Pause frame to the minimum Ethernet frame size. The fields for a Pause frame are as follows: Preamble Start (7 bytes) Frame Delimiter (1 byte)
Dest. MAC Address (6 bytes) ⫽ (01-80-C200-00-01) or unique DA
Source MAC Address (6 bytes)
Length/ Type (2 bytes) ⫽ 802.3 MAC Control (88-08)
MAC Control Opcode (2 bytes) ⫽ Pause (00-01)
MAC Control Parameters (2 bytes) ⫽ (00-00 to FF-FF)
Reserved (42 bytes) ⫽ All zeros
Frame Check Sequence (4 bytes)
Link Aggregation Link Aggregation, sometimes referred to as trunking, is an Ethernet feature used only in full-duplex mode. Essentially inverse multiplexing, link aggregation improves link performance and bandwidth availability between a pair of stations by enabling multiple physical facilities to serve as a single logical link. The link aggregation standard was created by the IEEE 802.3ad Working Group and entered into the formal standards in 2000. Prior to the introduction of link aggregation, it was difficult to deploy multiple links between a pair of Ethernet stations because the Spanning Tree protocol commonly deployed in bridged Ethernet networks was designed to disable secondary paths between two points to prevent loops from occurring on the network. The link aggregation protocol eliminates this problem by enabling multiple links between two devices. They can be between two switches, between a switch and a server, or between a switch and an end user station, all offering the following advantages: ■
Bandwidth can be increased incrementally. Prior to the introduction of link aggregation, bandwidth could only be increased by a factor of 10 by upgrading the 100 Mbps facility with a 1 Gbps facility.
■
Link aggregation facilitates load balancing by distributing traffic across multiple facilities. Traffic can either be shared equally across the collection of aggregated facilities, or it can be segregated according to priority and transported accordingly.
■
Multiple links imply a redundant transport capability. Under the link aggregation protocol, if a link in the collection fails, all traffic is simply redirected to another facility in the group, thus ensuring survivability.
■
The link aggregation process is completely transparent to higher-layer protocols. It operates by inserting a “shim” protocol between the MAC
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
97
protocol and the higher-layer protocols that reside above them. Each device in an aggregation of facilities transmits and receives using its own unique MAC address. As the frames reach the link aggregation protocol, the unique MAC addresses are shielded so that collectively they look like a single logical port to the higher layers. Link aggregation is limited to point-to-point links and only works on links that operate in full-duplex mode. Furthermore, all the links in an aggregation group must operate at the same bandwidth level.
Up the Stack: The Ethernet Physical Layer Over the years since Ethernet’s arrival on the LAN scene, it has gone through a series of metamorphoses. Today, it still operates at a range of bandwidth levels and is found in a variety of applications ranging from the local area to limited long-haul deployments. In the section that follows, we discuss the various flavors of Ethernet, focusing on the physical layer. We begin with the venerable Base5.
10Base5 10Base5 was the first 10 Mbps Ethernet protocol. It operated over 10millimeter coaxial cable and was commonly referred to as Thicknet because of the diameter of the cable. A word about nomenclature: 10Base5 represents a naming convention crafted during the creation of the 802 Committee standards. The 10 refers to 10 Mbps or the transmission speed, Base means that the transmission is digital baseband, and 5 refers to the 500meter maximum segment length. Other names in the series are similar. The original coax used in Thicknet installations was marked every 2.5 meters to indicate the point at which 10Base65 transceivers could be connected to the shared medium. They did not have to be connected at every 2.5-meter interval, but they did have to be placed at distances that were multiples of 2.5 meters. This separation served to minimize signal reflections that could degrade the quality of signals transmitted over the segment. Ten-millimeter Thicknet cable was typically bright yellow, with black indicator bands every 2.5 meters. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
98 A Touch of Transylvania
In 10Base5 networks, transceivers were attached using a sort of clamp that wrapped around the cable and used needle-like attachments to pierce the insulation and make contact with the conductors within. These devices were often called “vampire taps” because of the way they punctured the shared cable to get at the “life blood” within. They were often referred to as nonintrusive taps because there was no requirement to interrupt network operations to install them. In these early versions of Ethernet, end-user stations attached to the transceiver via a cable assembly known as an attachment unit interface (AUI). This AUI included the cable as well as a network interface card (NIC) that connected the cable to the NIC using a specialized 15-pin AUI connector. According to IEEE standards, this cable could be up to 50 meters in length, which means that stations could be that distance from the cable segment. A 10Base5 coaxial cable segment could be up to 500 meters in length, and as many as 100 transceivers could be attached to a single segment, as long as they were separated by multiples of 2.5 meters. Furthermore, a 10Base5 segment could comprise a single piece of cable or could comprise multiple cable sections attached end to end, as long as impedance mismatches were managed properly to prevent signal reflections within the network. Furthermore, multiple 10Base5 segments could be connected through segment repeaters, forming a large (but single and contiguous) collision domain. The repeaters regenerated the signal by transmitting it from one segment to another, amplifying the signal to maintain its signal strength throughout all the segments. The original standard permitted as many as five segments with four repeaters between any two stations. Three of the segments could be 1,500-meter coaxial segments, while the other two had to be point-to-point, 1,000-meter, interrepeater links. Each end of the three segments could have a 50-meter AUI cable, resulting in a maximum network length of 2,800 meters.
10Base2 The 10Base2 protocol supports 10 Mbps transmission over 5-millimeter coaxial cable, a configuration sometimes called Thinnet. It is also cheapnet and was the first standard introduced after traditional 10Base5 that relied on a different physical medium. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
99
In many ways, 10Base2 resembles 10Base5. Both use 50-ohm coax, and both use a bus topology. At the physical layer, the two standards share common signal transmission standards, collision-detection techniques, and signal-encoding parameters. The primary advantage of 10Base2’s thinner cable is that it is easier to install, manage, and maintain because it is lighter, more flexible, and less expensive than the thicker medium used by its predecessor. On the downside, the thinner cable offers greater transmission resistance and is therefore less desirable electrically. It supports a maximum segment length of 185 meters, compared to 10Base5’s 500 meters, and no more than 30 stations per segment compared to 100 stations on 10Base5. Although the spacing between stations on 10Base5 networks is critical for optimum performance, it is less so with 10Base2. The only limitation is that stations must be separated by no less than half a meter to minimize signal reflection. Alas, vampires are extinct with the arrival of 10Base2, which uses a BNC T-connector instead of a vampire tap to attach transceivers to the cable segment. As Figure 3-2 shows, the vertical part of the T is a plug connector that attaches directly to the internal or external NIC, while the horizontal arm of the T comprises two sockets that can be attached to BNC connectors on each end of the cable segments that are to be connected. When a station is removed from the LAN, the T connector is replaced with a Barrel connector that provides a straight-through connection. To further reduce signal reflection on the network and the resulting errors that can arise, each end of a 10Base2 segment must be terminated with a 50-ohm Bayonet-Neill-Concelman (BNC) terminator, which is electrically grounded for safety. 10Base2 Topologies Two wiring schemes are supported by 10Base2. The T connectors described earlier support a daisy chain topology in which the cable segment loops from one computer to the next. Electrical terminators (50-ohm resistors) are installed on the unused connector at each end of the chained segment, as shown in Figure 3-3.
Figure 3-2 A BNC T-connector
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
100 Figure 3-3 A 50-ohm BNC terminator, used to terminate the end of an Ethernet segment
The alternative wiring scheme is a point-to-point model in which the segment connects a single station to a 10Base2 repeater. This wiring scheme is used in environments where the structure of the building makes it impractical or impossible to daisy chain multiple computers together. The segment is terminated at the computer station on one end and is connected to a repeater on the other end. 10Base2 Summary 10Base2 operates in half-duplex mode at 10 Mbps over a single 5-millimeter coaxial cable segment. Because the cable is thinner, it is less expensive and easier to install, but because it is a narrower cable than 10Base5, transmission distances over it are somewhat limited compared to its predecessor. Further, when the protocol is deployed over a daisy-chained topology, it can be somewhat difficult to administer and troubleshoot when problems occur. The maximum segment length in 10Base2 is 185 meters, and the maximum 30 stations per segment must be separated by at least one half meter.
10BaseT The introduction of 10BaseT marked the arrival of modern Ethernet for business applications. It was the first version of the 802.3 standard to leave coax behind in favor of alternative media. 10BaseT provides a 10 Mbps transmission over two pair of Category Three twisted pair, sometimes called voicegrade twisted pair. Because it is designed to use twisted pair as its primary transmission medium, 10BaseT rapidly has become the most widely deployed version of Ethernet on the planet. The 10BaseT protocol uses one pair to transmit data and the other pair to receive. Both pairs are bundled into a single cable that often includes two additional pairs that are not used in 10BaseT. This so-called multifunction Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
101
cable may also include a bundle of fibers and one or more coaxial cables so that a single, large cable can transport voice, video, and data. Each end of the cable pairs used for 10BaseT is terminated with an eight-position RJ45 connector. Traditional 10BaseT connections are point to point. A 10BaseT cable, therefore, can have no more than two Ethernet transceivers, one at each end of the cable. In a typical installation, one end of the cable is usually connected to a 10BaseT hub, while the other end is to a computer’s NIC or to an external 10BaseT transceiver. In some cases, a pair of 10BaseT NICs is directly attached to each other using a special “crossover cable” that attaches the transmit pair of one station to the receive pair of the other, and vice versa. When attaching an NIC to a repeating hub, however, a normal cable is used and the crossover process is conducted inside the hub. 10BaseT Topology and Physical-Layer Issues When CAT 3 twisted pair is used, the maximum length per segment is 100 meters. Under some circumstances longer segments can be used as long as they meet signal quality transport standards. CAT 5 cable, which is higher quality than CAT 3 but is also more expensive, can extend the maximum segment length to 150 meters and still maintain quality stringency as long as installation requirements are met to ensure engineering compliance. Although the original Ethernet products used a shared bus topology, modern Ethernet installations rely on a collection of point-to-point links that together make up a star-wired configuration, as shown in Figure 3-4. In this scheme, the point-to-point links connect to a shared central hub that is typically mounted in a central wiring closet to facilitate maintenance, troubleshooting, and provisioning. Because 10BaseT uses separate transmit and receive pairs, it easily supports full-duplex transmission as an option. Needless to say, all components of the circuit—the media, the NIC, and the hub—must support full-duplex transport. 10BaseT Summary 10BaseT rapidly became the most widely deployed version of Ethernet LAN in the world because of its line speed and the fact that it operates over standard twisted-pair facilities. Also, because it supports a hubbed wiring scheme, it is easy to install, maintain, and troubleshoot. The only disadvantage it has is the fact that it supports shorter segment lengths than its predecessors, but its advantages far outweigh its disadvantages. In the functional domain of business, 10BaseT unquestionably dominates all other contenders. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
102 Figure 3-4 A star-wired Ethernet LAN. Each station is connected to a hub (top) that is typically (but not always) in a wiring closet.
A Brief Aside: Nomenclature With all this talk about wiring schemes, topologies, facilities, and logical and physical layouts, I thought it might be useful to take a brief side trip to explain two terms that are often misused and almost always misunderstood. These terms are topology and wiring scheme. For the purposes of our discussion, topology refers to the logical layout of the devices on the shared medium. On the other hand, wiring scheme refers to the physical layout of the network and the devices on it. A simple example will clarify the difference. Figure 3-5 shows a ring network—perhaps a token ring LAN, for example. Topologically, this network is a ring. However, to guard against ring failure caused by a physical breach, rings are often wired as shown in Figure 3-6. If Station A should become physically disconnected, for example, a relay in the hub closes and seals the breach in the ring. The wiring scheme of this LAN is a star, the form that best describes its physical layout. In fact, this layout is known as a star-wired ring. Similarly, the LAN shown in Figure 3-7 relies on a shared bus topology. However, because the entire shared Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
103
Figure 3-5 A token ring network
medium (the bus) is inside a physical hub, the single station LAN segments all emanate outward in a star wiring scheme.
10Broad36 Okay, if Ethernet works so well for LANs, perhaps it will work well for other applications like broadband video? 10Broad36 was designed to support the transmission of LAN traffic in addition to broadcast-quality video over the coax used in terrestrial community antenna television (CATV) systems. It provides 10 Mbps of bandwidth over a broadband cable system. The 36 in 10Broad36 refers to the maximum span length supported by the standard between two stations: 3,600 meters. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
104 Figure 3-6 A star-wired LAN. Each station is connected to the central hub to improve the management and survivability of the network in the event of a breach of the medium.
Hub
Figure 3-7 A bus-based LAN. All stations share access to the bus and therefore contend for its use.
CATV, which contrary to popular belief does not stand for CAble TeleVision but rather for Community Antenna TeleVision, is an analog transmission scheme in which channels are created by dividing the available transmission spectrum into 6 MHz frequency bands and assigning each band to a broadcast channel. By managing the available bandwidth properly, broadband cable systems can support multiple services, including both data and video. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
105
Broadband cable supports significantly longer segments than those supported by the original baseband 10Base5 and 10Base2. 10Broad36 segments can be as long as 1,800 meters, and all segments terminate at a head end (a signal origination point). As a result, a span of 3,600 meters can be accommodated (the far end of one segment through the head end to the far end of another segment). 10Broad36 transceivers attach directly to the cable both physically and electrically. The attachment cable can be as long as 50 meters, which adds another 100 meters to the overall end-to-end span of the system.
Fiber Optic Interrepeater Link (FOIRL) As businesses went through their inevitable morphological shifts from monolithic designs to a more distributed functional model in response to the growing demands from customers in the metro marketplace, one of the demands that became somewhat urgent was the need for greater coverage distance without sacrificing performance or bandwidth availability. One of the first major evolutionary stages that emerged was FOIRL, a two-fiber design that delivers 10 Mbps of bandwidth. It was designed to provide greater distances over point-to-point connections between repeaters. The standard was originally released in 1987, considered an early standard by those who study modern metro networks, but it was soon updated in concert with changes in the technological demands placed on it. In 1993, 10BaseFL (fiber link) was released by the IEEE, which further refined and solidified the FOIRL concept. FOIRL enables spans to be configured as long as 1,000 meters, significantly farther than any previous LAN standard. It should be noted that the newer 10BaseFL standard is backwards compatible with the older FOIRL technology. For example, a 10BaseFL transceiver can be deployed on one end of a facility with an older FOIRL transceiver used at the other. In this case, however, the maximum segment length is limited to the length specified by FOIRL (1,000 meters), not the 2,000-meter length supported by 10BaseFL.
10BaseF The next member of the Ethernet pantheon is 10BaseF. Crafted as an enhancement to the earlier FOIRL standard, 10BaseF defines 10 Mbps operation over fiber. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
106
10BaseF actually defines three segment types: 10BaseFL, 10BaseFB, and 10BaseFP. For reasons that will become clear in the paragraphs that follow, the three are not compatible with each other at the optical interface level. 10BaseFL 10BaseFL offers 10 Mbps transmission over a pair of fibers. The standard augments the FOIRL standard and supports a maximum segment length of 2,000 meters compared with FOIRL’s 1,000 meters. 10BaseFL has a variety of applications. It can be used to connect computers, repeaters, or a computer to a repeater. All segments are point to point in 10BaseFL, with a single transceiver at each end of the segment. Typically, a computer attaches to the shared infrastructure via an external 10BaseFL transceiver. The NIC in the computer attaches to the external transceiver through a standard AUI cable. The transceiver, on the other hand, attaches to the two fibers using standard ST connectors. One fiber is used to transmit data, while the other is used to receive. 10BaseFL (fiber link, sometimes fiber loop) was originally designed to work with multimode fiber, because at the time of its creation multimode fiber was affordable and readily available, while single mode was only used by large service providers in long-haul installations due to cost. The independent send and receive paths defined in 10BaseFL enable full-duplex mode to be supported as an optional configuration. In fullduplex mode, 10BaseFL supports 2,000-meter segment lengths. Furthermore, segment lengths are not restricted by the round-trip timing requirements of the CSMA/CD collision domain. In fact, segment lengths as great as 5 kilometers can be supported, and much longer segments can be installed if SMF is deployed. High-quality multimode fiber and transceivers can support segment lengths of 5 kilometers. Even longer distances can be supported with the more expensive SMF. 10BaseFL is ideal for connecting between buildings. In addition to supporting longer segment lengths, fiber optic cables are immune to electrical hazards such as lightning strikes and ground currents that can occur when connecting separate buildings. Fiber is also immune to electrical noise that can be generated by motors or other electrical equipment. 10BaseFB 10BaseFB (fiber backbone) is primarily used to interconnect repeaters at 10 Mbps, using a unique synchronous signaling protocol. The signaling protocol enables the number of repeaters in a 10 Mbps Ethernet network to be extended. Like 10BaseFL, 10BaseFB segments can be as long as 2,000 meters. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
107
Two factors limit the number of repeaters that can be deployed between two stations. First, each repeater adds a signal delay that can cause the time it takes for collisions to propagate throughout the network to exceed the maximum 512-bit time limit. Second, repeaters introduce random bit loss in the preamble field that can result in an overall reduction of the interframe gap below the required 9.6 microseconds (at 10 Mbps). 10BaseFB increases the number of allowable repeaters by reducing the amount of interframe gap loss. It does this by synchronizing the transmission interplay between the two repeaters. The interframe gap at the output of a normal repeater can be reduced by as many as eight bits. With 10BaseFB repeaters, the loss is reduced to two bits. This simplifies network design dramatically; suddenly, the only limiting factor on the size of the network is the time required for collisions to propagate. 10BaseFB can only be used on point-to-point links between repeaters, and both repeaters must support 10BaseFB. It cannot be used to connect a computer directly to a repeater. Furthermore, it does not support fullduplex mode. 10BaseFP 10BaseFP (fiber passive) relies on what is known as a “fiber optic passive star” topology. Based on passive optics, the passive star requires no power, can connect as many as 33 devices, and supports 500meter segments. The star comprises a bundle of fibers that are fused so that a signal from the ingress fiber can be transmitted to a bundle of egress fibers at 10 Mbps. Although not widely used, this model is gaining acceptance in cable television infrastructures because it requires no local power for signal propagation. In effect, the star serves as a passive hub that receives signals from 10BaseFP transceivers and distributes them to all the other 10BaseFP transceivers. It supports half-duplex transmission only.
The Arrival of Fast Ethernet (100BaseT) 100BaseT refers to the specifications and media standards for 100 Mbps Ethernet, often called Fast Ethernet. Four standards have been defined: 100BaseTX, 100BaseFX, 100BaseT4, and 100BaseT2. Each will be discussed in this section. All 100BaseT standards share a common MAC scheme, but each has its own unique physical-layer specification, sometimes referred to as a PHY, Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
108
which usually defines the characteristics of the transceiver used in the system. The PHY can be integrated directly into a repeater or NIC, or attached externally.
100BaseTX 100BaseTX is a 100 Mbps Ethernet transmission scheme using two pairs of twisted pair, one for transmit, one for receive. A typical 100BaseTX wiring scheme uses a cable that often houses four pairs. However, because of the technology’s high sensitivity to crosstalk, it is strongly recommended that the two remaining pairs be left unused. The standard supports 100-meter transmissions over 100-ohm CAT 5 UTP cable. CAT 5 is a higher-quality conductor than the CAT 3 cabling typically used with 10BaseT, and CAT 5 is rated for frequencies up to 100 MHz, while CAT 3 supports transmission up to 16 MHz. All 100BaseTX segments are point-to-point with a single transceiver at each end of the cable. Most connections are designed to connect a computer to a hub; these hubs typically have an integrated transceiver in 100BaseTX installations.
100BaseFX 100BaseFX is a two-fiber architecture that also operates at 100 Mbps. The segment maximum length is 412 meters for half-duplex links and 2,000 meters (or longer) for full-duplex designs. 100BaseFX is basically the optical equivalent of the 100BaseTX standard described earlier; the cabling and connectors found in 100BaseTX installations are simply replaced with fiber and optical connectors. Both standards use the same 4B/5B signal-encoding scheme. 100BaseFX segments are point-to-point facilities with a single transceiver at each end of the link, and the transceivers are unique to the standard. 100BaseFX enables full-duplex mode, which allows the longer 2,000-meter segment design to be implemented. As before, longer distances can be accommodated with SMF.
100BaseT4 100BaseT4 supports 100 Mbps transmissions over 4 pairs of CAT 3 (or higher) twisted pair, a strong advantage given the low cost of CAT 3. In metro operations, where cost is a factor, such advantages tend to be noticed. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
109
In 100BaseT4, one of the four pairs serves as a transmit pair, one as a receive pair, and two bidirectional pairs transmit or receive data. This model seems odd but actually makes a lot of sense. It ensures that one pair is always available for collision detection while the three remaining pairs are available for data transport. 100BaseT4 does not support the fullduplex mode of operation since it cannot support simultaneous transmitting and receiving at 100 Mbps.
100BaseT2 100BaseT2 is the only standard that supports 100 Mbps transmissions over two pairs of CAT 3 twisted pair. And unlike 100BaseTX, if additional pairs are available in the cable sheath, 100BaseT2 permits them to be used to transport voice or other LAN traffic. Even though 100BaseT2 is an innovative and powerful standard, it is not widely deployed today.
One Step Up: Gigabit Ethernet (1000BaseX) 1000BaseX, otherwise known as Gigabit Ethernet, is a relatively new arrival on the scene that has turned the LAN world on its ear and had an extraordinary impact on the metro world. Suddenly, corporate LANs are no longer hobbled by their glacially slow 10 Mbps networks or even their alltoo-slow 100 Mbps LANs. As with the Fast Ethernet series, Gigabit Ethernet standards actually define a family of standards, described later. Interestingly, these standards are based on physical-layer specifications adapted from the ANSI X3.230-1994 standard for Fibre Channel, a highspeed interface specification that has long been used for storage applications. By adopting the existing Fibre Channel specifications, 1000BaseX products found the market significantly easier to penetrate. It is important, however, that 1000BaseT does not use the Fibre Channel physical layer specifications and is not part of the 1000BaseX family of standards. 1000BaseT is described later in this part.
1000BaseLX 1000BaseLX is a fascinating standard, and the technologies that underlie it are equally interesting. The L in LX stands for long, because it relies on Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
110
long wavelength lasers to transmit significant amounts of data over longhaul fiber. The lasers specified by the standard operate in the 1270- to 1355nanometer range, and both single and multimode fiber are supported. Although long-wavelength lasers are more expensive than short-wavelength devices, they can transmit reliably over longer distances.
1000BaseSX The antithesis of 1000BaseLX, 1000BaseSX (short) relies on short-wavelength lasers operating in the 770- to 860-nanometer range to transmit data over multimode fiber. These lasers are less expensive than their longwavelength cousins and are ideal for short distances such as many of the fiber runs required in metro environments. The maximum segment length for these systems is between 275 and 550 meters, depending on the transmission mode (half- or full-duplex) and the type of fiber deployed.
1000BaseCX The more things change, the more they stay the same. The C in 1000BaseCX stands for copper because it uses specially designed shielded balanced copper cables, sometimes called twinax. Segment distances are limited to 25 meters, but even with such a short run high-speed copper is clearly needed when interconnecting network components within a building.
1000Base-T In June 1999, the IEEE released 802.3ab, the formal definition for 1000BaseT. The standard defines Gigabit Ethernet with transmission distances up to 100 meters over CAT 5 balanced copper facilities. The 1000BaseT PHY relies on full-duplex baseband transmission over four pairs of CAT 5 cable. The aggregate data rate of 1000 Mbps is achieved by transmitting 250 Mbps over each pair. Hybrids and echo cancellation devices support full-duplex transmissions by allowing data to be transmitted and received on the same pairs simultaneously.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
111
10-Gigabit Ethernet To confirm the high-speed future of Ethernet, the IEEE 802.3ae Working Group has defined two physical-layer standards for 10 Gbps optical Ethernet. These include a LAN PHY and a WAN PHY. The LAN PHY does not differ from the existing LAN standard, while the WAN PHY is new. It specifies asynchronous 10 Gbps transmission using the traditional 802.3 Ethernet frame format, stipulates minimum and maximum frame sizes, and recommends a MAC scheme at the client interface. At 1550 nm, it will initially reach 40 kilometers, expanded to 80 kilometers in coming months. Currently, 10 Gbps Ethernet is standardized for transport over fiber only; no copper twisted pair option is available as in Gigabit Ethernet. When the standard was first conceived, there was little thought given to a need for that kind of bandwidth to the desktop. However, the need is beginning to emerge and some chip manufacturers are now planning for 10 Gbps Ethernet over copper, using a design that will transmit 100 meters without a repeater. Working closely with the standards bodies, this capability will no doubt be reached soon.
Ethernet Summary So why has Ethernet suddenly become such a powerful contender in the metro space? There are numerous reasons. As stated earlier, Ethernet has been around for a long time and is easy to use and trusted. Its advantages are scalability, rapid and easy provisioning, granular bandwidth management, and simplified network management due to its single protocol nature. Table 3-1 compares the relative characteristics of Gigabit Ethernet and the soon-to-be-released 10-Gigabit Ethernet.
Service Providers A number of vendors have stepped up to the table and are now offering Ethernet access and transport over their networks. Table 3-2 displays a list of current Ethernet service providers, including their hardware vendors and offered services.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
112 Table 3-1 Gigabit Ethernet versus 10 Gigabit Ethernet
Characteristic
Gigabit Ethernet
10 Gigabit Ethernet
Physical media
Single-mode and multimode fiber, WideWave Division Multiplexing (WWDM, 802.3z)
Single-mode and multimode fiber
Distance
3.11 miles
40 kilometers
MAC
Full, half duplex
Full duplex
Coding
8B/10B
64B/66B, SONET/SDH
Physical media dependencies
850 nm, 1300 nm, 1550 nm WWDM
850 nm, 1300 nm, 1550 nm
Supports 10 Gbps TDM and DWDM?
No
Yes
Packet size
64—1,514 octets
64—1,514 octets
Source: 10 Gbps Ethernet Alliance
Table 3-2 Current Ethernet service providers
Service provider
Hardware vendor
Services
Yipes
Extreme/Riverstone
Retail access, TLAN
Cogent
Chromatis/Cisco
Retail access
Telseon
Foundry/Riverstone
Retail and wholesale access
Metromedia
Cisco
Managed connectivity
Intellispace
Riverstone
Retail access
Looking Glass
Cisco
Retail and wholesale access
Everest Broadband
Appian
Retail access
Sigma Networks
CIENA/Cisco
Wholesale Ethernet transport
Louis Dreyfus Communications
Nortel/Sycamore
Retail access, TLAN
Enkido
Agnostic
Retail access
LDCOM Networks
Sycamore
European retail access
Netigy
Cisco
Retail access
Cox
Cisco/Riverstone
Retail access
Telia
Extreme/Riverstone
Wholesale access
BT
Cisco/Riverstone
Retail and wholesale access
Qwest
ONI
Retail and wholesale access
Source: Yankee Group
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
113
Alternative Premises Schemes Of course, Ethernet is one of several premises schemes that drive traffic into the network core. Both alternative wired and wireless options exist; some of them are described here.
802.11 Another premises (some would say access) technology experiencing a great deal of attention today is 802.11, the set of standards that addresses wireless LAN (WLAN) considerations. IEEE 802.11 is a WLAN standard developed by the IEEE’s 802 committee to specify an air interface between a wireless client and a base station, as well as among a variety of wireless clients. First discussed in 1990, the standard has evolved through six draft versions and won final approval on June 26, 1997.
802.11 Physical Layer All 802 standards address themselves to both the physical and MAC layers. At the physical layer, IEEE 802.11 identifies three options for wireless LANs: diffused infrared, Direct Sequence Spread Spectrum (DSSS), and Frequency Hopping Spread Spectrum (FHSS). Although the infrared PHY operates at a baseband level, the other two radio PHYs operate at 2.4 GHz, part of the Industrial, Scientific, and Medical (ISM) band. It can be used for operating WLAN devices and does not require an end-user license. All three PHYs specify support for 1 Mbps and 2 Mbps data rates. Today 802.11 has evolved in a variety of directions, most of which have served to muddy the waters of the market. The original 802.11 WLAN standard was designed to operate at 2 Mbps within the 2.5 GHz range. Next came 802.11a, which operates at a whopping 54 Mbps in the 5 GHz range. The most recent addition is 802.11b, which operates at 11 Mbps in the 2.5 GHz range. Careful readers will notice one significant disparity here: Even though 802.11a is a much faster transport standard, it operates in a frequency band that is incompatible with either of the other two, which are in fact compatible with each other. In Europe, 802.11a competes head to head with HiperLAN II, while in Japan it runs up against High-Speed Wireless Access
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
114
(HiSWAN). For most regions of the world, 802.11b seems to be the emerging de facto standard for wireless high-speed Ethernet. And because it is backwards compatible with the original 2.5 GHz standard, it is widely accepted as a next-generation solution.
802.11 MAC Layer The 802.11 MAC layer, like CSMA/CD and token passing, presents the rules used to access the wireless medium. The primary services provided by the MAC layer are as follows: ■
Data transfer Based on a Carrier Sense Multiple Access with Collision Avoidance (CSMA/CA) algorithm as the media access scheme.
■
Association The establishment of wireless links between wireless clients and access points (APs).
■
Authentication The process of conclusively verifying a client’s identity prior to a wireless client associating with an AP. 802.11 devices operate under an open system where any wireless client can associate with any AP without verifying credentials. True authentication is possible with the use of the Wired Equivalent Privacy Protocol (WEP), which uses a shared key validation protocol similar to that used in Public Key Infrastructures (PKI). Only those devices with a valid shared key can be associated with an AP.
■
Privacy By default, data is transferred “in the clear.” Any 802.11compliant device can potentially eavesdrop on PHY 802.11 traffic that is within range. WEP encrypts the data before it is transmitted using a 40-bit encryption algorithm known as RC4. The same shared key used in authentication is used to encrypt or decrypt the data; only clients with the correct shared key can decipher the data.
■
Power management 802.11 defines an active mode, where a wireless client is powered at a level adequate to transmit and receive, and a power save mode, under which a client is not able to transmit or receive, but consumes less power while in a “standby mode” of sorts.
802.11 has garnered a great deal of attention in recent months, particularly with the perceived competition from Bluetooth, another short-distance wireless protocol. Significantly more activity is underway in the 802.11 space, however, with daily product announcements throughout the industry. Various subcommittees have been created that address everything from security to voice transport to QoS; it is a technology to watch. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
115
Home Phoneline Networking Alliance (HomePNA) The Home Phoneline Networking Alliance (HomePNA) is a not-for-profit association founded in 1998 by 11 companies to bring about the creation of uniform standards for the deployment of interoperable in-home networking solutions. The companies, 3Com, AMD, AT&T Wireless, Compaq, Conexant, Epigram, Hewlett-Packard, IBM, Intel, Lucent Technologies, and Tut Systems, are committed to the design of in-home communications systems that will enable the transport of LAN protocols across standard telephone inside wire. HomePNA operates at 1 Mbps and enables the user to employ every RJ11 jack in the house as both telephone and data ports for the interconnection of PCs, peripherals, and telephones. The standard enables for interoperability with existing access technologies, such as the x-Type Digital Subscriber Line (xDSL) and Integrated Services Digital Network (ISDN), and therefore provides a good migration strategy for small office/home office (SOHO) and telecommuter applications. The initial deployment utilizes Tut Systems’ HomeRun product, which enables telephones and computers to share the same wiring and to simultaneously transmit. Extensive tests have been performed by the HomePNA, and although some minor noise problems caused by AC power noise and telephony-coupled impedance have resulted, they have been able to eliminate the effect through the use of low-pass filters between the devices causing the noise and the jack into which they are plugged.
Bluetooth Bluetooth has been referred to as the Personal Area Network (PAN). It is a WLAN on a chip that operates in the unlicensed 2.4 GHz band at 768 Kbps, relatively slow compared to 802.11’s 11 Mbps. It does, however, include a 56 Kbps backward channel and three voice channels, and it can operate at distances of up to 100 feet (although most pundits claim 25 feet for effective operation). According to a report from Allied Business Intelligence, the Bluetooth devices market will reach $2 billion by 2005, a nontrivial number. The service model that Bluetooth supporters propose is one built around the concept of the mobile appliance. Bluetooth, named for a tenth-century Danish king (no, I don’t know whether he had a blue tooth), is experiencing growing pains and significant competition for many good reasons from 802.11. Whether Bluetooth succeeds or not is a matter still open for discussion. It’s far too early to tell. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
116 Wireless Application Protocol (WAP)
Originally developed by Phone.com, the Wireless Application Protocol (WAP) has proven to be a disappointment for the most part. Because it is designed to work with third-generation (3G) wireless systems, and because 3G systems have not yet materialized in anticipated numbers, some have taken to defining WAP to mean “Wrong Approach to Portability.” Germany’s D2 network reports that the average WAP customer uses it less than two minutes per day, which is tough to make money on when service is billed on a usage basis. 3G will be the deciding factor; when it succeeds, WAP will succeed, unless 802.11’s success continues to expand. Most believe it will.
The Mobile Appliance The mobile appliance concept is enjoying a significant amount of attention of late because it promises to herald in a whole new way of using network and computer resources—if it works as promised. The problem with so many of these new technologies is that they overpromise and underdeliver, precisely the opposite of what they’re supposed to do for a successful rollout. 3G, for example, has been billed as “the wireless Internet.” Largely as a result of that billing, it has failed. It is not the Internet—far from it. The bandwidth isn’t there, nor does it offer a device that can even begin to offer the kind of image quality that Internet users have become accustomed to. Furthermore, the number of screens that a user must go through to reach a desired site (I have heard estimates as high as 22!) is far too high. Therefore, until the user interface, content, and bandwidth challenges are met and satisfied, the technology will remain exactly that: a technology. There is no application yet, and that’s what people are willing to pay money for.
Access Technologies For the longest time, “access” described the manner in which customers reached the network for the transport of voice services. In the last 20 years, however, that definition has changed dramatically. In 1981, 20 years ago, IBM changed the world when it introduced the PC, and in 1984 the Macintosh arrived, bringing well-designed and organized computing power to the proverbial masses. Shortly thereafter, hobbyists began to take advantage of Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
117
emergent modem technology and created online databases, the first bulletin board systems that enabled people to send simple text messages to each other. This accelerated the modem market dramatically, and before long data became a common component of local loop traffic. At that time, there was no concept of Instant Messenger or of the degree to which e-mail would fundamentally change the way people communicate and do business. At the same time, the business world found more and more applications for data, and the need to move that data from place to place became a major contributor to the growth in data traffic on the world’s telephone networks. Today, then, access means much more than access to a network and its transport resources; access means access to content and services. It means putting into a place an access model that provides adequate bandwidth for an enterprise or residence customer to reach whatever online resources they need to reach, including voice, video, videoconferencing, storage farms, or databases. In the metro environment, it means providing access from an office location to a wide variety of bandwidth-intensive resources via the most cost-effective manner possible.
Marketplace Realities According to a number of demographic studies that have recently been conducted, approximately 80 million households today host home office workers, and the number is growing rapidly. These numbers include both telecommuters and those who are self-employed and work out of their homes. They require the ability to connect to remote LANs and corporate databases, retrieve e-mail, access the Web, and in some cases conduct videoconferences with colleagues and customers. The traditional bandwidthlimited local loop is not capable of satisfying these requirements with traditional modem technology. Dedicated private-line service, which would solve the problem, is far too expensive as an option, and because it is dedicated it is not particularly efficient. Other solutions are required, and these have emerged in the form of access technologies that take advantage of either a conversion to end-to-end digital connectivity (ISDN) or expanded capabilities of the traditional analog local loop (Digital Subscriber Line, [DSL]). In some cases, a whole new architectural approach is causing excitement in the industry (Wireless Local Loop [ WLL]). Finally, cable access has become a popular option as the cable infrastructure has evolved to a largely optical, all-digital system with high-bandwidth, two-way capabilities. We will discuss each of these options in the pages that follow. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
118
ISDN ISDN has been the proverbial technological roller coaster since its arrival as a concept in the late 1960s. Often described as the technology that took 15 years to become an overnight success, ISDN’s level of success has been all over the map. Internationally, it has enjoyed significant uptake as a true, digital local loop technology. In the United States, however, because of competing and often incompatible hardware implementations, high cost, and spotty availability, its deployment has been erratic at best. In market areas where providers have made it available at reasonable prices, it has been quite successful. Furthermore, it is experiencing something of a renaissance today because of DSL’s failure to capture the market. ISDN is tested, well understood, available, and fully functional. It can offer 128 Kbps of bandwidth right now, while DSL’s capability to do so is less certain. ISDN has also seen its sales numbers climb in the last year because of the dramatic growth in demand for videoconferencing services. ISDN is ideally suited for this application because it enables a user to aggregate bandwidth as required in multiples of 64 Kbps. As videoconferencing use has grown, so too have ISDN’s acceptance and deployment numbers.
ISDN Technology The traditional local loop is analog. Voice traffic is carried from an analog telephone to the central office using a frequency-modulated carrier; once at the central office, the signal is digitized for transport within the wide area long-haul backbone. On the one hand, this is good because it means that the overall transmission path has a digital component. On the other hand, the loop is still analog, and as a result the true promise of an end-to-end digital circuit cannot be realized. The circuit is only as good as the weakest link in the chain, and the weakest link is clearly the analog local loop. In ISDN implementations, local switch interfaces must be modified to support a digital local loop. Instead of using analog frequency modulation to represent voice or data traffic carried over the local loop, ISDN digitizes the traffic at the origination point, either in the voice set itself or in an adjunct device known as a terminal adapter (TA). The digital local loop then uses Time Division Multiplexing (TDM) to create multiple channels over which the digital information is transported, providing for a wide variety of truly integrated services.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
119
The Basic Rate Interface (BRI) ISDN has two implementations. The most common (and the one intended primarily for residence and small business applications) is called the Basic Rate Interface (BRI). In BRI, the two-wire local loop supports a pair of 64 Kbps digital channels known as B-Channels as well as a 16 Kbps D-Channel, which is primarily used for signaling but can also be used by the customer for low-speed (up to 9.6 Kbps) packet data. The B-Channels can be used for voice and data, and in some implementations they can be bonded together to create a single 128 Kbps channel for videoconferencing or other higher-bandwidth applications. Figure 3-8 shows a typical ISDN BRI implementation, including the alphabetic reference points that identify the “regions” of the circuit and the generic devices that make up the BRI. In this diagram, the LE is the local exchange, or switch. The NT1 is the network termination device that serves as the demarcation point between the customer and the service provider. Among other things, it converts the two-wire local loop to a four-wire interface on the customer’s premises. The terminal equipment, type 1 (TE1) is an ISDN-capable device such as an ISDN telephone. This simply means that the phone is a digital device and is therefore capable of performing the voice digitization itself. A terminal equipment, type 2 (TE2) is a non-ISDNcapable device, such as a plain old telephone service (POTS) telephone. In the event that a TE2 is used, a terminal adapter (TA) must be inserted between the TE2 and the NT1 to perform analog-to-digital conversion and rate adaptation.
Figure 3-8 The ISDN BRI
Channel 1
Signaling Channel
Channel 2
Switch
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
120
The reference points mentioned earlier identify circuit components between the functional devices just described. The U reference point is the local loop, the S/T reference point sits between the NT1 and the TEs, and the R reference point is found between the TA and the TE2.
BRI Applications Although BRI does not offer the high bandwidth that other, more recent technologies such as DSL do, its multiple 64 Kbps channels provide reasonable transport capabilities for many applications. The three most common today are remote LAN access, videoconferencing (mentioned earlier), and Internet access. For the typical remote worker, the bandwidth available through BRI is more than adequate, and the ability to bond multiple 64 Kbps channels makes content transport a manageable task.
The Primary Rate Interface (PRI) The other major implementation of ISDN is called the Primary Rate Interface (PRI). The PRI is really nothing more than the time-honored T-Carrier in that it is a four-wire local loop, uses Alternate Mark Inversion (AMI) and Binary 8 Zero Substitution (B8ZS) for ones-density control and signaling, and provides 24 channels of 64 Kbps that can be distributed among a collection of users as the customer sees fit (see Figure 3-9). In PRI, the signaling channel operates at 64 Kbps (unlike the 16 Kbps D-Channel in the BRI) and is not accessible by the user. It is used solely for signaling purposes; that is, it cannot carry user data. The primary reason for this is service protection; in the PRI, the D-Channel is used to control the 23 B-Channels and therefore requires significantly more bandwidth than the BRI D-Channel.
Figure 3-9 The ISDN PRI. The 23 (or 24) available channels can be combined and distributed however the user requires in multiples of 64 Kbps.
T-1
. . .
Up to 24 Channels (signaling channel implied).
Switch
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
121
Furthermore, the PRI standards enable multiple PRIs to share a single DChannel, which makes the D-Channel’s operational consistency all the more critical. The functional devices and reference points are not appreciably different from those of the BRI. The local loop is still identified as the U reference point. In addition to an NT1, we now add an NT2, which is a service distribution device, usually a private branch exchange (PBX), which allocates the PRI’s 24 channels to customers. This makes sense since PRIs are typically installed at businesses that employ PBXs for voice distribution. The S/T reference point is now divided; the S reference point sits between the NT2 and TEs, while the T reference point is found between the NT1 and the NT2. PRI service also has the capability to provision B-Channels as super-rate channels to satisfy the bandwidth requirements of higher bit rate services. These are called H-Channels and are provisioned as shown here: Channel
Bandwidth
H0
384 Kbps (6B)
H10
1.472 Mbps (23B)
H11
1.536 Mbps (24B)
H12
1.920 Mbps (30B)
PBX Applications The PRI’s marketplace is the business community, and its primary advantage is pair gain—that is, to conserve copper pairs by multiplexing the traffic from multiple user channels onto a shared, four-wire circuit. Inasmuch as a PRI can deliver the equivalent of 23 voice channels to a location over a single circuit, it is an ideal technology for a number of applications, including the interconnection of a PBX to a local switch, dynamic bandwidth allocation for higher-end videoconferencing applications, and interconnection between an Internet service provider’s (ISP) network and that of the local telephone company. Some PBXs are ISDN-capable on the line (customer) side, meaning that they have the capability to deliver ISDN services that emulate what would be provided over a direct connection to an ISDN-provisioned local loop. On the trunk (switch) side, the PBX is connected to the local switch via one or more T1s, which in turn provide access to the telephone network. This Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
122
arrangement results in significant savings, faster call setup, more flexible administration of trunk resources, and the capability to offer a diversity of services through the granular allocation of bandwidth as required. As the use of Internet Protocol (IP) telephony in the metro environment continues to grow because of its capability to deliver unified messaging and other distinct advantages, ISDN PRI has emerged once again as a valuable ally because of its capability to provide a digital local loop on the line side of the PBX.
Videoconferencing Although a single BRI provides adequate bandwidth for casual conferencing on a reduced-sized PC screen, PRI is preferable for high-quality, television-scale sessions. Its capability to provision bandwidth on demand makes it an ideal solution. All major videoconferencing equipment manufacturers have embraced PRI as an effective connectivity solution for their products and have consequently designed their products in accordance with accepted international standards, specifically H.261 and H.320. ISDN is only one of the so-called twisted-pair solutions that extend the capacity and lifetime of the local loop. Another is DSL, a technology family that has achieved significant attention in the last couple of years. The attention is due to both successes and failings on the part of the technology. When it works, it works extremely well. When it doesn’t, it tends to fail loudly and publicly.
Digital Subscriber Line (DSL) The access technology that has enjoyed the greatest amount of attention in recent times is DSL. It provides a good solution for remote LAN access, Internet surfing, and access for telecommuters to corporate databases. DSL came about largely as a direct result of the Internet’s success. Prior to its arrival, the average telephone call lasted approximately four minutes, a number that central office personnel used while engineering switching systems to handle expected call volumes. This number was arrived at after nearly 125 years of experience designing networks for voice customers. They knew about Erlang theory, loading objectives, and peak-calling days/weeks/seasons, and they had decades of trended data to help them anticipate load problems. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
123
In 1993, when the Internet—and with it, the World Wide Web— arrived, network performance became unpredictable as callers began to surf, often for hours on end. The average four-minute call became a thing of the past as online service providers such as America Online (AOL) began to offer flat-rate plans that did not penalize customers for long connect times. Service providers considered a number of solutions, including charging different rates for data calls than for voice calls, but none of these proved feasible until a technological solution was proposed. That solution was DSL. It is commonly believed that the local loop is incapable of carrying more than the frequencies required to support the voice band. This is a misconception. ISDN, for example, requires significantly high bandwidth to support its digital traffic. When ISDN is deployed, the loop must be modified in certain ways to eliminate its designed bandwidth limitations. For example, some long loops are deployed with load coils that “tune” the loop to the voice band. They make the transmission of frequencies above the voice band impossible, but they enable the relatively low-frequency voice band components to be carried across a long local loop. Highfrequency signals tend to deteriorate faster than low-frequency signal components, so the elimination of the high frequencies extends the transmission distance and reduces transmission impairments that would result from the uneven deterioration of a rich, multifrequency signal. These load coils therefore must be removed if digital services are to be deployed. A local loop is only incapable of transporting high-frequency signal components if it is designed not to carry them. The capacity is still there; the network design, through load coil deployment, simply makes that additional bandwidth unavailable. DSL services, especially Asymmetric DSL (ADSL), take advantage of this “disguised” bandwidth.
DSL Technology In spite of the name, DSL is an analog technology. The devices installed on each end of the circuit are sophisticated high-speed modems that rely on complex encoding schemes to achieve the high bit rates that DSL offers. Furthermore, several of the DSL services, specifically ADSL, G.Lite, Very High-speed DSL (VDSL), and Rate Adaptive DSL (RADSL), are designed to operate in conjunction with voice across the same local loop. ADSL is the most commonly deployed service and offers a great deal to both business and residence subscribers. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
124 DSL Services
DSL comes in a variety of flavors designed to provide flexible, efficient, high-speed service across the existing telephony infrastructure. From a consumer point of view, DSL, especially ADSL, offers a remarkable leap forward in terms of available bandwidth for broadband access to the Web. As content has steadily moved away from being largely text-based and has become more graphical, the demand for faster delivery services has grown. DSL may provide the solution at a reasonable cost to both the service provider and the consumer. It has also garnered the attention of the telephony service providers in a very different way. Because of its ubiquity and ease of use, cable modems have captured more than 70 percent of the broadband access market. The cable industry’s ability to package high-speed access with desirable content and their ongoing willingness to offer IP telephony for $5 per line per month, or less, has gained them enormous marketshare and resulted in an overall downward trend in the number of revenue-generating access lines owned and operated by the incumbent telcos. A number of DSL manufacturers have entered into trials with telephone companies to demonstrate that DSL can be used as the physical layer transport scheme for broadband content—specifically, video on demand. They realize that one criterion for long-term success is the ability to deliver widely varied content, and DSL may be the solution that enables them to go head to head with the cable players. Businesses will also benefit from DSL. Remote workers, for example, can rely on DSL for LAN and Internet access. Furthermore, DSL provides a good solution for VPN access as well as for ISPs looking to grow the bandwidth available to their customers. It is available in a variety of both symmetric and asymmetric services, and therefore offers a high-bandwidth access solution for a variety of applications. The most common DSL services are ADSL, High-bit-rate DSL (HDSL), HDSL-2, RADSL, Symmetric HighDensity DSL (SHDSL), and VDSL. The special case of G.Lite, a form of ADSL, will also be discussed. Asymmetric Digital Subscriber Line (ADSL) When the World Wide Web and flat-rate access charges arrived, the typical consumer phone call went from roughly four minutes in duration to several times that. All the engineering that led to the overall design of the network based on an average four-minute hold time went out the window as the switches staggered under the added load. Never was the expression, “In its success lie the seeds
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
125
of its own destruction,” more true. When ADSL arrived, it provided the offload required to save the network. The typical ADSL installation is shown in Figure 3-10. No change is required to the two-wire local loop, but minor equipment changes on either end, however, are required. First, the customer must have an ADSL modem at their premises. This device enables both the telephone service and a data access device, such as a PC, to be connected to the line. The ADSL modem is more than a simple modem, in that it also provides the Frequency Division Multiplexing (FDM) process required to separate the voice and data traffic for transport across the loop. The device that actually does this, shown in Figure 3-11, is called a splitter, in that it splits the voice traffic away from the data. It is usually bundled as part of the ADSL modem, although it can also be installed as a card in the PC, as a standalone device at the demarcation point, or on each phone at the premises. The most common implementation is to integrate the splitter as part of the DSL modem; this, however, is the least desirable implementation because
Figure 3-10 Typical DSL architecture. Voice travels in the standard voiceband, while data travels in a higher-frequency channel.
Router
Voice Switch
D S L A M
Data Traffic
Voice Traffic DSL Modem
Figure 3-11 A DSL splitter
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
126
this design can lead to crosstalk between the voice and data circuitry inside the device. When voice traffic reaches the ADSL modem, it is immediately encoded in the traditional voice band and handed off to the local switch when it arrives at the central office. The modem is often referred to as an ADSL Transmission Unit for Remote Use (ATU-R). Similarly, the device in the central office is often called an ATU-C (for central office). When a PC wants to transmit data across the local loop, the traffic is encoded in the higher-frequency band reserved for data traffic. The ADSL modem knows to do this because the traffic is arriving on a port reserved for data devices. Upon arrival at the central office, the data traffic does not travel to the local switch; instead, it stops at the ADSL modem that has been installed at the central office end of the circuit. In this case, the device is actually a bank of modems that serves a large number of subscribers and is known as a Digital Subscriber Line Access Multiplexer (DSLAM) (pronounced dee-slam). A DSLAM is shown in Figure 3-12. Instead of traveling on to the local switch, the data traffic is now passed around the switch to a router, which in turn is connected to the Internet. This process is known as a line-side redirect. The advantages of this architecture are fairly obvious. First, the redirect offloads the data traffic from the local switch so that it can go back to doing
Figure 3-12 A bay of DSLAMs rack-mounted in a central office
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
127
what it does best—switching voice traffic. Second, it creates a new line of business for the service provider. As a result of adding the router and connecting the router to the Internet, the service provider instantly becomes an ISP. This is a near-ideal combination, because it enables the service provider to become a true service provider by offering much more than simple access and transport. As the name implies, ADSL provides two-wire asymmetric service; that is, the upstream bandwidth is different from the downstream. In the upstream direction, data rates vary from 16 to 640 Kbps, while the downstream bandwidth varies from 1.5 to 8 Mbps. Because most applications today are asymmetric in nature, this disparity poses no problem for the average consumer of the service. A Word about the DSLAM This device has received a significant amount of attention recently because of the central role that it plays in the deployment of broadband access services. Obviously, the DSLAM must interface with the local switch so that it can pass voice calls on to the PSTN. However, it often interfaces with a number of other devices as well. For example, on the customer side, the DSLAM may connect to a standard ATU-C, directly to a PC with a built-in Network Interface Card (NIC), to a variety of DSL services, or to an integrated access device of some kind. On the trunk side (facing the switch), the DSLAM may connect to IP routers as described before, to an ATM switch, or to some other broadband service provider. It therefore becomes the focal point for the provisioning of a wide variety of access methods and service types. DSLAM: Centralized or Distributed? One of the major challenges that service providers face as they roll out DSL is distance. The length of a DSL local loop has stringent distance limitations, and a rather high percentage of the loops in the United States exceed those limitations. Furthermore, a high percentage of would-be DSL customers are connected to the central office via a loop carrier system, a multiplexing arrangement that allocates 64 Kbps DS0 channels to each customer as a way to conserve physical facilities (pair gain). Unfortunately, it obviates the point of DSL by bandwidth-limiting each customer. One reason these restrictions exist is because the DSLAM, the DSL service distribution device, resides in the central office. But what if it were placed closer to the customer, as shown in Figure 3-13? What if, for example, it were placed in the middle of a metro office park or in a neighborhood attached to the central office by an optical fiber? The result would be that all the limitations would disappear. Pair gain would cease to be a problem, Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
128 Figure 3-13 In this remote DSLAM network architecture, the DSLAM is located in the neighborhood or business park and is connected to the central office via an optical facility running ATM. The problem of distance and bandwidth is eliminated with this architecture, another example of core capability moving to the edge of the network.
Router ATM Voice
D S L A M
Switch DSL Modem
because the fiber would deliver more than enough bandwidth to each customer. Furthermore, local loop length would no longer be a problem because the connection between the locally placed DSLAM and a customer location would rarely (if ever) exceed the maximum allowable distance. This model of migrating the DSLAM from the central office to the periphery of the network is gaining widespread acceptance and is part of the convergence phenomenon that we have written extensively about. It is interesting that in order to achieve the benefits of convergence, divergence must be a part of the equation. By moving the intelligence and capability of the network closer to the end user, service is dramatically enhanced. Symmetric High-Density DSL (SHDSL) A new flavor of DSL is just hitting the marketplace in the form of SHDSL. This standard is based on the preexisting standards that governed SDSL, HDSL, HDSL-2, ISDN Digital Subscriber Line (IDSL), and others, and therefore is easily implementable and well understood. It offers 30 percent longer reach than earlier versions of DSL, a fact that overcomes the single greatest barrier to DSL’s widespread deployment. It also offers symmetric bandwidth over a 2-wire local loop at rates in excess of 2 Mbps, while a 4-wire version can offer bandwidth in the 5 Mbps range. The technology is rate adaptive and can therefore afford service providers the ability to offer a wide array of service plans. The primary market for SHDSL is the small-to-medium (SMB) business sector; it supports multiservice deployments including voice, video, data, and videoconferencing. Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
129
High Bit Rate DSL (HDSL) The greatest promise of HDSL is that it provides a mechanism for the deployment of four-wire T1 and E1 circuits without the need for span repeaters, which can add significantly to the cost of deploying data services. It also means that service can be deployed in a matter of days rather than weeks, something customers certainly applaud. DSL technologies in general enable repeaterless facilities as long as 12,000 feet, while traditional 4-wire data circuits such as T1 and E1 require repeaters every 6,000 feet. Consequently, many telephone companies are now using HDSL behind the scenes as a way to deploy these traditional services. By the time a service provider factors in labor and hardware, repeater installations can cost upward of $100,000 to install, and if a loop is long, there may be multiples of them. Customers often do not realize that the T1 facility they plug their equipment into is being delivered using HDSL technology at the physical layer. The important thing is that they don’t need to know. All the customer should have to care about is that a SmartJack is installed in the basement, and through that jack they have access to 1.544 Mbps or 2.048 Mbps of bandwidth—period. The real beneficiary of HDSL is the service provider because it provides pair gain. In the data world, where revenues per line are plummeting, every penny counts, especially on the capital side. HDSL-2 HDSL-2 offers the same service that HDSL offers, with one added (and significant) advantage: It does so over a single pair of wire, rather than two. It also provides other advantages. First, it was designed to improve vendor interoperability by requiring less equipment at either end of the span (transceivers and repeaters). Second, it was designed to work within the confines of standard telephone company Carrier Serving Area (CSA) guidelines by offering a 12,000-foot wire-run capability that matches the requirements of CSA deployment strategies. Rate-Adaptive DSL (RADSL) RADSL (pronounced ‘rad-zel’) is a variation of ADSL designed to accommodate changing line conditions that can affect the overall performance of the circuit. Like ADSL, it relies on DMT encoding, which selectively “populates” subcarriers with transported data, thus allowing for granular rate setting. Very High-Speed DSL (VDSL) VDSL shows promise as a provider of extremely high access bandwidth, as much as 52 Mbps over a short local loop. VDSL requires Fiber-to-the-Curb (FTTC) architecture and recommends ATM as a switching protocol; from a fiber hub, copper tail circuits deliver the signal to the business or residential premises. Bandwidth Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Part 3
130
available through VDSL ranges from 1.5 to 6 Mbps on the upstream side, and from 13 to 52 Mbps on the downstream side. Obviously, the service is distance-sensitive and actual achievable bandwidth drops as a function of distance. Nevertheless, even a short loop is respectable when such high bandwidth levels can be achieved. With VDSL, 52 Mbps can be reached over a loop length of up to 1,000 feet, a not unreasonable distance by any means. G.Lite Because the installation of splitters had proven to be a contentious and problematic issue, the need arose for a version of ADSL that did not require them. That version became known as either ADSL Lite or G.lite (after the ITU-T G-Series standards that govern much of the ADSL technology). In 1997, Microsoft, Compaq, and Intel created the Universal ADSL Working Group (UAWG)2, an organization that grew to nearly 50 members dedicated to the task of simplifying the rollout of ADSL. In effect, the organization had four stated goals: ■
To ensure that analog telephone service will work over the G.Lite deployment without remote splitters, in spite of the fact that the quality of the voice may suffer slightly due to the potential for impedance mismatch.
■
To maximize the length of deployed local loops by limiting the maximum bandwidth provided. Research indicates that customers are far more likely to notice a performance improvement when migrating from 64 Kbps to 1.5 Mbps than when going from 1.5 Mbps to higher speeds. Perception is clearly important in the marketplace, so the UAWG chose 1.5 Mbps as their downstream speed.
■
To simplify the installation and use of ADSL technology by making the process as “plug and play” as possible.
■
To reduce the cost of the service to a perceived reasonable level.
Of course, G.lite is not without its detractors. A number of vendors have pointed out that if G.lite requires the installation of microfilters at the premises on a regular basis, then true splitterless DSL is a myth, since microfilters are in effect a form of splitter. They contend that if the filters are required anyway, then they might as well be used in full-service ADSL deployments to guarantee high-quality service delivery. Unfortunately, this
2
The group “self-dissolved” in the summer of 1999 after completing what they believed their charter to be.
Downloaded from Digital Engineering Library @ McGraw-Hill (www.digitalengineeringlibrary.com) Copyright © 2004 The McGraw-Hill Companies. All rights reserved. Any use is subject to the Terms of Use as given at the website.
Enabling Technologies
Enabling Technologies
131
flies in the face of one of the key tenets of G.lite, which is to simplify and reduce the cost of DSL deployment