当前位置:首页 >> IT认证 >>

DESGN20SG


Using the Top-Down Approach to Network Design

Applying a Methodology to Network Design

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-1

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Top-Down Design Practices
Start your design here.

Design down the OSI model.

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-2

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Top-Down and Bottom-Up Approach Comparison
Top-Down Approach Incorporates organizational requirements Gives the big picture to organization and designer Bottom-Up Approach Allows a quick response to a design request Facilitates design based on previous experience Implements little or no notion of actual organizational requirements May result in inappropriate network design

Benefits

Disadvantages

Incorporates organizational requirements

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-3

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Top-Down Voice Design

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-4

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Creating a Network Decision Table
Decide which network layer requires decisions. Gather possible options for a given situation. Create a table that includes possible options and given requirements. Match given requirements with specific properties of given options. Select the option with the most matches as the most appropriate one.

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-5

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Selecting a Routing Protocol
Options Required Network Parameters Large Yes Yes Yes Good

Parameters Size of Network (Small/Medium/Large/Very Large) Enterprise-Focused (Yes/No) Use of VLSM (Yes/No) Supports Cisco Routers (Yes/No) Network Support Staff Knowledge (Good/Fair/Poor)

EIGRP

OSPF

BGP

Large Yes Yes Yes Good

Large Yes Yes Yes Fair

Very Large No Yes Yes Poor

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-6

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Assessing the Scope of the Network Design Process
Scope of Design Entire network Comments All branch office LANs upgraded to support Fast Ethernet technology Redundant equipment and links Addition of wireless client mobility Solutions to overcome bottlenecks

Campus

WAN

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-7

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Assessing the Scope of the Network Design Process
Application—Designing voice transport Network—Designing routing, addressing Physical, data link—Choosing connection type

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-8

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Structured Design Principles

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-9

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Cisco SONA Offerings

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-10

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Network Design Tools

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-11

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Planning an Implementation
If a design is composed of multiple complex components: – Implement each component separately; do not implement everything at once. Incremental implementation: – Reduces troubleshooting in case of failure – Reduces time needed to revert to previous state in case of failure

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-12

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Major Implementation Components
Each step should contain the following information:
Description Reference to design sections Detailed implementation guidelines Detailed roll-back guidelines in case of failure Estimated time for implementation

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-13

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Summary Implementation Plan
Date, Time
Phase 3 Step 1 Step 2 Step 3 Step 4 Phase 4 Step 1 Step 2 Step 3 Step 4 Phase 5 Step 1 Step 2 04/05/2007 … 04/03/2007 04/02/2007

Description
Install campus hardware Connect switches Install routers Complete cabling Verify data link layer Configure campus hardware Configure VLANs Configure IP addressing Configure routing Verify connectivity Launch campus updates into production Complete connections to existing network Verify connectivity

Implementation Details
Section 6.2.3 Section 6.2.3.1 Section 6.2.3.2 Section 6.2.3.3 Section 6.2.3.4 Section 6.2.4 Section 6.2.4.1 Section 6.2.4.2 Section 6.2.4.3 Section 6.2.4.4 Section 6.2.5 Section 6.2.5.1 Section 6.2.5.2

Complete

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-14

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Detailed Implementation Plan
Section 6.2.7.3, “Configure routing protocols in the WAN network module”:
Number of routers involved is 50. Use template from section 4.3.1, “EIGRP details.” Per router configuration: – Use passive-interface command on all nonbackbone LANs. (See section 4.2.3, “EIGRP details.”) – Use summarization according to the design. (See section 4.2.3, “EIGRP details,” and section 4.2.2, “Addressing details.”) Estimated time is 10 minutes per router. Roll-back procedure is not required.

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-15

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Pilot vs. Prototype Networks
The pilot or prototype network is used as proof of concept for the design: – A pilot network tests and verifies the design before the network is launched. – A prototype network tests and verifies a redesign in an isolated network before it is applied to the existing network. Results: – Success – Failure

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-16

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Example: Prototype Network

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-17

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Detailed Structure of a Design Document

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-18

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Summary
Designing an enterprise network is a complex project. Top-down design facilitates the process by dividing it into smaller, more manageable steps. Decision tables facilitate the selection of the most appropriate option from many possibilities. In assessing the scope of a network design, determine whether the design is for a new network or is a modification of the entire network, a single segment or module, a set of LANs, a WAN, or a remote-access network. The output of the design should be a model of the complete system. To achieve this, the top-down approach is highly recommended.

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-19

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

Summary (Cont.)
When the design is complete, you are ready to document the implementation and migration in as much detail as possible. After a design is complete, you should verify it. You can test the design in an existing or live network (pilot) or in a prototype network that will not affect the existing network. A design document lists the design requirements, documents the existing network, documents the network design, identifies the proof-of-concept strategy, and details an implementation plan.

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-20

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be

2007 Cisco Systems, Inc. All rights reserved.

DESGN v2.0—1-21

The PDF files and any printed representation for this material are the property of Cisco Systems, Inc., for the sole use by Cisco employees for personal study. The files or printed representations may not be


相关文章:
ICC1_201003_SG_02_Design_Planning_图文.pdf
ICC1_201003_SG_02_Design_Planning - Agen
SGTouch Express Design's Guide_图文.pdf
SGTouch Express Design's Guide - 用芯服务每一天 LOGO 电容式触摸感应控制芯片-SG8FXXXP Design Guide - MCU+Capacitiv...
更多相关标签: