Introduction

Network Analysis and Design

Chapter Content
1.Overview
2.System Methodology
3.System Description
4.Service Description
5.Service Characteristics
6.Performance Characteristics
Chapter Objective
Objective
students will be able to explain about system
methodology in brief
students will be able to explain about system
and service description in brief
students will be able to explain about service
and performance characteristics in brief
Evaluation
Method : Short Quizz, after finish
No remidial and extra quizz
Good Network ?
Satisfy users expectation
Ease user’s works
overview
Network
Network analysis Network Design
Architecture
logical

Process to produce designs reproducible

Application defensible
requirement
Entails
Learning Users need
about
device requirement
Network Analysis
What is Network Analysis?
❖ defines, determines and describes
❖ relationships among users, applications, devices and
networks

Network analysis purpose

listen to users, understand their needs and understand the
system
Network Architecture
What is Network Achitecture?
Analysis Process

Conceptual high-level,
Information
end-to-end structure
Gathered
Network Architecture
The process

determines sets of technology and topology choices

classes of equipment
relationship among network
Network Design
❖Provides physical details for the architecture
blueprints and drawings of the network
selections of vendors and service providers
selections of equipment

❖Applying the trade-offs, dependencies and

constraints
Good Design?
Is an iterative process of continuous
refinement
Is logical and consistent
Should deliver acceptable performance and
cost metrics (trade-off)
Is more than choosing the technology!
Process Component
Tactical and Strategic Significance

Long term
In course target
adjustment Near term
target Variable
Current
Target

Existing
Network

0 1 3 5

Time (years)
Cyclic and Iterative nature of Processes
Requirement gathering
1

One
Requirements iteration Network Implementation, Test and
2 4 acceptance
and Flow of
Analysis Process

Network architecture and design

Steps in
Process
Generation of Networking
Importance of Network Analysis
Help us understand the complexity and
nuances of each network and the system
they supported
Help us understand how technology influence
networks, users, applications and devices
Model for Network Analysis - Architecture and
design

Defining problems to be addressed

Establishing and managing customer
expectations
Monitoring existing network, system and its
environment
analyzing data
developing a set of option to solve problems
Model for Network Analysis - Architecture and
design

Evaluating and optimizing options based

on various trade-offs
Selecting one or more options
Planning implementation
System Methodology
Definition
- viewing the network
- subset of network environment that impact
or interacts with as a system
System Methodology
What SM Do?
- helps in determining, defining and describing
the important characteristics and capabilities
of your network
System Description
What is a system?
set of components that work together to support or
provide connectivity, communications and services to
users of the systems
The Components of the system:
Users
Applications
Devices
Networks
System Description

Generic component of a system

Network Services
Defined as levels of performance and function
in the network

Perspectives of network services

as services being offered by the network to the entire system
as sets of requirements from the network that are expected by the
users, applications or devices
Grouping Characteristics
Service characteristics
Individual network performance and functional
parameters that are used to describe services.
● offered by the network to the system (the service offering)
● requested from the network by users, applications, or devices
(the service request).

Characteristics of services that are requested from the

network can also be considered requirements for that
network
Service Metrics
Measurements of these characteristics in the network to
monitor, verify, and manage services
Examples of service characteristics are:
Defining a security or privacy level for a group of users or an
organization
Providing 1.5 Mb/s peak capacity to a remote user
Guaranteeing a maximum round-trip delay of 100 ms to servers in a
server farm
Demarcation Points
Service Levels
Why Leveling?
- to make easier for user grouping, billing,
management

Examples
committed information rates (CIRs); levels of capacity; classes of service (CoSs);
delay and capacity characteristics; types of service (ToSs); qualities of service
(QoSs);
Service Requests, Offerings, and Metrics
Requirement Flow Down Component

User User Requirement - eg. Interaction Delay

Application Application Requirement

eg. Application Processing Delay
Device Requirement
Device eg. Maximum end-to-end delay

Network Requirement
Network eg Maximum end-to-end delay

Network Element Requirement

