↪️
ccie.nyquist.eu
  • Table of Contents
  • Layer 2 Technologies
    • Ethernet Switching
      • L2 Switch Operations
      • Spanning Tree
        • 802.1d – STP
        • 802.1w – RSTP
        • 802.1s – MSTP
      • VTP 101
      • Private VLANs
      • VLANs
      • EtherChannel 101
    • Layer 2 WAN Protocols
      • HDLC
        • HDLC 101
      • PPP
        • PPP 101
        • PPP Authentication - PAP
        • PPP Authentication – CHAP
        • PPP Authentication – EAP
        • PPP Multilink
        • PPPoFR – PPP over Frame Relay
        • PPPoE – PPP over Ethernet
      • Frame Relay
        • Frame Relay 101
        • Frame Relay 102
        • Frame Relay Encapsulations – IETF vs Cisco
        • Multilink Frame Relay
        • Frame Relay Switching
        • Routing over Frame Relay
      • Bridging
        • Bridging on a router
        • MTU 101
    • Wireless
      • Wireless Principles
      • Wireless Implementations
      • Wireless Roaming
      • Wireless Authentication
        • WPA2 PSK
        • WPA2 802.1X
  • IPv4
    • IPv4 Addressing
      • Backup Interfaces
      • FHRP 101
      • DHCP 101
      • DNS 101
      • ARP 101
      • IPv4 101
      • Tunnel Interfaces
        • GRE Tunnels
      • BFD – Bidirectional Forwarding Detection
    • IPv4 Routing
      • How the routing table is built
        • How CEF works
        • Routing Order of Operations
        • NSF – Non Stop Forwarding
      • RIP
        • RIP 101
      • EIGRP
        • EIGRP 101
        • EIGRP Metric
        • More EIGRP Features
      • OSPF
        • OSPF 101
        • OSPF Areas
        • OSPF LSAs
        • OSPF Mechanics
      • IS-IS
        • IS-IS 101
        • IS-IS Mechanics – CLNP
      • BGP
        • BGP 101
        • BGP Attributes
        • More BGP
      • Route Redistribution
      • Policy based Routing
      • PfR 101 – Perfromance Routing
      • ODR
  • IPv6
    • IPv6-101
    • IPv6 Routing
    • Interconnecting IPv6 and IPv4
  • MPLS
    • MPLS 101
    • MPLS L3 VPN
  • Multicast
    • Multicast 101
    • PIM 101
    • IGMP 101
    • Inter Domain Multicast
    • IPv6 Multicast
    • Multicast features on switches
  • Security
    • NAT 101
    • NAT for Overlapping Networks
    • ACLs 101
    • ACLs 102
    • Cisco IOS Firewall
    • Zone Based Firewall
    • AAA 101
    • Controlling CLI Access
    • Control Plane
    • Switch Security
      • Switchport Traffic Control
      • Switchport Port Security
      • DHCP Snooping and DAI
      • 802.1x
      • Switch ACLs
    • IPSec VPN 101
      • IKE / ISAKMP 101
      • IPSEC Crypto Maps 101
      • IPSEC VTI 101
      • DMVPN 101
    • EAP 101
  • Network Services
    • NTP 101
    • HTTP 101
    • File Transfer 101 – TFTP & FTP
    • WCCP 101
  • QoS
    • QoS 101
    • Classification and Marking
    • Congestion Management
      • Legacy Congestion Management
      • SPD – Selective Packet Discard
      • CBWFQ
      • IP RTP Priority
    • Congestion Avoidance – WRED
    • Policing and Shaping
      • CAR 101
    • Compression and LFI
      • Header and Payload Compression
      • LFI for MultiLink PPP
    • Frame Relay QoS
      • Per VC Frame Relay QoS
    • RSVP 101
    • Switching QoS
  • Network Optimization
    • NetFlow 101 – TNF – Traditional NetFlow
    • NetFlow 102 – FNF – Flexible NetFlow
    • IP SLA 101
    • IP Accounting 101
    • Logging 101
    • SNMP and RMON 101
    • Cisco CLI Tips and Tricks
    • AutoInstall
    • Enhanced Object Tracking
    • Troubleshooting 101
    • SPAN, RSPAN, ERSPAN
  • Network Architecture
    • Hierarchical Network Architecture
    • SD Access
    • SD WAN
Powered by GitBook
On this page
  • Congestion, Delay, Jitter
  • QoS Architectures: IntServ vs DiffServ
  • IntServ
  • DiffServ
  • QoS process
  • Classification and Marking
  • Congestion Management (Queuing)
  • Congestion Avoidance (WRED)
  • Policing and Shaping
  • MQC (Modular QoS CLI)
  • Classification
  • Creating a Policy
  • Applying the Policy on an interface
  • Verifying
  • Compression and Fragmentation
  • Frame Relay QoS

Was this helpful?

  1. QoS

