Uh-oh, it looks like your Internet Explorer is out of date.
For a better shopping experience, please upgrade now.
Top-Down Network Design / Edition 2 available in Hardcover
Temporarily Out of Stock Online
The purpose of Top-Down Network Design, Third Edition, is to help you design networks that meet a customer’s business and technical goals. Whether your customer is another department within your own company or an external client, this book provides you with tested processes and tools to help you understand traffic flow, protocol behavior, and internetworking technologies. After completing this book, you will be equipped to design enterprise networks that meet a customer’s requirements for functionality, capacity, performance, availability, scalability, affordability, security, and manageability.
This book is for you if you are an internetworking professional responsible for designing and maintaining medium- to large-sized enterprise networks. If you are a network engineer, architect, or technician who has a working knowledge of network protocols and technologies, this book will provide you with practical advice on applying your knowledge to internetwork design.
This book also includes useful information for consultants, systems engineers, and sales engineers who design corporate networks for clients. In the fast-paced presales environment of many systems engineers, it often is difficult to slow down and insist on a top-down, structured systems analysis approach. Wherever possible, this book includes shortcuts and assumptions that can be made to speed up the network design process.
Finally, this book is useful for undergraduate and graduate students in computer science and information technology disciplines. Students who have taken one or two courses in networking theory will find Top-Down Network Design, Third Edition, an approachable introduction to the engineering and business issues related to developing real-world networks that solve typical business problems.
Changes for the Third Edition
Networks have changed in many ways since the second edition was published. Many legacy technologies have disappeared and are no longer covered in the book. In addition, modern networks have become multifaceted, providing support for numerous bandwidth-hungry applications and a variety of devices, ranging from smart phones to tablet PCs to high-end servers. Modern users expect the network to be available all the time, from any device, and to let them securely collaborate with coworkers, friends, and family. Networks today support voice, video, high-definition TV, desktop sharing, virtual meetings, online training, virtual reality, and applications that we can’t even imagine that brilliant college students are busily creating in their dorm rooms.
As applications rapidly change and put more demand on networks, the need to teach a systematic approach to network design is even more important than ever. With that need in mind, the third edition has been retooled to make it an ideal textbook for college students. The third edition features review questions and design scenarios at the end of each chapter to help students learn top-down network design.
To address new demands on modern networks, the third edition of Top-Down Network Design also has updated material on the following topics:
Modularity in network designs
The Cisco SAFE security reference architecture
The Rapid Spanning Tree Protocol (RSTP)
Internet Protocol version 6 (IPv6)
Ethernet scalability options, including 10-Gbps Ethernet and Metro Ethernet
Network design and management tools
Read an Excerpt
Chapter 5: Designing a Network Topology
Designing a backup path that has the same capacity as the primary path can beexpensive and is only appropriate if the customer's business requirements dictate abackup path with the same performance characteristics as the primary path.
If switching to the backup path requires manual reconfiguration of any components,then Users will notice disruption. For mission-critical applications, disruption isprobably not acceptable. An automatic fallover is necessary for mission-criticalapplications. BY using redundant, partial-mesh network designs, you can speedautomatic recovery time when a link falls.
One other important consideration with backup paths is that they must be tested.Sometimes network designers develop backup solutions that are never tested until acatastrophe happens. When the catastrophe occurs, the backup links do not work. Insome network designs, the backup links are used for load balancing as well asredundancy. This has the advantage that the backup path is a tested solution that isregularly used and monitored as a part of day-to-day operations. Load balancing isdiscussed in more detail in the next section.
The primary purpose of redundancy is to meet availability requirements. A secondarygoal is to improve performance by supporting load balancing across parallel links.
Load balancing must be planned and in some cases configured. Some protocols do notsupport load balancing by default. For example, when running Novell's Routing Protocol(RIP), an Internetwork Packet Exchange (IPX) router can remember only one route to aremote network. You can change this behavior on a Ciscorouter by using the ipx maximum-paths command.
In ISDN environments, You can facilitate load balancing by configuring channelaggregation. Channel aggregation on means that a router can automatically bring upmultiple ISDN B channels as bandwidth requirements increase. The Multilink Point-to-Point Protocol (MPPP) is an Internet Engineering Task Force (IETF) standard for ISDN B-channel aggregation. MPPP ensures that packets arrive in sequence at the receivingrouter. To accomplish this, data is encapsulated within the Point-to-point Protocol (PPP)and datagrams are given a sequence number. At the receiving router, PPP uses thesequence number to re-create the original data stream. Multiple channels appear as onelogical link to upper-layer protocols.Most vendor's implementations of IP routing protocols support load balancing acrossparallel links that have equal cost. (Cost values are used by routing protocols todetermine the most favorable path to a destination. Depending on the routing protocol,cost can be based on hop count, bandwidth, delay, or other factors.) Cisco supports loadbalancing across six parallel paths. With the IGRP and Enhanced [GRP protocols, Ciscosupports load balancing even when the paths do not have the same bandwidth (which isthe main metric used for measuring cost for those protocols). Using a feature calledvariance, IGRP and Enhanced IGRP can load balance across paths that do not haveprecisely the same aggregate bandwidth. Cost, metrics, and variance are discussed inmore detail in Chapter 7, "Selecting Bridging, Switching, and Routing Protocols."
Some routing protocols base cost on the number of hops to a particular destinationsThese routing protocols load balance over unequal bandwidth paths as long as thehop count is equal. Once a slow link becomes saturated, however higher capacitylinks cannot be filled. This is called Pinhole congestion. Pinhole congestion can be avoided by designing equal bandwidth links within one layer of the hierarchyusing a routing protocol that bases cost on bandwidth and has the variance feature.
Load balancing can be affected by advanced switching (forwarding) mechanismsimplemented in routers. Advanced switching processes often cache the path to remotedestinations to allow fast forwarding of subsequent packets to that destination. (Thecache obviates the need for the router CPU to look in the routing table for a path. Theresult of caching is that all packets destined to a particular destination take the same path.In this case, load balancing occurs across traffic flows to different destinations, but not ona packet-per-packet basis. Some newer technologies, such as Cisco Express Forwarding(CEF), can be configured to do packet-per-packet or destination-per-destination loadbalancing. Chapter 12, "Optimizing Your Network Design," covers CEF in more detail.
DESIGNING A CAMPUS NETWORK DESIGN TOPOLOGY
Campus network design topologies should meet a customer's goals for availability andperformance by featuring small broadcast domains, redundant distribution-laversegments, mirrored servers, and multiple ways for a workstation to reach a router for off-net communications. Campus networks should be designed using a hierarchical model sothat the network offers good performance, maintainability, and scalability.
A virtual LAN (VLAN) is an emulation of a standard LAN that allows data transfer totake place without the traditional physical restraints placed on a network. A networkadministrator can use management software to group users into a VLAN so they cancommunicate as if they were attached to the same wire, when in fact they are located ondifferent physical LAN segments. Because VLANs are based on logical instead ofphysical connections, they are very flexible.
Companies that are growing quickly cannot guarantee that employees working on thesame project will be located together. With VLANs, the physical location of a user doesnot matter. A network administrator can assign a user to a VLAN regardless of the user'slocation. In theory, VLAN assignment can be based on applications, protocols,performance requirements, security requirements, traffic-loading characteristics, or otherfactors.
VLANs allow a large flat network to be divided into subnets. This feature can be used todivide up broadcast domains. Instead of flooding all broadcasts out every port, a VLAN-enabled switch can flood a broadcast out only the ports that are part of the I same subnetas the sending station.
In the past, some companies implemented large switched campus networks with fewrouters. The goals were to keep costs down by using switches instead of routers, andprovide good performance because presumably switches were faster than routers. Withoutthe router capability of containing broadcast traffic, however, the companies neededVLANs. VLANs allow the large flat network to be divided into subnets. A router (or arouting module within a switch) was still needed for inter-subnet communication.
As routers become as fast as switches and Layer-3 functionality is added to switches,fewer companies will implement large, flat, switched networks, and there will be less of aneed for VLANs.
VLAN-based networks can be hard to manage and optimize. Also, when a VLAN isdispersed across many physical networks, traffic must flow to each of those networks,which affects the performance of the networks and adds to the capacity requirements oftrunk networks that connect VLANs....
Table of Contents
|Part I||Identifying Your Customer's Needs and Goals||3|
|Chapter 1||Analyzing Business Goals and Constraints||5|
|Using a Top-Down Network Design Methodology||5|
|Analyzing Business Goals||10|
|Analyzing Business Constraints||21|
|Business Goals Checklist||24|
|Chapter 2||Analyzing Technical Goals and Tradeoffs||27|
|Making Network Design Tradeoffs||57|
|Technical Goals Checklist||59|
|Chapter 3||Characterizing the Existing Internetwork||63|
|Characterizing the Network Infrastructure||63|
|Checking the Health of the Existing Internetwork||76|
|Tools for Characterizing the Existing Internetwork||89|
|Network Health Checklist||92|
|Chapter 4||Characterizing Network Traffic||95|
|Characterizing Traffic Flow||95|
|Characterizing Traffic Load||105|
|Characterizing Traffic Behavior||111|
|Characterizing Quality of Service Requirements||119|
|Network Traffic Checklist||128|
|Summary for Part I||128|
|Part II||Logical Network Design||131|
|Chapter 5||Designing a Network Topology||133|
|Hierarchical Network Design||133|
|Redundant Network Design Topologies||145|
|Modular Network Design||148|
|Designing a Campus Network Design Topology||150|
|Designing the Enterprise Edge Topology||170|
|Secure Network Design Topologies||180|
|Chapter 6||Designing Models for Addressing and Naming||185|
|Guidelines for Assigning Network Layer Addresses||186|
|Using a Hierarchical Model for Assigning Addresses||197|
|Designing a Model for Naming||209|
|Chapter 7||Selecting Switching and Routing Protocols||221|
|Making Decisions as Part of the Top-Down Network Design Process||222|
|Selecting Bridging and Switching Protocols||223|
|Selecting Routing Protocols||234|
|A Summary of IP, AppleTalk, and IPX Routing Protocols||261|
|Chapter 8||Developing Network Security Strategies||267|
|Network Security Design||267|
|Modularizing Security Design||278|
|Chapter 9||Developing Network Management Strategies||299|
|Network Management Design||299|
|Network Management Processes||300|
|Network Management Architectures||305|
|Selecting Protocols for Network Management||307|
|Selecting Tools for Network Management||312|
|Summary for Part II||315|
|Part III||Physical Network Design||317|
|Chapter 10||Selecting Technologies and Devices for Campus Networks||319|
|LAN Cabling Plant Design||320|
|Selecting Internetworking Devices for a Campus Network Design||341|
|An Example of a Campus Network Design||344|
|Chapter 11||Selecting Technologies and Devices for Enterprise Networks||363|
|Selecting Remote-Access Devices for an Enterprise Network Design||374|
|An Example of a WAN Design||389|
|Summary for Part III||398|
|Part IV||Testing, Optimizing, and Documenting Your Network Design||401|
|Chapter 12||Testing Your Network Design||403|
|Using Industry Tests||404|
|Building and Testing a Prototype Network System||405|
|Tools for Testing a Network Design||412|
|An Example of a Network Design Testing Scenario||416|
|Chapter 13||Optimizing Your Network Design||429|
|Optimizing Bandwidth Usage with IP Multicast Technologies||430|
|Reducing Serialization Delay||435|
|Optimizing Network Performance to Meet Quality of Service Requirements||437|
|Cisco Internetwork Operating System Features for Optimizing Network Performance||444|
|Chapter 14||Documenting Your Network Design||457|
|Responding to a Customer's Request for Proposal||458|
|Contents of a Network Design Document||460|
|Appendix A||Characterizing Network Traffic When Workstations Boot||471|
|Appendix B||References and Recommended Reading||479|