Data Network Design

Top-Down Network Design Steps

Analyze
requirements

Monitor and
optimize
network
performance

Implement
and test
network

Develop
logical
design

Develop
physical
design
Test, optimize,
and document
design
2

Network Design Steps

Phase 1 Analyze Requirements

Analisa

bisnis goal dan konstrainnya

Analisa technical goal dan tradeoffs
Karakteristikan existing network
Karakteristikan network traffic

Network Design Steps

Phase 2 Logical Network Design

Design

network topology
Design model untuk pengalamatan
dan penamaan
Pemilihan switching dan routing
protokol
Rancang strategi keamanan jaringan
Rancang strategi manajemen jaringan
4

Network Design Steps

Phase 3 Physical Network Design

Pilih

teknologi dan perangkat untuk

jaringan yang sesuai

Network Design Steps

Phase 4 Testing, Optimizing, dan

Dokumentasi Design Network
Test

the network design

Optimize the network design
Document the network design

Network Planning in Context

Strategic Business
Planning

What business do we want to be in?

What does it take to succeed ?

Market
Analysis

Where should we do our business ?

Who will be our customers and how will we win their business ?
Who will be our competitors and how will we be different ?

Business
Planning

What is our overall business case ?

How do we decide what to do first, next, as a target ?
How do we secure funding from our investors ?

Network
Planning

What is the optimal network to deliver on our business plans ?

How will we evolve our network while mitigating risk ?
How much capital expense are we talking about & when will it be needed ?

Network
Engineering
Network Integration,
Verification & Test

What do I need to know to implement my network (addressing, space, power) ?

How is my network optimized for performance, reliability, security, etc. ?
Will all the components in my network integrate properly ?
Petertest
Komisarczuk,
2003 works as expected?
How will I verify and
that theVUW,
network

July 2003

Why Network Planning ?

Align

networking objectives with business objectives

Align network roll-out with service roll-out.
Align network strategy with competitive strategy.
Address specific design decisions.
Provide long term network evolution strategy.
Provide plan for integrating new technologies /
services into the network.
Mitigate risks of emerging technologies.

Network Planning Service Overview

Analyse
Business Goals

Determine
Technical Goals

Determine
Traffic

Network
Design

Document
Network Plan

Identify
Scope

Scalability

Identify
Traffic types

Determine
Topology

Define
Evolution Plan

Identify
Network
Applications
and
Services

Availability

Determine
Traffic Flow

Service
Architectures

Optimize
Design / Evol.

Performance

Characterize
Traffic

Select
Technologies

Document
Network Plan

Security

Address QoS
Requirement

CPE
Access
Distribution Core
Interconnect

Manageability

Select
Products

Affordability

Define
Protocol Arch.

Technical
Preferences

Network
Management

Peter Komisarczuk, VUW, 2003

Revisit Network
Plan
July 2003

Required Inputs to Network Planning

Business planning resulting in

High level network direction
Understanding of economic constraints on network.

Market selection and market segmentation

Forecasted types and volumes of customers by segment.

Services selection and detailed service definition.

QoS requirements, reliability, technology constraints, etc.

Service demand forecasts

Forecasted units of each services the network should support.

Current network / systems documentation.

Network topology information
POP locations, collocations, etc.

Designated technical prime for the network planning activity.

Access to key technical, engineering, and planning resources.

Technology Decisions

Type of Services
IP is a way to provide a wide range of voice and data
services
ATM is ideal for multimedia services and bandwidth
scalability
FR is one of the most widely used WAN protocol
Ethernet provides the lowest cost broadband data
access
Voice, VPNs and other type of service
Type of Services and SLA are key considerations
when choosing backbone technology

Technology Decisions

Service Quality

an IP router backbone is sufficient if best effort service is

acceptable;
mechanisms such as int-serv and diff-serv are being delivered
for IP QOS for voice, data and video over IP

ATM backbone provides guaranteed QOS which is a

method for delivering real-time voice and video
Frame Relay provides Committed Information Rate
(CIR), has no native protection
restoration is typically left to a lower layer

Ethernet with 802.1p can provide CoS for packet based

services
MPLS can provide support for a wide range of packet
services with faster packet processing and CoS features

Business Goals
Analyse
Business Goals

Identify
Scope

Identify Network
Applications
and
Services

Municipal / Regional / Super-regional / National

Define Target Customers: Residential, Small, Regional, National

Define target service offers per customer type: Connectivity services,

Managed services, or out sourced services
Future service sets
Network technology constraints - business driven

Technical Goals
Determine
Technical Goals
Scalability

How much growth accounted for in design? Access? Core? Dist?

What will future traffic mix be (more traffic to switched/routed)?

Availability

What is required availability? Resiliency

What is the goal for MTBF and MTTR? Cost of downtime (missed SLAs)

Performance

Security

Manageability

Affordability
Technical
Preferences

What are goals in the following areas

