Analyzing Technical Goals and Tradeoffs: Top-Down Network Design Chapter Two
Analyzing Technical Goals and Tradeoffs: Top-Down Network Design Chapter Two
Analyzing Technical Goals and Tradeoffs: Top-Down Network Design Chapter Two
Chapter Two
Technical Goals
Scalability
Availability
Performance
Security
Manageability
Usability
Adaptability
Affordability
Scalability
Try to learn
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
Scalability
Availability
It is refer to as a Uptime.
Availability
Availability
Availability
Percentage=
100
Availability
For example :
If network is not available for 15 minutes in
a year.
100
= 99.9971%
Availability
Example 2
A service is available 24 hours a day ,7 days
a week. One hour a Downtime is calculated
as follow:
we know 24*7=168
=[(168 hours-1 down time)/168]*100
=(167/168)*100
=99.4 % availability
10
11
Down time
12
What is reliability
Reliability indicates the dependability of the
components that make up a network such as
routers ,switches ,servers and computers
Reliability is often measured as a probability of
failure
Reliability is often used as a general term that
refers to the quality of a product
Failure rate
MTBF (Mean Time Between Failures) or
MTTF (Mean Time to Failure)
MTTR (Mean Time to Repair)
Compiled By : Miss Kiran Ayub
13
Availability
For example:
The network should not fail more than once
every 4,000 hours (166 days) and it should
be fixed within one hour
4,000/4,001 = 99.98% availability
Compiled By : Miss Kiran Ayub
14
Network Performance
Common performance factors include
Bandwidth
Throughput
Bandwidth utilization
Offered load
Accuracy
Efficiency
Delay (latency)
Response time
15
16
17
18
Performance (continued)
Offered load
Sum of all the data all network nodes have
ready to send at a particular time.
Traffic in the queue
Accuracy
The amount of useful traffic that is correctly
transmitted, relative to total traffic
19
Performance (continued)
Efficiency
20
Performance (continued)
Efficiency
21
22
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 milliseconds
23
Security
Focus on requirements first
Identify network assets
Including their value and the expected cost
associated with losing them due to a
security problem
Analyze security risks
24
Security
Network Assets
Hardware
Software
Applications
Data
Intellectual property
Trade secrets
Companys reputation
25
Security
Security Risks
Hacked network devices
Data can be intercepted, analyzed, altered,
or deleted
User passwords can be compromised
Device configurations can be changed
Reconnaissance attacks
Denial-of-service attacks
26
Manageability
Fault management
Configuration management
Accounting management
Performance management
Security management
27
Usability
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 have a negative
affect on usability:
Strict security, for example
28
Adaptability
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 Quality of Service (QoS)
requirements
29
Affordability
A network should carry the maximum
amount of traffic possible for a given
financial cost
Affordability is especially important in
campus network designs
WANs are expected to cost more, but costs
can be reduced with the proper use of
technology
Quiet routing protocols, for example
30