QoS 101

PreviousWCCP 101NextClassification and Marking

Last updated 3 years ago

Was this helpful?

Congestion, Delay, Jitter

Congestion occurs when there is more traffic to be sent than the interface can physically send. Depending on the configuration, packets that are waiting to be sent can be dropped or queued. Dropping is no good because the information is lost (UDP) or it may require retransmissions (TCP). Queuing on the other hand introduces delays. For some types of traffic this might not be a problem but for voice traffic this will result in poor quality. Another important factor is delay variation, called jitter. It will also have a negative impact on voice or real time traffic.

QoS Architectures: IntServ vs DiffServ

QoS tries to model the way network devices handle traffic in order to offer each application the required QOS level in terms of congestion, delay or jitter. When deploying QoS in a network, there are 2 models that can be used: DiffServ and IntServ.

IntServ

IntServ provides an Integrated Services model, where the sender application requests a QoS level from the network, and the network devices agree to offer the required level end-to-end, from the sender to the receiver. The routers will have to implement a signalling method to communicate with the sender and with each other in order to agree if such a service level can be delivered or not. The signalling protocol used for IntServ is ).

DiffServ

DiffServ provides a Differentiated Service model, where each router along the path from sender to the receiver must be manually configured to offer the required QoS level for the application. There is no signalling protocol involved so routers and applications do not talk to each other. So how does one router know what the application level should be? The process of Classification will do that. Traffic will be separated into different classes and each class will be treated differently. Usually, traffic classification is performed at the network edge and then the traffic is marked according to the Type of Service that should be assigned to it. For each QoS marking a PHB (Per Hop Behaviour) is configured that defines the QoS level.

QoS process

Classification and Marking

See

Congestion Management (Queuing)

Congestion Avoidance (WRED)

Policing and Shaping

CAR

MQC (Modular QoS CLI)

MQC is a Cisco CLI Component used to apply QoS settings. In newer IOS versions, HQF is used instead of MQC. HQF is a an extended implementation of MQC that allows the use of hierarchical policies. They actually work pretty much the same.

There are 3 steps when using MQC:

Classification

R(config)# class-map CLASS [match-all | match-any]
!match-all = AND (default)
!match-any = OR

Now add match criteria for the class:

R(config-cmap)# match ATTRIBUTE VALUE

Creating a Policy

A policy is a list of Classes and the actions defined for each class:

R(config)# policy-map POLICY
R(config-pmap)# class CLASS
R(config-pmap-c)#?
Policy-map class configuration commands:
  bandwidth        Bandwidth
  compression      Activate Compression
  drop             Drop all packets - used as a Security feature
  exit             Exit from class action configuration mode
  log              Log IPv4 and ARP packets - used as a Security feature
  netflow-sampler  NetFlow action
  no               Negate or set default values of a command
  police           Police
  priority         Strict Scheduling Priority for this Class
  queue-limit      Queue Max Threshold for Tail Drop
  random-detect    Enable Random Early Detection as drop policy
  service-policy   Configure Flow Next
  set              Set QoS values
  shape            Traffic Shaping

Default Class

In a policy, all traffic that is not matched by the defined classes will be considered to be inside the default class. This class can be configured using:

R(config-pmap)# class default-class

Applying the Policy on an interface

R(config-if)# service-policy {input | output } POLICY

Verifying

To verify the configuration, use one of the following commands:

R# show class-map 
R# show policy-map [POLICY class CLASS]
R# show policy-map interface INTERFACE

Compression and Fragmentation

Frame Relay QoS

Currently, the most used method of configuring QoS is via the MQC. See .

Before MQC, there were 4 types of Queuing mechanisms that could be used on an interface of a Cisco Router. They are known now as legacy methods of configuring QoS: FIFO, WFQ, PQ, CQ. See for more details.

Additionally, are ways of configuring a Priority Queue for RTP (usually voice) traffic.

There are 2 methods for congestion avoidance: Tail Drop and (Weighted) Random Early Detection. See for more details.

See for more details.

CAR is a legacy mechanism that can perform classification, marking and policing. See .

For details, see .

Now, inside each class you can define the QoS parameters for , , , and so on. You can also define a service policy for a class, which will make use of HQF, thus making the current policy the parent of the policy defined in the service policy Here are some of the things you can define for each class:

See , or look for Frame Relay Fragmentation Support.

Frame Relay offers some specific QoS configuration options which are detailed in the article.

RSVP (Resource Reservation Protocol
Classification and Marking
CBWFQ
Legacy Congestion Management
IP RTP Priority and IP RTP Reserve
Congestion Avoidance – WRED
Policing and Shaping
CAR 101
Classification using MQC
Marking
CBWFQ for Congestion Management
Class-Based WRED for Congestion Avoidance
Policing or Shaping
Header and Payload Compression
Link Fragmentation and Interleaving
Frame Relay QoS