Utilization, Delay, Delay Variation, Accuracy
Will you offer secure tunnel/VPN service? Auth. service, Dial VPN
Extranet, Layer 2 (ATM/FR), GRE, Ipsec, L2TP, LANE?
What are plans in the following areas;
Performance, Fault, Configuration, Security and Accounting Management
All the above goals must be traded off against each other to determine
the most cost effective solution.
What are specific technical constraints related to business plan,
Peter Komisarczuk, VUW, 2003
differentiation, marketability, etc. (I.e. VoIP, Wireless access, etc.)

July 2003

Traffic Determination
Determine
Traffic
Identify
Traffic types

What are the types of traffic (Client/Server, Terminal/Host, Distributed?)

What are applications (Large Data Center, Web caching?)

Determine
Traffic Flow

What percentage of traffic Intracity, Intercity, Intercountry, Off Net?

How much traffic is switched/routed? ATM vs Frame Relay? Native IP?
What are communities of interest? Is most symmetrical TDM traffic? PVC or SVC?

Characterize
Traffic

Determine Traffic Load (by application, protocol, user community)

Traffic behavior (broadcast/multicast, efficiency, error recovery, flow control)
Traffic load (duty cycle, busy hour, peak/burstiness requirements, concurrency)

Determine QoS
Requirement

Categories of Service to be supported (real time, best effort, controlled load)

ATM QoS (nrt-VBR, rt-VBR, UBR, CBR, ABR)
IP QoS (DiffServ, IntServ with RSVP, best effort)
What is delay budget for Real Time applications? Hop Count?
Is there a goal for how many classes of service to offer to clients?

Network Design
Network
Design
Determine
Topology

Hierarchical vs Flat? Traditional 3 layer model? Full Mesh/Partial Mesh/Star?

Redundant links, Load balancing, Multihoming, Diverse Paths, VPNs, Collocates,
POPs, etc.

Service
Architectures

Define how services will map across the network end-to-end.

Develop call / session flows.

Select
Technologies

Access technologies (wireless, copper, fiber, HFC; Core technologies (ATM, FR, IP,
TDM, etc.); Interconnect technologies (Gateways, Signaling, etc.)

Select
Products
Define Protocol
Architectures
Network
Management

IADs, DSLAMs, Routers, Switches, Gateways, etc.

Map end to end protocol architectures to ensure internetworking
Identify gaps and address with architecture extensions.
Centralized or distributed? Out of band access? RMON capability?
Smart CSU/DSU for statistics and SLA monitoring? Definition of Demarcation

Document Network Plan

Document
Network Plan
Define
Evolution Plan

Define target network architecture.

Define year by year evolution to target from Day 1 architecture.

Optimize
Design / Evol.

Revisit network design to: minimize network disruptions during

evolution, maximize reuse during evolution,

Document
Network Plan

Annotated diagrams
Design documents (optional)

Example of SLA Metrics

Service Metric

Agreed Value

Overall Service Availability

99.95 percent over a 2 month rolling window

Site Availability

99.50 percent over a 2 month rolling window

Network Delay

170 milliseconds for a 64 byte frame

Network Throughput

99.99 percent

Maximum Site Access Speed

512 Kilobytes per second

Maximum Number of site affected by a non

redundant Point of Failure

10

Minimum CIR (Committed Information Rate)

for each site circuit (fractional T1)

256 kbps

Minimum CIR (Committed Information Rate)

for each T1 circuit at head-end sites

1.544 Mbps

Design Considerations
Traffic

Patterns & Sinks/Sources

Physical Constraints
Designing for Node and Link Failures
Impact of Packet Processing
Service Levels

Traffic Patterns & Sink/Sources

Traffic

Patterns / Distribution
Enterprise Network v.s. Internet Backbone
Growth Projections for New and Existing Service
Time of Day Patterns and Time Zone Differences
Impact of Network Architecture and Connectivity
Variety of Traffic Types (ATM, FR, Ethernet, IP,
etc.)
Service Types (Best Effort Data, QoS Data,
Video, Voice, etc.)

Traffic Patterns & Sink/Sources

Traffic Sinks / Sources

Application Service Providers and Hosting
Sites
Caching & Content Delivery Storage
Network Access Points
Peering Relationships (Backbone,
Regional and Local)
Narrowband v.s. Broadband Subscribers
International Links

Service Level Metrics

Total Service Availability & Site Availability
Mean time between failures
Mean time between service outages
Mean/Minimum Service Restoration Time
Maximum Impact for Major Point of Failure
Capacity
Peak Data Rate, Sustained Date Rate & Minimum Data Rate
Throughput is the amount of useful data transferred across a
path
Network Access Speed is often termed Access Bandwidth
Efficiency = Throughput / Bandwidth
Network Fail over & Load Balancing Capability

Service Level Metrics

Utilization
An average measure of how much of a circuits
capacity is in use
Long term & historical data can be use to forecast
capacity
Peak to average ration should be used to design for
hot periods
Delay
End-to-end or round-trip delay
Delay variation is a measure of congestion (also
know as jitter)
Protocol Stack, Serialization, Latency of
Switch/Routers, Propagation and Queuing