Scribd
Upload
4 views

QoS

The document outlines quality requirements for voice and video calls, emphasizing acceptable latency, jitter, and loss levels. It discusses traffic classification and marking methods, including CoS and DSCP, to ensure proper service levels for different traffic types. Additionally, it covers congestion management techniques and traffic shaping/policing to maintain desired traffic rates and quality of service.

Uploaded by

mascucsy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views

QoS

The document outlines quality requirements for voice and video calls, emphasizing acceptable latency, jitter, and loss levels. It discusses traffic classification and marking methods, including CoS and DSCP, to ensure proper service levels for different traffic types. Additionally, it covers congestion management techniques and traffic shaping/policing to maintain desired traffic rates and quality of service.

Uploaded by

mascucsy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Quality Requirements for Voice and Video

● Voice and traditional standard definition video packets must meet these
recommended requirements to be an acceptable quality call:
○ Latency (delay) ≤ 150 ms
○ Jitter (variation in delay) ≤ 30 ms
○ Loss ≤ 1%
● These are one way requirements, meaning a packet sent from a phone in HQ
has 150ms to reach the phone in the branch, and vice versa
● HD video has stricter requirements

Congestion

● Congestion causes delay to packets as they wait in the queue


● As the size of the queue changes it causes jitter
● There is a limit to the size of the queue. If a packet arrives when the queue is
full the router will drop it
● Voice and video calls (and applications) will be unacceptable quality if they do
not meet their delay, jitter and loss requirements
Classification and Marking
● For a router or switch to give a particular level of service to a type of traffic, it
has to recognise that traffic first
● Common ways to recognise the traffic are by COS (Class of Service) marking,
DSCP (Differentiated Service Code Point) marking, an Access Control List, or
NBAR (Network Based Application Recognition)

Layer 2 Marking - CoS Class of Service


● There is a 3 bit field in the Layer 2 802.1q frame header which is used to carry
the CoS QoS marking
● A value of 0 – 7 can be set. The default value is 0 which is designated as Best
Effort traffic
● CoS 6 and 7 are reserved for network use
● IP phones mark their call signalling traffic as CoS 3 and their voice payload as
CoS 5

Layer 3 Marking - DSCP


● The ToS Type of Service byte in the Layer 3 IP header is used to carry the
DSCP QoS marking
● 6 bits are used which gives 64 possible values. The default value is 0 which is
designated as Best Effort traffic
● IP phones mark their call signalling traffic as 24 (CS3) and their voice payload
as 46 (EF)
● There are standard markings for other traffic types, such as 26 (AF31) for
mission critical data, and 34 (AF41) for SD video
Recognising Traffic with an ACL
● An Access Control List can be used to recognise traffic based on its Layer 3
and Layer 4 information
● For example SSH traffic going to and from the router 10.10.100.10 on TCP
port number 22

Recognising Traffic with NBAR


● NBAR (Network Based Application Recognition) can be used to recognise
traffic based on its Layer 3 to Layer 7 information
● Signatures can be downloaded from Cisco and loaded on your router which
recognise well known applications

Congestion Management
● Queuing can be used to manage congestion on routers and switches
● CBWFQ (Class Based Weighted Fair Queuing) gives bandwidth guarantees
to specified traffic types
● LLQ (Low Latency Queuing) is CBWFQ with a priority queue
● Traffic in the priority queue is sent before other traffic
MQC Modular QoS CLI
● Cisco QoS configuration uses the MQC Modular QoS CLI
● It has 3 main sections
● Class Maps define the traffic to take an action on
● Policy Maps take the action on that traffic
● Service Policies apply the policy to an interface

(This config isn’t required on the CCNA)


Shaping and Policing
● Traffic Shaping and Policing can be used to control traffic rate.
● They both measure the rate of traffic through an interface and take an action if
the rate is above a configured limit.
● Traffic shaping buffers any excess traffic so the overall traffic stays within the
desired rate limit.
● Traffic policing drops or re-marks excess traffic to enforce the specified rate
limit.
● Classification can be used to allow different rates for different traffic types.

You might also like