Study guide
1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation
Cisco ENCOR 350-401 CCNP Enterprise Core
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
0.1 Cisco 350-401 ENCOR Exam Logistics, Blueprint Structure, and Certification Paths 0.2 Preparation Strategy, Lab Environment Setup, and Practical Test Pacing
2 Enterprise Campus Architecture and High Availability
1.1 Enterprise Network Design: Two-Tier, Three-Tier, Fabric, and Cloud Architectures 1.2 High Availability Architecture: Device Redundancy, FHRPs, and Stateful Switchover (SSO) 1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation
3 Cisco Software-Defined Architecture: SD-WAN and SD-Access
2.1 Cisco Catalyst SD-WAN: Control, Management, and Data Planes 2.2 Cisco SD-Access Architecture: Control Plane, Data Plane, and Fabric Node Roles 2.3 SD-Access Campus Interoperability: Integrating Traditional Networks with Fabric
4 Device and Network Virtualization Technologies
3.1 Device Virtualization: Type 1/2 Hypervisors, Virtual Machines, and Virtual Switching 3.2 Data Path Virtualization: VRF-Lite, GRE Tunneling, and IPsec VPN Fundamentals 3.3 Network Virtualization Overlays: LISP and VXLAN Encapsulation Mechanics
5 Layer 2 Infrastructure: Trunking, EtherChannel, and Spanning Tree
4.1 802.1Q Trunking, Native VLAN, and Dynamic Trunking Protocol Troubleshooting 4.2 EtherChannel Bundling: Static, LACP, and PAgP Implementation and Verification 4.3 Spanning Tree Architecture: RSTP, MST, and STP Protection Mechanisms
6 Layer 3 Routing: OSPF Multi-Area and Protocol Comparison
5.1 Enterprise Routing Principles: Distance Vector vs. Link-State, EIGRP, and OSPF 5.2 OSPFv2 and OSPFv3 Multi-Area Architecture: LSAs, Area Types, and Summarization 5.3 Policy-Based Routing (PBR) Architecture, Configuration, and Route-Maps
7 Exterior Routing: BGP Peering and Path Selection
6.1 External BGP (eBGP) Peering, States, Neighbor Adjacencies, and Timers 6.2 BGP Path Attributes and the Step-by-Step Best Path Selection Algorithm
8 IP Services and First-Hop Redundancy
7.1 Time Synchronization: Network Time Protocol (NTP) and Precision Time Protocol (PTP) 7.2 Network Address Translation: Static NAT, Dynamic NAT, and PAT/Overload 7.3 First Hop Redundancy Protocols: HSRP and VRRP Implementation and Failover
9 IP Multicast Architecture and Protocols
8.1 Multicast Addressing, IGMPv2/v3 Host Membership, and the RPF Check 8.2 Protocol Independent Multicast Sparse Mode (PIM-SM) and Rendezvous Point Discovery 8.3 Anycast RP with MSDP, Source-Specific Multicast (SSM), and Bidirectional PIM
10 Network Diagnostics, Monitoring, and Telemetry
9.1 Network Diagnostic Tools: Conditional Debugging, Traceroute, SNMPv3, and Syslog Logging 9.2 Flexible NetFlow (FNF) Architecture: Flow Records, Exporters, and Monitors 9.3 Switched Port Analyzer: Local SPAN, Remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN)
11 Performance Monitoring and Model-Driven Assurance
10.1 IP Service Level Agreements (IP SLA) Probes, Responder, and Route Tracking 10.2 Cisco Catalyst Center: Assurance Dashboards, AI Analytics, and Machine Reasoning Workflows 10.3 Model-Driven Telemetry and Programmable Interfaces: NETCONF and RESTCONF Verification
12 Device Access Control and AAA Architecture
11.1 Device Line Protection: Console, Aux, VTY, Local Authentication, and Privilege Levels 11.2 AAA Architecture: Comparing RADIUS vs. TACACS+ and Method List Configuration
13 Infrastructure Security: ACLs, CoPP, and API Security
12.1 IPv4 and IPv6 Access Control Lists (ACLs): Standard, Extended, and Named Rules 12.2 Control Plane Policing (CoPP): Protecting the Route Processor with MQC 12.3 REST API Security: Token Authentication, TLS Transport, and Rate Limiting
14 Enterprise Network Security Design: ISE, TrustSec, and MACsec
13.1 Endpoint Security Architecture: 802.1X, Cisco ISE Posture, and Profiling 13.2 Next-Generation Firewalls (FTD) and Enterprise Threat Defense Design 13.3 Cisco TrustSec (Security Group Tags) and MACsec (802.1AE) Layer 2 Encryption
15 Network Automation Fundamentals: Python, JSON, and YANG
14.1 Python Fundamentals for Network Engineers: Data Types, Control Flow, and Libraries 14.2 JSON Data Encoding: Syntax, Formatting Rules, and Python Serialization 14.3 YANG Data Modeling: Modules, Tree Structures, and Data Representation
16 Controller REST APIs and RESTCONF Implementation
15.1 Cisco Catalyst Center Intent APIs and Authentication Workflows 15.2 Cisco Catalyst SD-WAN Manager (vManage) REST APIs and Device Interaction 15.3 RESTCONF Protocol Operations: HTTP Verbs, Datastores, and Response Codes
17 Event-Driven Automation and Infrastructure Orchestration
16.1 Cisco Embedded Event Manager (EEM) Applet Architecture and Event Detectors 16.2 Configuration Management: Comparing Ansible, Puppet, Chef, and SaltStack 16.3 Infrastructure as Code (IaC) Principles with Terraform in Enterprise Networks
1.3 Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation
Key Takeaways Explain This Topic AI
The Differentiated Services (DiffServ) model provides scalable, per-hop Quality of Service by classifying and marking packets at ingress and applying behavioral per-hop queuing without maintaining per-flow signaling states.
Layer 3 DSCP repurposes the IPv4 Type of Service (ToS) byte into 6 bits of classification (64 codepoints), distinguishing Class Selector (CS), Assured Forwarding (AF), and Expedited Forwarding (EF = 46).
The trust boundary demarcates where packet markings are validated or re-marked to best effort, typically enforced at the access switch or negotiated through CDP/LLDP with enterprise IP phones.
Policing enforces rigid rate boundaries by dropping or re-marking excess bursts without buffering, while shaping queues excess packets into memory to smooth traffic transmission at outbound interfaces.
Modular QoS CLI (MQC) configures QoS in three modular components: class-map (identification), policy-map (action/bandwidth allocation), and service-policy (interface application).
Last updated: October 2026
Quality of Service (QoS) Architecture, Classification, Queuing, and Configuration Interpretation
Quality of Service (QoS) provides predictable, deterministic network behavior for latency-sensitive applications—such as real-time voice, interactive video, and business-critical transactions—competing against bulk data across constrained enterprise campus links.
Fundamental QoS Models
Modern enterprise networks implement one of three standard QoS models:
Best Effort: The default operational model. Packets receive First-In, First-Out (FIFO) scheduling without classification, resource reservation, or preferential treatment. When links become congested, packets are dropped indiscriminately.
Integrated Services (IntServ / RSVP - RFC 1633 / RFC 2205): A "hard QoS" model where endpoints signal their bandwidth and latency requirements end-to-end using the Resource Reservation Protocol (RSVP). Every intermediate router along the path must maintain per-flow state tables and reserve explicit bandwidth before traffic flows. While IntServ guarantees QoS, it fails to scale in large enterprise networks because tracking thousands of individual microflows exhausts router memory and CPU resources.
Differentiated Services (DiffServ - RFC 2474): A "soft QoS" model that replaces per-flow state with scalable class-based aggregation. Ingress edge devices classify and mark packets into aggregated traffic classes. Intermediate nodes inspect these markings and apply stateless Per-Hop Behaviors (PHB) —such as specific queuing, scheduling, and drop mechanisms. DiffServ scales seamlessly and serves as the foundation for modern enterprise network QoS.
Classification and Marking: Layer 2 CoS vs. Layer 3 DSCP
Classification identifies traffic flows; marking alters a designated header field to categorize packets for subsequent queuing treatment.
Layer 2 Class of Service (CoS)
In 802.1Q tagged Ethernet frames, the 16-bit Tag Control Information (TCI) field includes the 3-bit Priority Code Point (PCP) , which carries the Class of Service (CoS) value (0–7). Because CoS resides within the Layer 2 802.1Q header, it is lost whenever a frame crosses a Layer 3 routed boundary or traverses an untagged access port.
Layer 3 Differentiated Services Code Point (DSCP)
RFC 2474 redefined the legacy 8-bit IPv4 Type of Service (ToS) byte and IPv6 Traffic Class byte:
DSCP Field (Bits 0–5): The first 6 bits define the Differentiated Services Code Point (DSCP), providing 64 distinct codepoints (0–63) .
ECN Field (Bits 6–7): The last 2 bits are allocated for Explicit Congestion Notification (RFC 3168). 0 1 2 3 4 5 6 7
- +---+---+---+---+---+---+---+---+
- | DSCP (6 bits) | ECN |
- +---+---+---+---+---+---+---+---+
- DiffServ Architectural Classes
Default Forwarding (DF): DSCP 0 ( 000000 ), representing best-effort traffic.
Class Selector (CS): CS0 through CS7 provide backward compatibility with the legacy 3-bit IP Precedence (IPP) field. The decimal value equals IPP multiplied by 8:
CS1 = 8 ( 001000 ), CS2 = 16 ( 010000 ), CS3 = 24 ( 011000 ), CS4 = 32 ( 100000 ), CS5 = 40 ( 101000 ), CS6 = 48 ( 110000 ), CS7 = 56 ( 111000 ).
RFC 4594 recommends CS6 for network control traffic such as routing protocols; CS7 is reserved for future use.
Assured Forwarding (AF - RFC 2597): Defines four distinct classes (1 to 4) with three drop precedence levels per class (1 = Low, 2 = Medium, 3 = High). Formatted as AFxy where x is class (1–4) and y is drop precedence (1–3).
Decimal formula: DSCP = 8x + 2y
Example: AF31 has a decimal value of 8(3) + 2(1) = 26. AF32 has a value of 8(3) + 2(2) = 28. AF33 has a value of 8(3) + 2(3) = 30. Under congestion, AF33 is dropped before AF32, which is dropped before AF31.
Expedited Forwarding (EF - RFC 3246): DSCP 46 ( 101110 ). Designed for low-loss, low-latency, low-jitter real-time traffic, specifically VoIP media (Real-time Transport Protocol - RTP).
Standard DSCP Values and Enterprise Workloads
- Classification Name Binary Code Decimal Value Drop Precedence / Class Recommended Enterprise Workload
- CS0 / DF 000000 0 None (Best Effort) General web browsing, file downloads
- CS1 (Scavenger) 001000 8 Backward Compatible IPP 1 Peer-to-peer, unauthorized streaming
AF11 / AF12 / AF13 001010 / 001100 / 001110 10 / 12 / 14 Low / Med / High Drop (Class 1) Bulk data transfers, backup operations
AF21 / AF22 / AF23 010010 / 010100 / 010110 18 / 20 / 22 Low / Med / High Drop (Class 2) Transactional data, ERP, database queries
CS3 011000 24 Backward Compatible IPP 3 Call signaling (SIP, H.323) per RFC 4594
AF31 / AF32 / AF33 011010 / 011100 / 011110 26 / 28 / 30 Low / Med / High Drop (Class 3) Multimedia streaming per RFC 4594; older Cisco baselines used it for mission-critical data
AF41 / AF42 / AF43 100010 / 100100 / 100110 34 / 36 / 38 Low / Med / High Drop (Class 4) Interactive video, videoconferencing
- EF 101110 46 Strict Priority VoIP audio payload (RTP streams)
- CS6 110000 48 Backward Compatible IPP 6 Network control (OSPF, BGP, EIGRP)
- CS7 111000 56 Backward Compatible IPP 7 Reserved for future use (RFC 4594)
- Trust Boundaries
A trust boundary establishes the physical perimeter where incoming QoS markings are accepted. Markings received from outside the trust boundary are untrusted and reset to best effort (DSCP 0).
Untrusted Endpoints: Workstations, laptops, and printers often generate arbitrary markings. If left untrusted, rogue applications could mark peer-to-peer downloads as Expedited Forwarding (DSCP 46).
IP Phone Demarcation: In enterprise deployments, an IP phone typically connects to a switch access port while a workstation daisy-chains into the PC port on the back of the phone. Using Cisco Discovery Protocol (CDP) or LLDP-MED, the switch establishes a conditional trust boundary:
Voice media from the phone (DSCP 46 / CoS 5) and signaling (DSCP 24 / CoS 3) are trusted.
Frames arriving from the downstream workstation are untrusted; their CoS and DSCP markings are rewritten to 0 at ingress.
Traffic Conditioning: Policing vs. Shaping
When traffic exceeds its contracted Committed Information Rate (CIR), traffic conditioning engines intervene: Traffic Burst > CIR
- |
- +---> [POLICING] ---> Drop excess or Re-mark to lower DSCP (No Buffering, Ingress/Egress)
- |
- +---> [SHAPING] ---> Buffer excess in memory, smooth output rate (Buffering delay, Egress only)
Traffic Policing: Evaluates packets against a token bucket algorithm. Packets exceeding the CIR are immediately dropped or re-marked to a higher drop precedence (e.g., Markdown from AF21 to AF22). Policing introduces no delay or jitter because it does not buffer packets. However, dropping packets triggers TCP sliding window collapse. Policing is supported on both ingress and egress interfaces.
Traffic Shaping: Enforces rate limits by holding excess packets in a software buffer queue, transmitting them at a steady, metered pace. Shaping smooths bursty transmission and prevents packet loss at the cost of introduced buffering delay and jitter. Because packets cannot be delayed before they arrive, shaping is supported only on egress (outbound) interfaces.
Congestion Management and Queuing
When an egress interface experiences congestion, hardware scheduling algorithms determine which packets are transmitted first:
Priority Queuing (PQ): Strict priority scheduling. Packets in the priority queue are always serviced before any lower queue. Without strict policing, high-volume priority traffic will completely starve non-priority queues.
Class-Based Weighted Fair Queuing (CBWFQ): Allocates guaranteed minimum bandwidth percentages to distinct traffic classes. During congestion, each class receives its configured bandwidth slice; remaining bandwidth is shared proportionally.
Low Latency Queuing (LLQ): Combines CBWFQ with a strict Priority Queue (PQ) for delay-sensitive traffic (voice and interactive video). Crucially, the PQ in LLQ is bounded by a strict policer. If voice traffic exceeds its provisioned rate, excess voice packets are dropped rather than allowing the priority queue to starve the CBWFQ data queues.
Congestion Avoidance: Tail Drop vs. WRED
When egress queues fill completely, the switch performs Tail Drop , discarding all subsequent incoming packets regardless of priority. In TCP-heavy networks, tail drop causes TCP Global Synchronization : dozens of concurrent TCP sessions experience simultaneous packet loss, drop their congestion windows simultaneously, and retransmit at the same time, producing severe throughput oscillations.
Weighted Random Early Detection (WRED) eliminates global synchronization:
WRED monitors average queue depth. When queue occupancy crosses a minimum threshold, WRED begins probabilistically dropping packets at random before the buffer fills.
By dropping individual packets from separate flows, TCP endpoints back off at staggered times.
"Weighted" WRED uses IP Precedence or DSCP drop precedence values: packets marked with high drop precedence (such as AF23) begin dropping at lower queue thresholds than packets marked with low drop precedence (such as AF21).
Cisco MQC Configuration and Interpretation
The Modular QoS CLI (MQC) organizes QoS implementation into three decoupled steps: 1. class-map --> Classifies traffic using match criteria
- 2. policy-map --> Defines actions (priority, bandwidth, shape, police, set)
- 3. service-policy--> Applies policy-map to interface (input or output)
- MQC Configuration Example ! Step 1: Classification
- class-map match-all CM-VOICE-RTP
- match dscp ef
- class-map match-all CM-MISSION-CRITICAL
- match dscp af31 af32
- ! Step 2: Policy Mapping
- policy-map PM-CAMPUS-EGRESS
- class CM-VOICE-RTP
- priority level 1
- police cir 512000 conform-action transmit exceed-action drop
- class CM-MISSION-CRITICAL
- bandwidth percent 35
- random-detect dscp-based
- class class-default
- bandwidth percent 25
- fair-queue
- ! Step 3: Interface Application
- interface GigabitEthernet1/0/1
- service-policy output PM-CAMPUS-EGRESS
- Interpreting show policy-map interface
The show policy-map interface command provides critical operational verification: Switch# show policy-map interface GigabitEthernet1/0/1
GigabitEthernet1/0/1
Service-policy output: PM-CAMPUS-EGRESS
- Class-map: CM-VOICE-RTP (match-all)
- 128492 packets, 20558720 bytes
- 5 minute offered rate 124000 bps, drop rate 0000 bps
- Match: dscp ef (46)
- Priority: Strict Priority,
police:
cir 512000 bps, bc 16000 bytes
conformed 128492 pkts, 20558720 bytes; actions:
transmit
exceeded 0 pkts, 0 bytes; actions:
- drop
- conformed 124000 bps, exceeded 0000 bps
- Class-map: CM-MISSION-CRITICAL (match-all)
- 892100 packets, 1141888000 bytes
- 5 minute offered rate 2850000 bps, drop rate 0000 bps
- Match: dscp af31 (26) af32 (28)
- Queueing
- queue limit 64 packets
- (queue depth/total drops/no-buffer drops) 0/0/0
- bandwidth 35% (350000 kbps)
dscp-based WRED:
- dscp 26: min-threshold 40, max-threshold 60, mark-probability 1/10 (0 drops)
- dscp 28: min-threshold 30, max-threshold 50, mark-probability 1/10 (0 drops)
- Class-map: class-default (match-any)
- 4521098 packets, 5786905440 bytes
- 5 minute offered rate 14200000 bps, drop rate 1420 pkts
- bandwidth 25% (250000 kbps)
Offered Rate vs. Drop Rate: Confirms incoming volume and drops. drop rate 0000 bps in the voice class indicates no voice packets are being discarded.
Priority Policer Verification: The conformed counter records passed voice packets, while exceeded 0 pkts verifies that the 512 kbps strict priority policer has not discarded excess voice traffic.
Queue Depth & WRED Drops: In CM-MISSION-CRITICAL , WRED monitors thresholds (e.g., dropping DSCP 28 at a minimum threshold of 30 packets versus DSCP 26 at 40 packets), successfully avoiding tail drops.
MQC Command Structure Breakdown
MQC Hierarchy Primary Commands Operational Purpose
class-map match dscp , match cos , match access-group , match protocol Identifies and isolates traffic based on Layer 2–4 headers
policy-map priority , bandwidth percent , police , shape average , set dscp Defines queue scheduling, policing, shaping, and marking actions
service-policy service-policy input <name> , service-policy output <name> Binds the configured policy to an interface in a specific direction
Verification show policy-map interface <id> , show class-map Displays real-time matching statistics, queue depth, and drop counts