Дизајн на компјутерски мрежи

Вонр. Проф. д-р Анастас Мишев

Вонр. Проф. д-р Соња Филипоска
 За предметот
• Предавања 2 часа
• Аудиториски 2 часа
• Лабораториски 1 час

• Услов за потпис – без 1 лаб вежба

 Книги
• Implementing Cisco QoS v2.2
• Designing for Cisco Internetwork Solutions
(DESGN) 3 ed.
• Top-Down Network Design Third Edition
• Network Analysis, Architecture, and Design 3 ed.
 Што ќе учиме?
• Предавања
– Квалитет на сервис – QoS
– Управување со и избегнување на задушување
– Обликување на сообраќајот
– Методологија за дизајн на мрежи
– Хиерархиски модел на мрежа
– Модуларизација на мрежа
 Што ќе учиме?
• Вежби
– Напредно рутирање
– Избор на протоколи при дизајн
– BGP
– IP multicast
– IPv6 routing
– MPLS
– Metro Ethernet
– Логички и физички дизајн на мрежи
 Оценување
• Писмен испит 33 бода
• Теоретски испит 33 бода
• Тестови 10 бода
• Лабораториски вежби 14 бода
• Проектна задача 10 бода
• Бодови: Оценка:
• 50-60 6 (шест)
• 61-70 7 (седум)
• 71-80 8 (осум)
• 81-90 9 (девет)
• 91-100 10 (десет)
ПОТРЕБА ЗА ВОВЕДУВАЊЕ НА
QOS
 Converged Networks:
Quality Issues (Cont.)
• Lack of bandwidth: Multiple flows compete for a
limited amount of bandwidth.
• End-to-end delay (fixed and variable): Packets
have to traverse many network devices and links
that add up to the overall delay.
• Variation of delay (jitter): Sometimes there is a
lot of other traffic, which results in more delay.
• Packet loss: Packets may have to be dropped
when a link is congested.
 Lack of Bandwidth

Bandwidth max = min (10 Mbps, 256 kbps, 512 kbps, 100 Mbps) =
256 kbps
Bandwidth avail = bandwidth max / flows

• Maximum available bandwidth equals the bandwidth of the

weakest link
• Multiple flows are competing for the same bandwidth, resulting in
much less bandwidth being available to one single application.
 Ways to Increase Available Bandwidth

• Upgrade the link: the best solution but also the most expensive.
• Forward the important packets first.
• Compress the payload of Layer 2 frames (it takes time).
• Compress IP packet headers.
 End-to-End Delay

Delay = P1 + Q1 + P2 + Q2 + P3 + Q3 + P4 = X ms
• End-to-end delay equals a sum of all serialization,
propagation, processing, and queuing delays in the path.
• In Best-Effort networks, propagation delay is fixed,
processing and queuing delays are unpredictable.
 Types of Delay

• Processing Delay: The time it takes for a router to take the packet from
an input interface, examine it, and put it into the output queue of the
output interface
• Queuing Delay: The time a packet resides in the output queue of a
router
• Serialization Delay: The time it takes to place the “bits on the wire”
• Propagation Delay: The time it takes to transmit a packet
 Ways to Reduce Delay

• Upgrade the link; the best solution but also the most expensive.
• Forward the important packets first.
• Compress the payload of Layer 2 frames (it takes time).
• Compress IP packet headers.
 Packet Loss

• Tail drops occur when the output queue is full. These are
common drops, which happen when a link is congested.
• Many other types of drops exist, usually the result of router
congestion, that are uncommon and may require a hardware
upgrade (input drop, ignore, overrun, frame errors).
 Ways to Prevent Packet Loss

• Upgrade the link; the best solution but also the most expensive.
• Guarantee enough bandwidth to sensitive packets, increase
buffer space.
• Prevent congestion by randomly dropping less important
packets before congestion occurs.
 Summary
• Traditional networks use a separate network for delay- and
jitter-sensitive voice traffic. The voice network is
engineered to support the required number of calls. For
data traffic, protocols like TCP have been developed to
adapt to the bursty nature of a data network.
• Converged networks that support voice, video, and data
create new requirements for managing network traffic.
QoS meets those requirements.
• Converged networks suffer from different quality issues,
including lack of adequate bandwidth, end-to-end and
variable delay, and lost packets.
• Lack of bandwidth causes networks to experience different
types of delay, including processing delay, queuing delay,
serialization delay, and propagation delay.
 Summary (Cont.)
