CoS Queue Marking: Mapping 802.1p to Egress Queues for Enterprise Networks

In the high-stakes world of enterprise networking, "Best Effort" is rarely good enough. When voice calls drop or video conferences lag, the culprit is often a lack of prioritization at the most fundamental level: the Data Link Layer (Layer 2). Class of Service (CoS) queue marking is the mechanism that ensures your most critical data—be it a CEO’s Zoom call or a high-frequency financial transaction—gets the "express lane" treatment through a switch.

This guide provides an in-depth, technical exploration of CoS marking, how it interacts with egress queues, and how to maintain QoS consistency across your network infrastructure.

Get a Free Network Performance Audit

Understanding CoS: The Foundation of Layer 2 QoS

Class of Service (CoS) refers to a 3-bit field within an Ethernet frame header, specifically defined by the IEEE 802.1p standard. Because it is only 3 bits long, it supports exactly eight possible values (0 through 7).

The 802.1Q Tag Anatomy

CoS does not exist in a standard "untagged" Ethernet frame. It is housed within the 802.1Q VLAN tag. When a frame is tagged for a specific VLAN, a 16-bit Tag Control Information (TCI) field is added. The first 3 bits of this TCI field are the Priority Code Point (PCP), commonly known as the CoS bits.

Standard CoS Value Mappings

While organizations can customize these, the industry generally follows these standard assignments:

The Mechanics of Marking: How Traffic is Tagged

Marking is the process of setting the CoS bits in the frame header. This happens at the Trust Boundary—the point in the network where the administrator decides to "trust" the incoming markings or overwrite them based on policy.

Ingress Classification

Before a frame can be marked, it must be classified. A switch looks at incoming traffic and identifies it based on:

• Port-based: All traffic on Port 1 is CoS 5.
• Protocol-based: All RTP (Voice) traffic is CoS 5.
• ACL-based: Traffic from a specific MAC or IP range is marked with a specific CoS.

The Trust Boundary

If a switch is connected to an IP phone, it might "trust" the CoS 5 marking coming from the phone. However, if a user’s PC sends traffic marked as CoS 7 (to try and cheat the system), the switch will typically "strip" or "remark" that traffic to CoS 0 at the trust boundary to prevent network abuse.

Also Read: Point-to-Point Links: PPP and Dedicated Networks

CoS to Queue Mapping: From Bits to Buffers

Marking the bits is only half the battle. The actual "Quality of Service" happens when those bits are used to place the frame into a specific hardware buffer, or Egress Queue.

The Hardware Queue Structure

Modern switches (like the Cisco Nexus 9000 series or Allied Telesis x-series) have multiple physical egress queues per port. A common configuration is 1P7Q, meaning 1 Strict Priority (SP) queue and 7 Weighted Round Robin (WRR) queues.

1. The Mapping Table: The switch refers to an internal table that dictates: "If a frame has CoS 5, place it in Queue 7."
2. Scheduling: The switch scheduler then decides which queue to service next.
   • Strict Priority (SP): The switch always empties Queue 7 before looking at any other queue. This is vital for Voice.
   • Weighted Round Robin (WRR): The switch gives a certain percentage of bandwidth to each queue (e.g., Queue 3 gets 20%, Queue 2 gets 10%).

Also Read: Physical Layer Signaling: How Data Moves in Networking

Cross-Layer Consistency: Mapping CoS to DSCP

CoS is a Layer 2 (Data Link) property. Once a frame passes through a router and the MAC header is stripped, the CoS value is lost. To maintain QoS across the entire network (Layer 3), we must map CoS to DSCP (Differentiated Services Code Point).

The Conversion Logic

DSCP is a 6-bit field in the IP header (Layer 3), allowing for 64 levels of priority.

• CoS to DSCP: When a frame enters a Layer 3 switch, the device copies the CoS value into the DSCP field. Usually, CoS 5 (Voice) is mapped to DSCP 46 (Expedited Forwarding - EF).
• DSCP to CoS: When a packet is encapsulated into a frame to be sent over a trunk, the switch maps the DSCP value back to a CoS value.

Formula for Simple Mapping:

A common (though basic) mapping uses the 3 most significant bits of the DSCP value to determine the CoS. For instance, DSCP 46 (binary 101110) has the first three bits 101, which equals decimal 5. Thus, DSCP 46 maps to CoS 5.

Conclusion

CoS queue marking is the bedrock of a responsive, high-performance network. By correctly classifying traffic at the edge, marking it with the appropriate 802.1p bits, and mapping those bits to strategic egress queues, administrators can guarantee the performance of mission-critical applications. As networks transition toward more complex cloud-hybrid models, maintaining the integrity of these markings across both Layer 2 and Layer 3 becomes the difference between a seamless user experience and a productivity-killing bottleneck.

Talk to a Network Architect

Key Takeaways on Class of Service (CoS) queue marking

• CoS is Layer 2: It lives in the 802.1Q VLAN tag and is limited to 8 priority levels (0-7).
• Marking vs. Queuing: Marking identifies the traffic; queuing provides the actual differentiated treatment.
• Strict Priority is for Voice: Always map CoS 5 to a Strict Priority queue to minimize jitter and latency.
• Trust Boundaries are Critical: Only trust markings from known, authorized devices (like IP phones) to prevent "Priority Creep."
• End-to-End QoS requires Mapping: You must map CoS to DSCP at the Layer 3 boundary to ensure priority is maintained across routers.

Frequently Asked Questions (FAQs) on Class of Service (CoS) queue marking

Q: What happens to CoS marking if the frame is untagged?

A: Standard Ethernet frames (untagged) do not have a CoS field. In this case, the switch will assign a "Internal Priority" or "Port Default CoS" to the frame for queuing purposes while it is inside the switch.

Q: Why use CoS if DSCP has more priority levels?

A: CoS is essential for Layer 2 switches that do not look deep enough into the packet to see the IP header. It provides a fast, hardware-based way to prioritize frames within a LAN or across trunk links.

Q: Can I use CoS 7 for my own applications?

A: It is highly discouraged. CoS 7 and 6 are generally reserved for network control traffic (like Spanning Tree or OSPF). If you saturate these queues with application data, you risk causing a network-wide collapse because control packets won't get through.

Q: Is CoS the same as 802.1p?

A: Yes. 802.1p is the specific sub-standard of 802.1Q that defines the 3-bit Priority Code Point (PCP) field used for Class of Service.