Aula 01 Cap 01
Identificando
Requerimentos de
Design
02/07/2012
1-3
02/07/2012
1-4
1-5
02/07/2012
Criticality
(critical/important/
unimportant)
Microsoft Outlook
Important
Cisco Unified
MeetingPlace
Important
Microsoft Internet
Explorer, Opera,
Netscape
Important
Video on demand
IP/TV
Critical
Database
Oracle
Critical
Customer
applications
Critical
Application Type
Groupware
Web browsing
Customer support
Comments
1-7
Service
Comments
Security
QoS
Network management
High availability
IP telephony
Mobility
Need client laptop guest access along with mobility of employee PCs
1-9
02/07/2012
Gathered Data
(Existing Situation)
Comments
Increase competitiveness
Corporation Y, Corporation Z
Better products
Reduce costs
Reduce costs
Organizational Constraint
Gathered Data
(Existing Situation)
Comments
Budget
$650,000
Personnel
Policy
Current equipmentCisco;
prefers to stay with it
Scheduling
02/07/2012
Importance
Comments
Performance
20
Availability
25
Manageability
Security
15
Adaptability
10
Scalability
25
Total
100
Scalability is critical
Technical Constraints
Gathered Data
Comments
Existing wiring
Coaxial cabling
Bandwidth availability
Application compatibility
02/07/2012
Resumo
The PPDIOO approach reflects the life cycle phases of a standard
network.
The design methodology under PPDIOO includes these
processes:
- Identifying customer requirements
- Characterizing the existing network and sites
- Designing the network topology and solutions
Key steps in identifying customer requirements include these:
- Identifying network applications and services
- Defining organizational goals and constraints
- Defining technical goals and constraints
Characterizing the
Existing Network
and Sites
02/07/2012
1-3
02/07/2012
1-4
1-5
02/07/2012
1-6
1-7
10
02/07/2012
1-8
1-9
11
02/07/2012
12
02/07/2012
13
02/07/2012
14
02/07/2012
Accounting software
Protocol:
Servers:
Clients:
50
Scope:
Campus
Importance:
High
Average rate:
Mbps
15
02/07/2012
16
02/07/2012
17
02/07/2012
Summary Report
Characterization of the existing network results in a
summary report that is used to:
Describe the software features required in the network
Describe possible problems in the existing network
Identify the actions needed to prepare the network for the
implementation of the required features
Influence the customer requirements
18
02/07/2012
19
02/07/2012
Medium Network
Large Network
Huge Network
1-20
Switches/Routers
20-200
Switches/Routers
200-800
Switches/Routers
>800
Switches/Routers
12
12
16
12
24
16
24
c) Review documentation
12
16
16
16
16
16
16
48
80
160
16
16
24
24
40
40
16
16
32
16
16
32
32
48
48
80
80
44-48
86-98
132-180
288-384
20
02/07/2012
Summary
Characterizing an existing network entails gathering as much
information about the network as possible. Organization input, a
network audit, and traffic analysis provide the key information that
you need.
Identifying major features of the network involves gathering
network documentation and querying the organization.
The auditing process adds detail to the initial network
documentation that you created from existing documentation and
customer input.
You can manually audit a small network, but you typically need
automated tools to audit a large network.
Traffic analysis verifies the set of applications and protocols used
in the network and determines the traffic patterns of the
applications.
.
Summary (Cont.)
Tools used for traffic analysis range from manual identification
of applications using Cisco IOS Software commands in
combination with NBAR or NetFlow to those where dedicated
software- or hardware-based analyzers capture live packets or
SNMP data.
The result of the network characterization is a summary report
describing the health of the network.
21
02/07/2012
22
02/07/2012
Benefits
Disadvantages
Bottom-Up Approach
Incorporates organizational
requirements
Incorporates organizational
requirements
Implements little or
no notion of actual
organizational requirements
May result in inappropriate
network design
1-3
1-5
23
02/07/2012
Parameters
EIGRP
OSPF
BGP
Required
Network
Parameters
Size of Network
(Small/Medium/Large/Very Large)
Large
Large
Very Large
Large
Enterprise-Focused
(Yes/No)
Yes
Yes
No
Yes
Use of VLSM
(Yes/No)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Good
Fair
Poor
Good
1-6
Comments
Entire network
Campus
WAN
1-7
24
02/07/2012
1-8
1-9
25
02/07/2012
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
26
02/07/2012
Description
Implementation
Details
04/02/2007
Complete
Section 6.2.3
Step 1
Connect switches
Section 6.2.3.1
Step 2
Install routers
Section 6.2.3.2
Step 3
Complete cabling
Section 6.2.3.3
Step 4
Section 6.2.3.4
Section 6.2.4
Section 6.2.4.1
Step 2
Configure IP addressing
Section 6.2.4.2
Step 3
Step 4
Configure routing
Verify connectivity
Launch campus updates into
production
Complete connections to
existing network
Verify connectivity
Section 6.2.4.3
Section 6.2.4.4
Phase 4
Step 1
04/03/2007
Phase 5
04/05/2007
Step 1
Step 2
Date, Time
Section 6.2.5
Section 6.2.5.1
Section 6.2.5.2
27
02/07/2012
28
02/07/2012
29
02/07/2012
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.
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.
30
02/07/2012
Aula 01 - Cap. 02
Network Structure
Models
2-1
2-2
31
02/07/2012
2-3
Access Layer
Concentration point at which clients access the network
Layer 2 switching in the access layer: Defines a single broadcast
domain
Multilayer switching in the campus access layer: Optimally
satisfies the needs of a particular user through routing, filtering,
authentication, security, or quality of service
Multilayer switching in the WAN access layer: Helps control WAN
costs using dial-on-demand routing (DDR) and static routing
2-4
32
02/07/2012
2-5
Distribution Layer
Provides multilayer switching between access and core layers:
Provides media transitions
Aggregates bandwidth by concentrating multiple low-speed access links into a
high-speed core link
Determines department or workgroup access
Provides redundant connections for access devices
2-6
33
02/07/2012
2-7
Core Layer
The function of the core layer is to provide fast and
efficent data transport that:
Forms a high-speed backbone with fast transport services
Provides redundancy and fault tolerance
Offers good manageability
2-8
34
02/07/2012
2-9
2-10
35
02/07/2012
Summary
The hierarchical network model provides a modular view of a
network, making it easier to design and build a network.
The purpose of the access layer is to grant end-user access to
network resources.
The distribution layer provides aggregation for the access layer
devices and uplinks to the core layer. It is also used to enforce
policy within the network.
The core layer provides a high-speed, highly available backbone
designed to switch packets as fast as possible.
2-11
Using a Modular
Approach in
Network Design
2-1
36
02/07/2012
2-4
2-5
37
02/07/2012
2-6
2-11
38
02/07/2012
2-16
Summary
The enterprise campus infrastructure module includes the
campus infrastructure module and the server farm module.
The enterprise edge modules include the e-commerce module,
the Internet connectivity module, the remote access and VPN
module, and the WAN and MAN and site-to-site modules.
The remote enterprise modules include the remote branches,
data centers, and teleworkers.
2-22
39
02/07/2012
2-23
40