Académique Documents
Professionnel Documents
Culture Documents
Copyright John Wiley & Sons, Inc. All rights reserved. Reproduction or translation of this work beyond that named in Section 117 of the United States Copyright Act without the express written consent of the copyright owner is unlawful. Requests for further information should be addressed to the Permissions Department, John Wiley & Sons, Inc. Adopters of the textbook are granted permission to make back-up copies for their own use only, to make copies for distribution to students of the course the textbook is used in, and to modify this material to best suit their instructional needs. Under no circumstances can copies be made for resale. The Publisher assumes no responsibility for errors, omissions, or damages, caused by the use of these programs or from the use of the information contained herein.
2
Chapter 9. Outline
Introduction Traditional Network Design, Building Block Network Design Needs Analysis Geographic Scope, Application Systems, Network Users, Categorizing Network Needs, Deliverables Technology Design Designing Clients and Servers, Designing Circuits and Devices, Network Design Tools, Deliverables Cost Assessment Request for Proposal, Selling the Proposal to Management, Deliverables Designing for Network Performance Managed Networks, Network Circuits, Network Devices, Minimizing Network Traffic
4
Introduction
Needs Analysis
11
Needs Analysis
The first step is to analyze the needs of network users along with the requirements of network applications. Most efforts today involve upgrades and not new network designs, so most needs may already be understood. LAN and BN design issues include improving performance, upgrading or replacing unreliable or aging equipment, or standardizing network components to simplify network management. At the MAN/WAN level, circuits are leased and upgrades involve determining if capacity increases are needed. The object of needs analysis is to produce a logical network design, which describes what network elements will be needed to meet the organizations needs.
12
13
14
Application Systems
The designers must review the applications currently used on the network and identify their location so they can be connected to the planned network (baselining). Next, applications expected to be added to the network are included. It is also helpful to identify the hardware and software requirements and protocol type for each application.
15
Network Users
In the past, application systems accounted for the majority of network traffic. Today, much network traffic comes from Internet use (i.e., e-mail and WWW). The number and type of users that will generate network traffic may thus need to be reassessed. Future network upgrades will require understanding how the use of new applications, such as video, will effect network traffic.
16
Deliverables
The key deliverable for the needs assessment stage is a set of network maps, showing the applications and the circuits, clients, and severs in the proposed network, categorized as typical or high volume.
18
19
Technology Design
20
Technology Design
After needs assessment has been completed, the next design phase is to develop a technology design (or set of possible designs) for the network.
21
Deliverables
The key deliverables at this point are a revised set of network maps that include general specifications for the hardware and software required. In most cases the crucial issue is the design of the network circuits.
26
27
Cost Assessment
28
Cost Assessment
Cost assessments goal is to assess the costs of various network alternatives produced as part of technology design. Costs to consider include:
Circuit costs for both leased circuits and cabling. Internetworking devices such as switches and routers. Hardware costs including servers, memory, NICs & UPSs. Software costs for operating systems, application software and middleware. Network management costs including special hardware, software, and training. Test and maintenance costs for monitoring equipment and supporting onsite repairs. Operations costs to run the network.
29
Network Requirements
Choice sets of possible network designs (hardware, software, circuits); Mandatory, desirable, and wish list items, Security and control requirements; Response time requirements; Guidelines for proposing new network designs
Service Requirements
Implementation time plan; Training courses and materials; Support services (e.g., spare parts on site); Reliability and performance guarantees
Bidding Process
Time schedule for the bidding process; Ground rules; Bid evaluation criteria; Availability of additional information
Deliverables
There are three key deliverables for this step:
1. An RFP issued to potential vendors. 2. After the vendor has been selected, the revised set of network maps including the final technology design, complete with selected components. 3. The business case written to support the network design, expressed in terms of business objectives.
33
34
39
Policy-based Management
In policy-based management, the network manager uses special software to set priority policies for network traffic. These take effect when the network becomes busy. For example, videoconferencing might be given a high priority since delays will have the highest impact on the performance of that application.
40
Traffic Analysis
The easy way to manage network traffic growth is simply to upgrade heavily used circuits. A more sophisticated approach is to do traffic analysis. Consider the network in Figure 9-10:
The Toronto-Dallas network segment is heavily used (thick line), but the traffic is mostly moving between LA and NY. The solution is to create a new LA to NY segment (dashed line).
41
42
Network Devices
Since network devices vary in their characteristics, a networks performance will be influenced by the devices selected to operate on it. Three important factors to network performance that are related to network device characteristics are:
Device latency Device memory Load balancing
44
Device Latency
Latency is the delay (waiting time) that occurs when a device processes a message. Slow speed devices have high latency, while high speed devices have low latency. The fastest devices run at wire speed. Latency becomes a critical issue under high traffic conditions since high latency devices can create traffic congestion. This is similar to the way that long lines of traffic form at tollbooths on highways during rush hour.
45
Device Memory
Memory and latency are related, since any device that operates at less than wire speed may need to store newly arrived packets. Otherwise packets will need to be retransmitted, making the traffic situation worse. Memory is also important for servers since memory access speeds are many times faster than hard disk access times. The larger the memory a server has, the more likely it is able to process a request quickly, so Web and file servers should have the greatest amount of memory practical.
46
Load Balancing
Load balancing means sharing the processing load between servers. A separate load balancing server is usually needed to allocate the work between processors. The load-balancing server then allocates tasks to the other processors, using an algorithm such as a round robin formula. An example of this is shown in Figure 9-11.
47
48
51
52
53
End of Chapter 9
54