Study guide
2.1 QoS Components: Classification, Marking & Trust Boundaries
CCNP Enterprise ENCOR 350-401
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Enterprise Architecture & Hierarchical Design
1.1 Enterprise Network Design Models & Hierarchical Campus Architecture 1.2 On-Premises, Cloud & Hybrid Infrastructure Deployment Models 1.3 Hardware Switching Architecture & Packet Forwarding
2 Chapter 2: Enterprise Quality of Service (QoS)
2.1 QoS Components: Classification, Marking & Trust Boundaries 2.2 QoS Policy: Queuing, Shaping, Policing & Interpreting MQC Output
3 Chapter 3: Software-Defined WAN (Catalyst SD-WAN)
3.1 Cisco Catalyst SD-WAN Architecture & Orchestration 3.2 SD-WAN Policies, Traffic Engineering & Application-Aware Routing
4 Chapter 4: Software-Defined Access (Catalyst SD-Access)
4.1 Catalyst SD-Access Fabric Architecture & Plane Separation 4.2 Cisco TrustSec, Security Group Tags (SGT), SXP & MACsec
5 Chapter 5: Device & Data Path Virtualization
5.1 Server & Network Device Virtualization 5.2 VRF-Lite & Virtual Routing Multi-Tenancy 5.3 GRE & IPsec Tunnel Virtualization Mechanics
6 Chapter 6: Network Virtualization & Overlay Technologies
6.1 LISP Architecture & EID-to-RLOC Mapping Mechanics 6.2 VXLAN & EVPN Overlay Architecture
7 Chapter 7: Layer 2 Infrastructure & Switching
7.1 VLANs, 802.1Q Trunking & VTPv3 7.2 Spanning Tree Protocol Mechanics 7.3 Advanced STP Protection Mechanisms 7.4 EtherChannel Link Aggregation
8 Chapter 8: Layer 3 Routing Foundations & EIGRP
8.1 IP Routing Foundations & Administrative Distance 8.2 Enhanced Interior Gateway Routing Protocol (EIGRP)
9 Chapter 9: OSPFv2 & OSPFv3 Operations
9.1 OSPFv2 Architecture & Neighbor State Machine 9.2 OSPF LSA Types & Multi-Area Design 9.3 OSPFv3 for IPv4 and IPv6 Address Families
10 Chapter 10: Border Gateway Protocol (BGP)
10.1 BGP Architecture, Neighbor States & Peering 10.2 BGP Path Attributes & Best Path Selection Algorithm
11 Chapter 11: Policy-Based Routing & Route Redistribution
11.1 Policy-Based Routing (PBR) & Route Maps 11.2 Route Redistribution & Loop Prevention
12 Chapter 12: IP Services & High Availability
12.1 First Hop Redundancy Protocols (HSRP, VRRP & GLBP) 12.2 Network Time Protocol (NTPv4) & Precision Time Protocol (PTP) 12.3 Network Address Translation (NAT/PAT) & VRF-Aware NAT
13 Chapter 13: IP Multicast Operations
13.1 IP Multicast Addressing, Group Management (IGMPv1/v2/v3) & IGMP Snooping 13.2 Protocol Independent Multicast (PIM-SM, PIM-SSM & Bidir-PIM) 13.3 Rendezvous Point (RP) Distribution Mechanisms
14 Chapter 14: Network Assurance & Monitoring
14.1 Diagnostic Utilities, Conditional Debugging & Path MTU Discovery 14.2 Syslog Architecture, Logging Facilities & Severity Levels 14.3 SNMPv1/v2c/v3 Security & Flexible NetFlow (FNF) Architecture 14.4 Switched Port Analyzer (SPAN, RSPAN, ERSPAN) & IP SLA Object Tracking
15 Chapter 15: Catalyst Center Assurance & Controller Operations
15.1 Cisco Catalyst Center (DNA Center) Assurance & AI Network Analytics 15.2 Cisco Catalyst Center Device Onboarding & Software Image Management (SWIM)
16 Chapter 16: Enterprise Security & Access Control
16.1 Device Hardening, AAA Architecture & RADIUS/TACACS+ 16.2 Access Control Lists (ACLs) for Infrastructure Security 16.3 Control Plane Policing (CoPP) & Control Plane Protection (CPPr) 16.4 Layer 2 Infrastructure Security Features 16.5 IEEE 802.1X Port-Based Authentication & MAB
17 Chapter 17: Threat Defense & API Security
17.1 Enterprise VPN Technologies (DMVPN Phase 1/2/3 & FlexVPN) 17.2 Next-Generation Threat Defense & Secure Access Service Edge (SASE)
18 Chapter 18: Network Automation, Programmability & Data Modeling
18.1 Python Fundamentals for Network Engineers & Cisco Libraries 18.2 YANG Data Modeling Language (RFC 6020/7950) & Model Types 18.3 REST API Architecture, HTTP Verbs, Security & Cisco Controller APIs 18.4 Model-Driven Telemetry (MDT) & NETCONF/RESTCONF Operations
19 Chapter 19: Orchestration, EEM & AI Operations
19.1 Configuration Management & Infrastructure as Code (Ansible & Terraform) 19.2 Cisco Embedded Event Manager (EEM) & Intent-Based Networking
2.1 QoS Components: Classification, Marking & Trust Boundaries
Key Takeaways Explain This Topic AI
ENCOR v1.2 topic 1.4 is 'Interpret QoS configurations', so the exam tests reading a policy and predicting its effect rather than authoring one from a blank prompt.
DSCP is the high-order 6 bits of the IPv4 ToS / IPv6 Traffic Class byte, giving values 0-63; Layer 2 CoS (802.1p) and MPLS EXP carry only 3 bits, so any DSCP-to-CoS mapping is lossy and is normally taken from the three most significant DSCP bits.
Expedited Forwarding is DSCP 46 (binary 101110) and Assured Forwarding uses the AFxy pattern where x is the class 1-4 and y is the drop precedence 1-3, so AF31 evaluates to decimal 26 and AF41 to decimal 34.
The trust boundary should sit as close to the source as possible while still being under administrative control; an untrusted access port rewrites incoming DSCP to 0 by default, and conditional trust extends trust to a device only after CDP or LLDP-MED verifies it.
Classification identifies traffic and marking writes a value into the header, and the Modular QoS CLI separates them: class-map matches, policy-map sets or polices, and service-policy attaches the result to an interface in one direction.
Last updated: August 2026
2.1 QoS Components: Classification, Marking & Trust Boundaries
ENCOR v1.2 topic 1.4 is worded precisely: "Interpret QoS configurations." The verb matters. Cisco is not asking you to design a queuing strategy from scratch; it is asking you to look at a policy-map , a show policy-map interface counter block, or a switchport trust statement and correctly predict what happens to a packet. Everything in this section and the next exists to make that prediction reliable.
1. The Four Impairments QoS Actually Manages
QoS cannot create bandwidth. It can only decide who suffers first when a link is oversubscribed. There are exactly four impairments:
- Impairment Definition Voice target Interactive video target
- Bandwidth Bits per second available to a flow 21-320 kbps per call, codec-dependent 384 kbps - 20+ Mbps
- Delay (latency) One-way end-to-end transit time <= 150 ms one-way <= 150 ms
- Jitter Variation in inter-packet arrival delay <= 30 ms <= 30 ms
- Loss Percentage of packets discarded <= 1% <= 1%
These thresholds come from the long-standing Cisco design guidance derived from ITU-T G.114 and they show up constantly in scenario stems. When a question says "voice calls are choppy but throughput tests pass", it is describing jitter , not bandwidth. When it says "callers hear each other talk over one another", it is describing delay .
2. Three QoS Models
- Model Mechanism Scalability Where you see it
- Best effort No classification, FIFO everywhere Infinite Default on every interface
IntServ Per-flow reservation signalled with RSVP ; routers hold per-flow state Poor — state grows with flows Legacy voice admission control, some MPLS-TE
DiffServ Per-hop behaviour selected by a marking in the packet header; no per-flow state Excellent Essentially all modern enterprise QoS
DiffServ won because it pushes complexity to the network edge. The edge classifies and marks once; every downstream hop simply reads the mark and applies a Per-Hop Behaviour (PHB) . That single sentence is the conceptual core of topic 1.4.
- 3. Marking Fields: Where the Bits Live LAYER 2 (802.1Q tagged frame) LAYER 3 (IPv4 header, byte 2)
- +--------+--------+------------+ +---------------------------------+
- | TPID | PCP|DEI| VLAN ID | | DSCP (6 bits) | ECN (2 bits) |
- | 0x8100 | 3b | 1b | 12 bits | | 0 .. 63 | 0 .. 3 |
- +--------+--------+------------+ +---------------------------------+
- ^ ^
- | |
- CoS / 802.1p Formerly "IP Precedence" was the
- values 0-7 top 3 bits of this same byte
- Field Where Width Range Note
- CoS (802.1p PCP) 802.1Q tag 3 bits 0-7 Lost on an access port — untagged frames have no CoS
- MPLS EXP / TC MPLS shim header 3 bits 0-7 Provider-facing; same 3-bit constraint as CoS
- IP Precedence IPv4 ToS byte 3 bits 0-7 Legacy; equals the top 3 bits of DSCP
- DSCP IPv4 ToS / IPv6 Traffic Class 6 bits 0-63 The modern marking; survives Layer 3 boundaries
The single most common design error the exam probes: a marking placed only in CoS is destroyed the moment the frame crosses a routed hop or leaves a trunk, because CoS lives in the 802.1Q tag. Mark in DSCP if the value must survive end to end.
DSCP-to-CoS mapping is lossy
Mapping 6 bits into 3 bits cannot be reversible. The default Cisco behaviour takes the three most significant DSCP bits , which is equivalent to the old IP Precedence value. So DSCP 46 (EF, binary 101110 ) maps to CoS 5, and DSCP 34 (AF41, binary 100010 ) also maps to CoS 4 — and AF41, AF42, and AF43 all collapse onto the same CoS. Drop-precedence granularity does not survive the mapping.
4. DSCP Arithmetic and the Standard PHBs
You must be able to convert between the DSCP name and its decimal value without a lookup table.
Class Selector (CS) PHBs
CS values are backward compatible with IP Precedence: the top 3 bits carry the precedence and the low 3 bits are zero. Therefore CSn = n x 8 .
- Name Binary Decimal Typical use
- DF / CS0 000000 0 Best effort (default)
- CS1 001000 8 Scavenger / bulk
- CS2 010000 16 OAM / network management
- CS3 011000 24 Call signalling (SIP, SCCP)
- CS4 100000 32 Real-time interactive
- CS5 101000 40 Broadcast video
- CS6 110000 48 Network control (routing protocols)
- CS7 111000 56 Reserved — do not mark user traffic here
- Assured Forwarding (AF) PHBs
The AF name is AFxy where x is the AF class (1-4, meaning increasing queue priority) and y is the drop precedence (1 = lowest chance of being dropped, 3 = highest). The encoding is xxxyy0 , which gives the formula AFxy = 8x + 2y .
- Drop precedence 1 (low) Drop precedence 2 (medium) Drop precedence 3 (high)
- AF1x AF11 = 10 AF12 = 12 AF13 = 14
- AF2x AF21 = 18 AF22 = 20 AF23 = 22
- AF3x AF31 = 26 AF32 = 28 AF33 = 30
- AF4x AF41 = 34 AF42 = 36 AF43 = 38
Worked example: AF31 is class 3, drop precedence 1, so binary 011 01 0 = 26. Worked example: AF43 is class 4, drop precedence 3, so binary 100 11 0 = 38. The formula 8x + 2y reproduces both: 8(3) + 2(1) = 26 and 8(4) + 2(3) = 38.
Expedited Forwarding (EF)
EF = DSCP 46 = binary 101110 . EF is the single PHB defined for low-loss, low-latency, low-jitter service and is reserved for voice bearer traffic. It is deliberately not a CS value and not an AF value — memorise 46 outright. The higher-order bits 101 are why EF maps down to CoS 5.
5. RFC 4594 Marking Recommendations Used in Cisco Designs
- Traffic class Recommended DSCP Recommended queue treatment
- Network control (OSPF, BGP, EIGRP) CS6 (48) Small guaranteed bandwidth
- VoIP bearer (RTP) EF (46) Priority / LLQ
- Broadcast video CS5 (40) Priority or guaranteed
- Real-time interactive video CS4 (32) Priority or guaranteed
- Multimedia conferencing AF41/42/43 (34/36/38) Guaranteed bandwidth with WRED
- Multimedia streaming AF31/32/33 (26/28/30) Guaranteed bandwidth with WRED
- Call signalling CS3 (24) Small guaranteed bandwidth
- Transactional data AF21/22/23 (18/20/22) Guaranteed bandwidth
- Bulk data AF11/12/13 (10/12/14) Guaranteed bandwidth, aggressive WRED
- Scavenger CS1 (8) Minimal bandwidth, first to drop
- Best effort DF (0) Default queue
Exam-relevant asymmetry: signalling is CS3 while the media it sets up is EF. Losing signalling breaks call setup; losing bearer breaks audio. They are marked differently on purpose so they can be queued differently.
6. Trust Boundaries
A trust boundary is the point at which the network begins believing the QoS markings inside arriving packets. Everything outside the boundary is untrusted and gets re-marked or zeroed. +---------------------------------------------------------------------------+
- | WHERE TO PUT THE TRUST BOUNDARY (best -> acceptable) |
- +---------------------------------------------------------------------------+
- | BEST: IP phone -- trusted endpoint you administer |
- | GOOD: Access switchport -- classify/mark here with an ingress policy |
- | OK: Distribution layer -- further from the source, more traffic to |
- | classify, more CPU/TCAM per policy |
- | NEVER: Trust a PC, a printer, or anything a user can reconfigure |
- +---------------------------------------------------------------------------+
The governing principle is "trust as close to the source as possible, but never trust a device you do not administer." A user workstation can set DSCP 46 on a torrent client trivially; if the access port trusts DSCP, that torrent lands in the voice priority queue.
The three switchport trust states
Untrusted (default on Catalyst access ports) — incoming CoS and DSCP are overwritten with 0. Safe, but it also destroys legitimate endpoint markings.
Unconditional trust — trust dscp or trust cos accepts whatever arrives. Appropriate only on uplinks toward other switches you administer, or toward a server you control.
Conditional trust — the port trusts markings only after the attached device identifies itself over CDP or LLDP-MED. On IOS-XE the modern syntax is trust device cisco-phone (also cts , ip-camera , media-player ). If the phone is unplugged and a laptop is connected in its place, CDP/LLDP-MED verification fails and the port silently reverts to untrusted. This is the elegant answer to the "phone plus daisy-chained PC" topology, and it pairs naturally with the voice VLAN behaviour covered in Section 7.1.
7. Classification vs. Marking, and the MQC That Expresses Them
These two words are not synonyms and the exam separates them.
Classification answers "which bucket is this packet in?" It inspects something — an ACL, a DSCP value, an incoming interface, or an NBAR2 application ID — and assigns the packet to a class. Classification changes nothing in the packet.
Marking answers "what value should I write so downstream hops do not have to re-inspect?" It rewrites DSCP, CoS, or MPLS EXP.
The Modular QoS CLI (MQC) is the three-step construct that carries both. You have already met it in a security context in Section 16.3, where CoPP uses exactly the same grammar. ! STEP 1 - class-map: CLASSIFY. 'match-any' = logical OR, 'match-all' = logical AND.
- class-map match-any VOICE-BEARER
- match dscp ef
- match protocol rtp audio
!
- class-map match-any CALL-SIGNALLING
- match dscp cs3
- match protocol sip
!
- class-map match-all TRANSACTIONAL-ERP
- match access-group name ERP-SERVERS
- match protocol http
!
- ! STEP 2 - policy-map: decide the ACTION per class
- policy-map INGRESS-MARK
- class VOICE-BEARER
- set dscp ef
- class CALL-SIGNALLING
- set dscp cs3
- class TRANSACTIONAL-ERP
- set dscp af21
- class class-default
- set dscp default
!
- ! STEP 3 - service-policy: ATTACH, in exactly one direction
- interface GigabitEthernet1/0/12
- description Access port - user + phone
- trust device cisco-phone
- service-policy input INGRESS-MARK
- Reading that policy the way the exam wants
match-any in VOICE-BEARER means a packet qualifies if it carries DSCP EF or NBAR2 identifies it as audio RTP.
match-all in TRANSACTIONAL-ERP means the packet must match the ERP-SERVERS ACL and be identified as HTTP. Miss either condition and it falls through.
Classes are evaluated top to bottom, first match wins . Reordering the classes changes behaviour.
class-default catches everything unmatched. Here it is explicitly re-marked to DF, which is the correct hardening posture at a trust boundary: anything you did not deliberately recognise loses its markings.
service-policy input applies on ingress only. A separate service-policy output would be required to queue on egress — and queuing is an egress-only action, which is the subject of Section 2.2.