Study guide
11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE
Cisco 350-801 CLCOR CCNP/CCIE Collaboration Core v2.0
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Collaboration Architecture, Deployment Models, Sizing & Upgrades
1.1 Collaboration Architecture & Deployment Models 1.2 Capacity Planning, Sizing & Bandwidth Considerations 1.3 High Availability, Redundancy & Disaster Recovery 1.4 Cisco Unified CM Cluster Upgrade Process
2 Chapter 2: Edge Architecture, Security & Network Services
2.1 Collaboration Edge Architecture: CUBE & Expressway 2.2 Security Protocols & PKI: SSO, OAuth, TLS & SRTP 2.3 Network Infrastructure Services: DNS, NTP, DHCP & LDAP
3 Chapter 3: Protocols, Codecs & Endpoint Provisioning
3.1 SIP Signaling Architecture & Call Flows 3.2 Session Description Protocol (SDP) & Early Offer vs. Delayed Offer 3.3 Audio/Video Codecs & DTMF Relay 3.4 Endpoint Deployment, Onboarding & Troubleshooting
4 Chapter 4: CUCM Dial Plan Fundamentals & Digit Analysis
4.1 Partitions and Calling Search Spaces (CSS) 4.2 Route Patterns, Route Groups & Route Lists 4.3 Translation Patterns, Transformation Patterns & Digit Manipulation 4.4 Globalized Call Routing & Local Route Group (LRG)
5 Chapter 5: Advanced Call Control, Call Routing & User Management
5.1 Call Admission Control (CAC), Locations & AAR 5.2 Toll Fraud Prevention & Call Privileges 5.3 CUCM User Management, LDAP Integration & RBAC 5.4 Administrative XML (AXL) API & Dial-Plan Troubleshooting Tools
6 Chapter 6: Cisco Unity Connection & Voicemail Integration
6.1 Cisco Unity Connection Architecture & SIP Integration 6.2 Mailbox Provisioning, User Templates & Class of Service 6.3 Message Waiting Indication (MWI) & Troubleshooting 6.4 Call Handlers & Directory Handlers
7 Chapter 7: IOS XE Voice Gateways, CUBE & Media Resources
7.1 Cisco IOS XE Voice Gateways & Dial Peers 7.2 Voice Translation Rules and Translation Profiles 7.3 Cisco Unified Border Element (CUBE) Configuration & Redundancy 7.4 IOS XE Media Resources & DSP Management
8 Chapter 8: Webex Architecture, Control Hub, Meetings & Messaging
8.1 Webex Suite Overview & Control Hub Architecture 8.2 Cloud Identity Management, SCIM & Directory Connector 8.3 Webex Developer Platform & APIs 8.4 Configuring Webex Cloud Meetings 8.5 Configuring Webex Cloud Messaging
9 Chapter 9: Webex Calling Routing, Permissions & PSTN Connectivity
9.1 Webex Calling Architecture, Locations & Number Management 9.2 Webex Calling Routing, Trunks & Dial Plans 9.3 Webex Calling Call Routing Process & Translation Patterns 9.4 Webex Calling Toll Fraud Prevention, Call Permissions & Operating Modes 9.5 PSTN Connectivity: Cloud-Connected PSTN (CC-PSTN) & Cisco Calling Plans 9.6 Webex Calling Local Gateway (LGW) Architecture & Configuration
10 Chapter 10: Webex Hybrid Services & Cloud Connected UC
10.1 Cloud-Connected UC (CCUC) Architecture & Telemetry 10.2 Webex Hybrid Calendar & Hybrid Directory Services 10.3 Webex Video Mesh & Hybrid Data Security
11 Chapter 11: Media Quality, QoS Engineering & Troubleshooting
11.1 Real-Time Media Characteristics & Impairments 11.2 QoS Classification, Marking & Trust Boundaries 11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE 11.4 Troubleshooting Media Quality & Call Failures
11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE
Key Takeaways Explain This Topic AI
The Modular QoS CLI (MQC) standardizes QoS configuration into a discrete three-step model: define traffic classes ( class-map ), configure policies and queuing behaviors ( policy-map ), and apply the policy to an interface ( service-policy ).
Low Latency Queuing (LLQ) integrates a strict Priority Queue (PQ) for delay-sensitive voice media with Class-Based Weighted Fair Queuing (CBWFQ) for video, signaling, and data classes.
The strict priority queue is governed by an embedded traffic policer: during interface congestion, voice traffic exceeding the configured priority bandwidth ceiling is dropped to protect non-priority CBWFQ queues from starvation.
Class-Based Weighted Fair Queuing allocates bandwidth using either bandwidth <kbps> or bandwidth remaining percent <pct> , providing guaranteed minimum bandwidth to video and signaling without starvation.
Weighted Random Early Detection (WRED) provides congestion avoidance by dropping TCP packets probabilistically before buffers fill; WRED must be applied to AF classes ( random-detect dscp-based ) and must never be configured on the Voice priority queue.
Last updated: October 2026
11.3 Low Latency Queuing (LLQ) Configuration on Cisco IOS XE
Queuing is the congestion management mechanism deployed on router interfaces to determine the order in which packets depart when arrival rates exceed link transmission capacity. Without intelligent queuing, interfaces operate on a First-In, First-Out (FIFO) basis, where delay-sensitive voice packets become trapped behind large bulk data frames. On Cisco IOS XE routers, Low Latency Queuing (LLQ) represents the premier congestion management architecture for real-time collaboration networks. This section covers the Modular QoS CLI (MQC) framework, LLQ scheduling mechanics, policing dynamics, congestion avoidance, and complete configuration templates.
1. The Modular QoS CLI (MQC) Framework
Cisco IOS XE structures QoS configuration through the Modular QoS Command-Line Interface (MQC) . MQC decouples packet classification from policy actions, establishing a standardized three-step workflow: +-------------------------------------------------------------------------+
- | THE THREE-STEP MQC CONFIGURATION MODEL |
- | |
- | STEP 1: CLASSIFICATION STEP 2: POLICY ACTION |
- | +--------------------------+ +-------------------------------+ |
- | | class-map [all | any] | ----> | policy-map <name> | |
- | | match ip dscp ... | | class <class-name> | |
- | | match protocol ... | | priority / bandwidth | |
- | +--------------------------+ +---------------+---------------+ |
- | | |
- | v |
- | STEP 3: INTERFACE ATTACHMENT +-------------------------------+ |
- | | interface GigabitEthernet0/0/1| |
- | | service-policy output <name> | |
- | +-------------------------------+ |
- +-------------------------------------------------------------------------+
- Step 1: Traffic Classification ( class-map )
The class-map construct identifies and groups traffic based on specific packet headers or inspection criteria:
Matching Operators :
class-map match-all <name> : Enforces a logical AND ; a packet must satisfy every configured match statement to belong to the class.
class-map match-any <name> : Enforces a logical OR ; a packet matching any single match statement is admitted to the class.
Classification Criteria :
match ip dscp <value> : Inspects Layer 3 DSCP code points (e.g., ef , af41 , cs3 ).
match protocol <protocol> : Utilizes Network-Based Application Recognition (NBAR2) deep packet inspection to classify traffic regardless of Layer 4 ports (e.g., match protocol webex-media ).
match access-group name <acl> : Evaluates standard or extended Access Control Lists.
Step 2: Policy Map Creation ( policy-map )
The policy-map associates QoS actions with previously defined classes. Actions include bandwidth reservations, strict priority queuing, traffic shaping, policing, and remarking.
Step 3: Policy Attachment ( service-policy )
The service-policy command applies the policy-map to an interface, subinterface, or tunnel interface in either the input or output direction. Queuing policies (LLQ/CBWFQ) can only be applied in the output (egress) direction because a router cannot queue packets it has not yet received.
2. Low Latency Queuing (LLQ) Scheduling Mechanics
Queuing algorithms have evolved through several generations of router hardware:
First-In, First-Out (FIFO) : Packets are transmitted strictly in order of arrival. Subject to massive latency and jitter.
Priority Queuing (PQ) : Multiple strict priority queues. Lower queues receive zero service until higher queues empty, resulting in severe starvation of standard data.
Custom Queuing (CQ) : Round-robin scheduling with byte-count thresholds. Prevents starvation, but cannot provide low latency guarantees.
Weighted Fair Queuing (WFQ) : Dynamically divides bandwidth among conversations based on IP Precedence. Cannot guarantee fixed bandwidth ceilings for specific enterprise classes.
Class-Based Weighted Fair Queuing (CBWFQ) : Allocates guaranteed minimum bandwidth to user-defined classes using a modified deficit round-robin scheduler. Excellent for data and video, but introduces excessive jitter for voice.
Low Latency Queuing (LLQ) : Combines the strict delay bounds of a Strict Priority Queue (PQ) with the starvation protection of CBWFQ . +-------------------------------------------------------------------------+
- | LOW LATENCY QUEUING (LLQ) SCHEDULER |
- | |
- | INGRESS PACKETS |
- | | |
- | +---> [Classifier: DSCP / MQC] |
- | | |
- | +---> [Priority Queue: Voice (EF)] |
- | | | (Serviced FIRST before any other queue) |
- | | v |
- | +---> [CBWFQ Queue 1: Video (AF41)] |
- | | | |
- | +---> [CBWFQ Queue 2: Signaling (CS3)] |
- | | | (Weighted Round-Robin Scheduler) |
- | +---> [CBWFQ Queue 3: Critical Data] |
- | | | |
- | +---> [Class-Default: Best Effort] |
- | | |
- | v |
- | +----------------------+ |
- | | HARDWARE TX-RING | |
- | +----------+-----------+ |
- | | |
- | v |
- | [PHYSICAL TRANSMISSION WIRE] |
- +-------------------------------------------------------------------------+
- The Scheduler Operation
The LLQ scheduler inspects the Strict Priority Queue first. Whenever a packet resides in the priority queue, the scheduler dequeues it immediately and sends it to the interface hardware transmit ring (Tx-Ring). Only when the priority queue is completely empty does the scheduler service the remaining CBWFQ queues (Video, Signaling, Critical Data, and Class-Default) using weighted round-robin scheduling.
3. Priority Queue Configuration & Policer Dynamics
While strict priority queuing delivers the near-zero delay and jitter required by voice media, it reintroduces the fundamental danger of Priority Queuing: queue starvation . If an unpoliced voice queue were flooded with excess traffic, it would monopolize 100% of interface bandwidth, starving critical signaling, business applications, and routing protocols.
The Built-In LLQ Policer
To eliminate the risk of starvation, Cisco LLQ incorporates an implicit traffic policer directly within the priority command:
Syntax :
priority <bandwidth-kbps> : Allocates a dedicated bandwidth ceiling in kbps.
priority percent <percentage> : Allocates a ceiling as a percentage of the total interface or parent shaping bandwidth.
Non-Congested State : If the physical interface is not congested, voice packets arriving in excess of the configured priority ceiling are transmitted without penalty.
Congested State : The moment the interface experiences congestion (the software queue engages because the hardware Tx-Ring is full), the built-in policer strictly enforces the configured priority bandwidth limit . Any voice traffic exceeding the allocated kbps or percentage is immediately discarded!
Caution
Priority Queue Sizing Rule : Under-provisioning the priority bandwidth allocation on a WAN interface results in silent voice packet drops during congestion, producing catastrophic audio distortion. Sizing calculations must account for the peak concurrent call volume multiplied by the full Layer 2 bandwidth of the voice codec (e.g., 87.2 kbps per G.711 call on Ethernet).
Cisco IOS XE Dual Priority Queuing
Modern Cisco IOS XE releases support Dual LLQ , enabling two distinct strict priority levels:
priority level 1 : Highest strict priority. Serviced ahead of all other queues. Universally reserved for Voice Media (EF).
priority level 2 : Second strict priority. Serviced after Priority Level 1 is empty, but before any CBWFQ queue. Reserved for Interactive Video (AF41).
- 4. CBWFQ & Congestion Avoidance (WRED vs. Tail Drop)
- CBWFQ Bandwidth Allocation
Non-priority classes (Video, Signaling, Transactional Data) utilize Class-Based Weighted Fair Queuing:
bandwidth <kbps> : Guarantees a minimum rate in kilobits per second during congestion.
bandwidth remaining percent <percentage> : Allocates a percentage of the unreserved bandwidth remaining after priority and absolute bandwidth guarantees have been satisfied. This is the modern Cisco-recommended standard for enterprise WAN edge policies.
Congestion Avoidance: WRED vs. Tail Drop
When a router queue fills to 100% capacity, incoming packets encounter tail drop . In networks carrying thousands of TCP flows, tail drop triggers TCP Global Synchronization :
Multiple TCP connections drop packets simultaneously.
All TCP endpoints simultaneously back off their transmission windows (multiplicative decrease).
Network utilization collapses, causing the queue to empty.
All endpoints simultaneously ramp up transmission speeds (slow start), causing the queue to overflow again, repeating the oscillatory saw-tooth cycle. +-------------------------------------------------------------------------+
- | DSCP-BASED WRED DISCARD PROFILES |
- | |
- | DISCARD PROBABILITY |
- | 100% | |
- | | /| AF43 (Drop 3 - Discard First) |
- | | / | |
- | | /| / | AF42 (Drop 2 - Medium Drop) |
- | | / | / | |
- | | /| / | / | AF41 (Drop 1 - Discard Last) |
- | | / | / | / | |
- | 0% +----------+--+---+----+--+-----+------------------------ |
- | Min1 Min2 Min3 Max Threshold |
- | AVERAGE QUEUE DEPTH |
- +-------------------------------------------------------------------------+
- DSCP-Based Weighted Random Early Detection (WRED)
Weighted Random Early Detection (WRED) prevents TCP global synchronization by randomly discarding packets before the buffer fills. By dropping individual packets from random TCP sessions, WRED causes distinct TCP flows to back off at staggered intervals, maintaining smooth, continuous 100% link utilization.
DSCP-Based WRED ( random-detect dscp-based ) : Differentiates discard thresholds based on the packet's Assured Forwarding drop precedence. Packets marked AF43 (High Drop) are dropped at a lower queue threshold than AF42 (Medium Drop) , while AF41 (Low Drop) packets are protected until queue depth nears capacity.
Crucial Rule : WRED must NEVER be applied to the Voice Priority Queue . Voice uses UDP, which does not have TCP congestion window mechanics. Dropping voice packets degrades MOS quality without causing the sender to throttle back. Priority queues rely strictly on policing or tail drop.
5. Enterprise WAN Edge MQC Configuration Template
The following complete, production-grade configuration demonstrates a hierarchical MQC policy applied to a Gigabit WAN edge interface on a Cisco Catalyst 8300 / ISR 4000 running Cisco IOS XE. ! =========================================================================
- ! 1. CLASSIFICATION: CLASS-MAPS FOR ENTERPRISE COLLABORATION TRAFFIC
- ! =========================================================================
- class-map match-any CM-VOICE-MEDIA
- match ip dscp ef
- class-map match-any CM-INTERACTIVE-VIDEO
- match ip dscp af41
- match ip dscp af42
- class-map match-any CM-CALL-SIGNALING
- match ip dscp cs3
- match ip dscp af31
- class-map match-any CM-CRITICAL-DATA
- match ip dscp af21
- match ip dscp af22
- ! =========================================================================
- ! 2. QUEUING POLICY: CHILD POLICY-MAP (LLQ + CBWFQ + WRED)
- ! =========================================================================
- policy-map PM-WAN-QUEUING-CHILD
- class CM-VOICE-MEDIA
- ! Strict Priority Queue: 1,000 kbps reserved; policed during congestion
- priority 1000
- class CM-INTERACTIVE-VIDEO
- ! Guaranteed bandwidth for 2-way Webex/SIP Video
- bandwidth remaining percent 30
- ! DSCP-based WRED to manage video burst congestion
- random-detect dscp-based
- class CM-CALL-SIGNALING
- ! Guaranteed bandwidth to prevent SIP keepalive/INVITE drops
- bandwidth remaining percent 5
- class CM-CRITICAL-DATA
- ! Transactional ERP / Enterprise database traffic
- bandwidth remaining percent 35
- random-detect dscp-based
- class class-default
- ! Remaining bandwidth allocated to general best-effort data
- bandwidth remaining percent 30
- fair-queue
- ! =========================================================================
- ! 3. TRAFFIC SHAPING: PARENT POLICY-MAP (HIERARCHICAL MQC / H-QoS)
- ! =========================================================================
- policy-map PM-WAN-EDGE-PARENT
- class class-default
- ! Shape to committed sub-line rate (e.g., 100 Mbps on a 1 Gbps physical handoff)
- shape average 100000000
- service-policy PM-WAN-QUEUING-CHILD
- ! =========================================================================
- ! 4. INTERFACE ATTACHMENT
- ! =========================================================================
- interface GigabitEthernet0/0/1
- description Primary WAN Uplink to Carrier MPLS Fabric
- ip address 198.51.100.2 255.255.255.252
- service-policy output PM-WAN-EDGE-PARENT
- Key Verification Commands
show policy-map interface <interface-name> : Displays real-time queuing statistics, packet counts, offered rates, and tail drop / policer drop counters for each configured class.
show class-map : Validates match criteria and syntax for configured class-maps.
show policy-map : Displays configured policy-map parameters and queuing allocations.