eg. buffer sizes or priorities
Service Request & Requirements
Service Request categories:
Best effort service
Predictable
Guaranteed
Service metrics
measureable quantities
threshold and limits of service
conformance
nonconformances
Performance limits and threshold
Performance Characteristics
12 Boundary exceeded
Nonconformance

8 Limit on Capacity
Conformance-warning
6 Threshold on Capacity
5
Threshold
exceeded
Conformance

0 Time
Performance Characteristics
Capacity
goodput, throughput, bandwidth
Delay
one directions, both directions
RMA
reliability, maintability, availability
Performance Envelopes
Technical Goals
Scalability
Availability
Performance
Security
Manageability
Usability
adaptibility
affordability
Scalability
refers to the ability to grow
try to learn
how much will grow the network in a short/medium
term
number of sites to be added
what will be needed at each of these sites
how many users will be added
how many more servers will be added
Metrics - RMA
reliability
indicator of the frequency of failure
related measure is mean time between failure (MTBF)
maintainability
generally expressed as mean time to repair (MTTR)
availability
operational availability
scheduled maintenance is not included in this calculation
Availability
Expressed as a mean time between failure
(MTBF) and mean time to repair (MTTR)
Availability = MTBF/(MTBF+MTTR)
Example:
The network should not fail more than once every
4000 hours (166 days) and it should be fixed within
one hour
4000/4001 = 99.98% availability
Availability
Usually means how much time the network is
operational
can be expressed as a percent uptime per
year, month, week, day or hour compared to
the total time in that period
24/7 operation
if network is up for 165 hour in the 168 hour week then
availability is 98.21%
SLA
Service Level Agreement
Formalization of the Quality of Service in a
contract between the customer and the service
provider
Network performance
bandwidth
throughput
bandwidth utilization
offered load
accuracy
efficiency
delay(latency) and delay variations
response time
Bandwidth vs throughput
Bandwidth and throughput are not the same thing
Bandwidth
the data carrying capacity of a circuit
specified in bits per second
Throughput
the quantity of error free data transmitted per unit of time
average rate of successful message delivery over a
communication channel
measured in b/s, byte/s, or packet per second (pps)
Throughput affect factor
the size of packets
inter frame gaps between packets
packets per second rating of devices that forward packets
client speed (CPU, memory, and HD access speed)
server speed (CPU, memory and HD access speed)
network design
protocols
distance
errors
time of day
etc
Efficiency
How much overhead is required to deliver an
amount of data
How large can packet be?
Delay from the user’s point of view
Response time
A function of the application and the
equipment the application is running on, not
just the network
most users expect to see something on the
screen in 100 to 200 miliseconds
Delay from the engineers point of view

propagation delay
transmisiton delay
packet switching delay
queuing delay
Example
a packet switch has 5 users, each offering
packets at a rate of 10 packets per second
the average length of the packet is 1024 bit
the packet switch needs to transmit this data
over a 56 kb/s WAN circuit
Load = 5 x 10 x 1024 = 51200 b/s
Utilization = 51200/56000 = 91.4%
average number of packets in queue = (0.914)/(1-0.914) - 10.63
packets
Security
Focus on requirements first
Detailed security planning
identify network assets
analyze security risk
Network assets
Hardware
Software
Applications
Data
Intellectual property
Trade secrets
Company’s reputation
Security risks
Hacked network devices
reconnaissance attacks -> scout for failures
denial of service attacks
Manageability
performance management
fault management
configuration management
security management
accounting management
usability
the ease of use with which network users can
access the network and services
networks should make users jobs easier
some design decisions will ahve a negative
affect on usability
adaptibility
avoid incorporating any design elements that
would make it hard to implement new
technologies in the future
change can come in the form of new protocols,
new business practices, new fiscal goals, new
legislation
a flexible design can adapt to changing traffic
patterns and QoS requirements.
affordability
a network should carry the maximum amount
of traffic possible for a given financial cost
affordability is especially important i campus
network designs
WAN are expected to cost more but costs can
be reduced with the proper use of
technology
Making tradeoffs
Scalability 20

Availability 30

Network performance 15

Security 5

Manageability 5

Usability 5

Adaptibility 5

Affordability 15

Total 100