• End-to-end delay is the sum of all propagation,
processing, and queuing delays.
• Packet loss can cause applications that use TCP to
slow down. Applications that do not use TCP, such as
voice traffic, will experience poor voice quality if the
packet loss is too excessive.
• Ways to increase the available bandwidth, decrease
the delay and packet loss include:
– Increasing the link capacity
– Using QoS mechanisms such as queuing, WRED, traffic
policing and shaping, and link efficiency mechanisms such
as payload and header compression
ШТО Е QOS?
QoS Defined
QoS for Converged Networks
 Step 1:
Identify Traffic and Its Requirements
• Network audit
– Identify traffic on the
network
• Business audit
– Determine how each type of
traffic is important for
business
• Service levels required
– Determine required
response time
 QoS Traffic Requirements: Voice
• Latency < 150 ms*
• Jitter < 30 ms*
• Loss < 1%*
• 17-106 kbps guaranteed
priority bandwidth per call
• 150 bps (+ Layer 2 overhead)
guaranteed bandwidth for
voice control traffic per call
*one-way requirements
 QoS Requirements: Videoconferencing
• Latency = 150 ms*
• Jitter = 30 ms*
• Loss = 1%*
• Minimum priority bandwidth
guarantee required is:
– Video stream + 20%
– For example, a 384 kbps stream
would require 460 kbps of priority
bandwidth
*one-way requirements
 QoS Traffic Requirements: Data
• Different applications have different
traffic characteristics.
• Different versions of the same
application can have different traffic
characteristics.
• Classify data into relative-priority
model with no more than 4 to 5
classes:
– Mission-Critical Apps: Locally defined
critical applications
– Transactional: Interactive traffic,
preferred data service
– Best-Effort: Internet, e-mail, unspecified
traffic
– Less-Than-Best-Effort (Scavenger): peer-
to-peer applications
 Step 2:
Divide Traffic into Classes
 Step 3:
Define Policies for Each Traffic Class

• Set minimum bandwidth

guarantee
• Set maximum bandwidth
limits
• Assign priorities to each
class
• Manage congestion
 QoS Policy

• A network-wide
definition of the
specific levels of
quality of service
assigned to different
classes of network
traffic
 QoS Policy (Cont.)
• Align Network Resources with Business Priorities
 Summary
• QoS is the ability of the network to provide better or
“special” service to users and applications.
• Building QoS requires three steps: identify requirements,
classify network traffic, and define network-wide policies
for quality.
• Voice, video, and data have very different QoS
requirements to run effectively on a network. These
requirements affect how voice, video, and data packets are
identified.
• Business requirements determine how to define traffic into
traffic classes, from highest priority to lowest priority.
• A QoS policy is a network-wide definition of the specific
levels of QoS assigned to classes of network traffic.
ИМПЛЕМЕНТАЦИЈА НА QOS
 Methods for Implementing QoS Policy
• CLI
• MQC
• AutoQoS VoIP (voice QoS)
• AutoQoS Enterprise (voice, video, and data QoS)
• QPM
 Implementing QoS with CLI
• Traditional method
• Nonmodular
• Cannot separate traffic classification from policy
definitions
• Used to augment, fine-tune newer AutoQoS
method
 Implementing QoS with MQC
• A command syntax for configuring QoS policy
• Reduces configuration steps and time
• Configure policy, not “raw” per-interface
commands
• Uniform CLI across major Cisco IOS platforms
• Uniform CLI structure for all QoS features
• Separates classification engine from the policy
 Implementing QoS with AutoQoS
• AutoQoS VoIP supported both in the LAN and
WAN environments
• AutoQoS Enterprise supported on WAN
interfaces
• Routers can deploy Enterprise QoS policy
treatment for voice, video, and data traffic
• Switches can deploy QoS policy treatments for
voice by a single command
 Comparing Methods for
Implementing QoS
AutoQoS AutoQoS
CLI MQC VoIP Enterprise

Ease of Use Poor Easier Simple Simple

Ability to Fine-
OK Very Good Very Good Very Good
Tune

Time to Deploy Longest Average Shortest Shortest

Modularity Poor Excellent Excellent Excellent

QPM: Monitoring and Reporting
with CBQoSMIB
 Module Summary
• The problems which can lead to poor QoS for
applications running on a converged network include
lack of bandwidth, excessive delay, jitter, and packet
loss.
• QoS is the ability of the network to provide better or
“special” service to select users and applications.
• The key steps to implement QoS on a converged
network include:
– Identifying the traffic types and their requirements
– Classifying the traffic
– Defining and implementing QoS policies for each traffic
class
 Module Summary (Cont.)
• Voice, video, and data have very different
requirements and must be defined into traffic
classes.
• Different methods to implement a QoS policy on
Cisco devices include the following:
– Use existing CLI configuration mode
– Use MQC-based QoS configuration
– Use automated methods such as AutoQoS and QPM