Top-Down Network Design / Edition 3

Hardcover (Print)
Rent
Rent from BN.com
$13.40
(Save 82%)
Est. Return Date: 11/17/2014
Buy Used
Buy Used from BN.com
$44.11
(Save 41%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $18.11
Usually ships in 1-2 business days
(Save 75%)
Other sellers (Hardcover)
  • All (25) from $18.11   
  • New (14) from $44.55   
  • Used (11) from $18.11   

Overview

Top-Down Network Design, Second Edition, is a practical and comprehensive guide to designing enterprise networks that are reliable, secure, and manageable. Using illustrations and real-world examples, it teaches a systematic method for network design that can be applied to campus LANs, remote-access networks, WAN links, and large-scale internetworks.

You will learn to analyze business and technical requirements, examine traffic flow and QoS requirements, and select protocols and technologies based on performance goals. You will also develop an understanding of network performance factors such as network utilization, throughput, accuracy, efficiency, delay, and jitter. Several charts and job aids will help you apply a top-down approach to network design.

This Second Edition has been revised to include new and updated material on wireless networks, virtual private networks (VPNs), network security, network redundancy, modularity in network designs, dynamic addressing for IPv4 and IPv6, new network design and management tools, Ethernet scalability options (including 10-Gbps Ethernet, Metro Ethernet, and Long-Reach Ethernet), and networks that carry voice and data traffic.

Top-Down Network Design, Second Edition, has a companion website at http://www.topdownbook.com, which includes updates to the book, links to white papers, and supplemental information about design resources.


Keeping in mind customer's needs, goals and constraints, this practical, comprehensive network design guide provides an excellent starting point for CCIE design solutions. Author Priscilla Oppenheimer takes a top-down approach to logical and physical network design criteria, as she analyzes business and technical goals. This is not an introductory networking publication by any means; it is intended for network professionals with experience in troubleshooting, administering or managing heterogeneous internetworks. Readers should be past the Cisco Certified Design Associate (CCDA) stage and into CCDP or CCNP certification.

Read More Show Less

Product Details

  • ISBN-13: 9781587202834
  • Publisher: Cisco Press
  • Publication date: 9/8/2010
  • Series: Networking Technology Series
  • Edition number: 3
  • Pages: 447
  • Sales rank: 524,500
  • Product dimensions: 7.40 (w) x 9.20 (h) x 1.20 (d)

Meet the Author


Priscilla Oppenheimer has been developing datacommunications and networking systems since 1980 whenshe received her master's degree in Information Science fromthe University of Michigan. After many years as a softwaredeveloper, she became a technical instructor and trainingdeveloper and taught more than 2,000 network engineersfrom most of the Fortune 500 companies. Her employmentat such companies as Apple Computer, Network General,and Cisco Systems gave her a chance to troubleshoot real-world network design problems and the opportunity todevelop a practical methodology for enterprise networkdesign.
Read More Show Less

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.

Load Balancing

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.

Virtual LANs

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

Read More Show Less

Table of Contents

Ch. 1 Analyzing business goals and constraints 5
Ch. 2 Analyzing technical goals and tradeoffs 27
Ch. 3 Characterizing the existing internetwork 63
Ch. 4 Characterizing network traffic 95
Ch. 5 Designing a network topology 133
Ch. 6 Designing models for addressing and naming 185
Ch. 7 Selecting switching and routing protocols 221
Ch. 8 Developing network security strategies 267
Ch. 9 Developing network management strategies 299
Ch. 10 Selecting technologies and devices for campus networks 319
Ch. 11 Selecting technologies and devices for enterprise networks 363
Ch. 12 Testing your network design 403
Ch. 13 Optimizing your network design 429
Ch. 14 Documenting your network design 457
App. A Characterizing network traffic when workstations boot 471
Read More Show Less

Customer Reviews

Average Rating 4
( 5 )
Rating Distribution

5 Star

(3)

4 Star

(1)

3 Star

(0)

2 Star

(1)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Posted September 1, 2010

    more from this reviewer

    comprehensive coverage

    [This is a review of the 3rd edition.]

    Oppenheimer directs the book at a network analyst who might have to design a large scale network for a client company. The discussion starts by suggesting an analysis of the client's industry and needs. This is reinforced by definitions of various network performance metrics, like MTBF, MTTR, capacity, throughput, delay (latency), delay variation, etc. Chapter 2 is distinguished by a comprehensive explanation of each metric. The explanations are fairly non-technical. You don't need a degree in computer science or electrical engineering to follow it.

    The text then goes into how to characterise any existing network. This is a pragmatic recognition that you typically do not have a blank slate, with no pre-existing network. These days, a company is likely to already have a network, which presumably is developing bottlenecks or other problems, such that you have been called in to suggest upgrades.

    Later in the book, the narrative does get more involved, delving into the design of a network topology, with associated switches and routers. Various common protocols are briefly but succinctly covered. As a network designer, you need thorough acquaintance with these and the text is an excellent discourse.

    I have never seen the 1st or 2nd editions, so I'm unsure exactly how the 3rd differs. I am guessing that much of the text is unchanged. For example, the protocols have been largely stable for several years. While the advice about network topologies could also have been largely unaltered. The most recent portions of this text may pertain to the latest capabilities of switches and routers.

    The text is also admirably ecumenical in its hardware descriptions. No lock in for Cisco hardware.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)