- play_arrow Overview
- play_arrow Understanding How Class of Service Manages Congestion and Defines Traffic Forwarding Behavior
- Understanding How Class of Service Manages Congestion and Controls Service Levels in the Network
- How CoS Applies to Packet Flow Across a Network
- The Junos OS CoS Components Used to Manage Congestion and Control Service Levels
- Mapping CoS Component Inputs to Outputs
- Default Junos OS CoS Settings
- Packet Flow Through the Junos OS CoS Process Overview
- Configuring Basic Packet Flow Through the Junos OS CoS Process
- Example: Classifying All Traffic from a Remote Device by Configuring Fixed Interface-Based Classification
- Interface Types That Do Not Support Junos OS CoS
-
- play_arrow Configuring Platform-Specific Functionality
- play_arrow Configuring Class of Service on ACX Series Universal Metro Routers
- CoS on ACX Series Routers Features Overview
- Understanding CoS CLI Configuration Statements on ACX Series Routers
- DSCP Propagation and Default CoS on ACX Series Routers
- Configuring CoS on ACX Series Routers
- Classifiers and Rewrite Rules at the Global, Physical, and Logical Interface Levels Overview
- Configuring Classifiers and Rewrite Rules at the Global and Physical Interface Levels
- Applying DSCP and DSCP IPv6 Classifiers on ACX Series Routers
- Schedulers Overview for ACX Series Routers
- Shared and Dedicated Buffer Memory Pools on ACX Series Routers
- CoS for PPP and MLPPP Interfaces on ACX Series Routers
- CoS for NAT Services on ACX Series Routers
- Hierarchical Class of Service in ACX Series Routers
- Storm Control on ACX Series Routers Overview
- play_arrow Configuring Class of Service on MX Series 5G Universal Routing Platforms
- Junos CoS on MX Series 5G Universal Routing Platforms Overview
- CoS Features and Limitations on MX Series Routers
- Configuring and Applying IEEE 802.1ad Classifiers
- Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- Example: Performing Output Scheduling and Shaping in Hierarchical CoS Queues for Traffic Routed to GRE Tunnels
- CoS-Based Interface Counters for IPv4 or IPv6 Aggregate on Layer 2
- Enabling a Timestamp for Ingress and Egress Queue Packets
- play_arrow Configuring Class of Service on PTX Series Packet Transport Routers
- CoS Features and Limitations on PTX Series Routers
- CoS Feature Differences Between PTX Series Packet Transport Routers and T Series Routers
- Understanding Scheduling on PTX Series Routers
- Virtual Output Queues on PTX Series Packet Transport Routers
- Example: Configuring Excess Rate for PTX Series Packet Transport Routers
- Identifying the Source of RED Dropped Packets on PTX Series Routers
- Configuring Queuing and Shaping on Logical Interfaces on PTX Series Routers
- Example: Configuring Queuing and Shaping on Logical Interfaces in PTX Series Packet Transport Routers
- Example: Configuring Strict-Priority Scheduling on a PTX Series Router
- CoS Support on EVPN VXLANs
- Understanding CoS CLI Configuration Statements on PTX Series Routers
- Classification Based on Outer Header of Decapsulation Tunnel
-
- play_arrow Configuring Line Card-Specific and Interface-Specific Functionality
- play_arrow Feature Support of Line Cards and Interfaces
- play_arrow Configuring Class of Service for Tunnels
- play_arrow Configuring Class of Service on Services PICs
- CoS on Services PICs Overview
- Configuring CoS Rules on Services PICs
- Configuring CoS Rule Sets on Services PICs
- Example: Configuring CoS Rules on Services PICs
- Packet Rewriting on Services Interfaces
- Multiservices PIC ToS Translation
- Fragmentation by Forwarding Class Overview
- Configuring Fragmentation by Forwarding Class
- Configuring Drop Timeout Interval for Fragmentation by Forwarding Class
- Example: Configuring Fragmentation by Forwarding Class
- Allocating Excess Bandwidth Among Frame Relay DLCIs on Multiservices PICs
- Configuring Rate Limiting and Sharing of Excess Bandwidth on Multiservices PICs
- play_arrow Configuring Class of Service on IQ and Enhanced IQ (IQE) PICs
- CoS on Enhanced IQ PICs Overview
- Calculation of Expected Traffic on IQE PIC Queues
- Configuring the Junos OS to Support Eight Queues on IQ Interfaces for T Series and M320 Routers
- BA Classifiers and ToS Translation Tables
- Configuring ToS Translation Tables
- Configuring Hierarchical Layer 2 Policers on IQE PICs
- Configuring Excess Bandwidth Sharing on IQE PICs
- Configuring Rate-Limiting Policers for High Priority Low-Latency Queues on IQE PICs
- Applying Scheduler Maps and Shaping Rate to Physical Interfaces on IQ PICs
- Applying Scheduler Maps to Chassis-Level Queues
- play_arrow Configuring Class of Service on Ethernet IQ2 and Enhanced IQ2 PICs
- CoS on Enhanced IQ2 PICs Overview
- CoS Features and Limitations on IQ2 and IQ2E PICs (M Series and T Series)
- Differences Between Gigabit Ethernet IQ and Gigabit Ethernet IQ2 PICs
- Shaping Granularity Values for Enhanced Queuing Hardware
- Ethernet IQ2 PIC RTT Delay Buffer Values
- Configuring BA Classifiers for Bridged Ethernet
- Setting the Number of Egress Queues on IQ2 and Enhanced IQ2 PICs
- Configuring the Number of Schedulers per Port for Ethernet IQ2 PICs
- Applying Scheduler Maps to Chassis-Level Queues
- CoS for L2TP Tunnels on Ethernet Interface Overview
- Configuring CoS for L2TP Tunnels on Ethernet Interfaces
- Configuring LNS CoS for Link Redundancy
- Example: Configuring L2TP LNS CoS Support for Link Redundancy
- Configuring Shaping on 10-Gigabit Ethernet IQ2 PICs
- Configuring Per-Unit Scheduling for GRE Tunnels Using IQ2 and IQ2E PICs
- Understanding Burst Size Configuration on IQ2 and IQ2E Interfaces
- Configuring Burst Size for Shapers on IQ2 and IQ2E Interfaces
- Configuring a CIR and a PIR on Ethernet IQ2 Interfaces
- Example: Configuring Shared Resources on Ethernet IQ2 Interfaces
- Configuring and Applying IEEE 802.1ad Classifiers
- Configuring Rate Limits to Protect Lower Queues on IQ2 and Enhanced IQ2 PICs
- Simple Filters Overview
- Configuring a Simple Filter
- play_arrow Configuring Class of Service on 10-Gigabit Ethernet LAN/WAN PICs with SFP+
- CoS on 10-Gigabit Ethernet LAN/WAN PIC with SFP+ Overview
- BA and Fixed Classification on 10-Gigabit Ethernet LAN/WAN PIC with SFP+ Overview
- DSCP Rewrite for the 10-Gigabit Ethernet LAN/WAN PIC with SFP+
- Configuring DSCP Rewrite for the 10-Gigabit Ethernet LAN/WAN PIC
- Queuing on 10-Gigabit Ethernet LAN/WAN PICs Properties
- Mapping Forwarding Classes to CoS Queues on 10-Gigabit Ethernet LAN/WAN PICs
- Scheduling and Shaping on 10-Gigabit Ethernet LAN/WAN PICs Overview
- Example: Configuring Shaping Overhead on 10-Gigabit Ethernet LAN/WAN PICs
- play_arrow Configuring Class of Service on Enhanced Queuing DPCs
- Enhanced Queuing DPC CoS Properties
- Configuring Rate Limits on Enhanced Queuing DPCs
- Configuring WRED on Enhanced Queuing DPCs
- Configuring MDRR on Enhanced Queuing DPCs
- Configuring Excess Bandwidth Sharing
- Configuring Customer VLAN (Level 3) Shaping on Enhanced Queuing DPCs
- Simple Filters Overview
- Configuring Simple Filters on Enhanced Queuing DPCs
- Configuring a Simple Filter
- play_arrow Configuring Class of Service on MICs, MPCs, and MLCs
- CoS Features and Limitations on MIC and MPC Interfaces
- Dedicated Queue Scaling for CoS Configurations on MIC and MPC Interfaces Overview
- Verifying the Number of Dedicated Queues Configured on MIC and MPC Interfaces
- Scaling of Per-VLAN Queuing on Non-Queuing MPCs
- Increasing Available Bandwidth on Rich-Queuing MPCs by Bypassing the Queuing Chip
- Flexible Queuing Mode
- Multifield Classifier for Ingress Queuing on MX Series Routers with MPC
- Example: Configuring a Filter for Use as an Ingress Queuing Filter
- Ingress Queuing Filter with Policing Functionality
- Ingress Rate Limiting on MX Series Routers with MPCs
- Rate Shaping on MIC and MPC Interfaces
- Per-Priority Shaping on MIC and MPC Interfaces Overview
- Example: Configuring Per-Priority Shaping on MIC and MPC Interfaces
- Configuring Static Shaping Parameters to Account for Overhead in Downstream Traffic Rates
- Example: Configuring Static Shaping Parameters to Account for Overhead in Downstream Traffic Rates
- Traffic Burst Management on MIC and MPC Interfaces Overview
- Understanding Hierarchical Scheduling for MIC and MPC Interfaces
- Configuring Ingress Hierarchical CoS on MIC and MPC Interfaces
- Configuring a CoS Scheduling Policy on Logical Tunnel Interfaces
- Per-Unit Scheduling and Hierarchical Scheduling for MPC Interfaces
- Managing Dedicated and Remaining Queues for Static CoS Configurations on MIC and MPC Interfaces
- Excess Bandwidth Distribution on MIC and MPC Interfaces Overview
- Bandwidth Management for Downstream Traffic in Edge Networks Overview
- Scheduler Delay Buffering on MIC and MPC Interfaces
- Managing Excess Bandwidth Distribution on Static Interfaces on MICs and MPCs
- Drop Profiles on MIC and MPC Interfaces
- Intelligent Oversubscription on MIC and MPC Interfaces Overview
- Jitter Reduction in Hierarchical CoS Queues
- Example: Reducing Jitter in Hierarchical CoS Queues
- CoS on Ethernet Pseudowires in Universal Edge Networks Overview
- CoS Scheduling Policy on Logical Tunnel Interfaces Overview
- Configuring CoS on an Ethernet Pseudowire for Multiservice Edge Networks
- CoS for L2TP LNS Inline Services Overview
- Configuring Static CoS for an L2TP LNS Inline Service
- CoS on Circuit Emulation ATM MICs Overview
- Configuring CoS on Circuit Emulation ATM MICs
- Understanding IEEE 802.1p Inheritance push and swap from a Transparent Tag
- Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag
- CoS on Application Services Modular Line Card Overview
- play_arrow Configuring Class of Service on Aggregated, Channelized, and Gigabit Ethernet Interfaces
- Limitations on CoS for Aggregated Interfaces
- Policer Support for Aggregated Ethernet Interfaces Overview
- Understanding Schedulers on Aggregated Interfaces
- Examples: Configuring CoS on Aggregated Interfaces
- Hierarchical Schedulers on Aggregated Ethernet Interfaces Overview
- Configuring Hierarchical Schedulers on Aggregated Ethernet Interfaces
- Example: Configuring Scheduling Modes on Aggregated Interfaces
- Enabling VLAN Shaping and Scheduling on Aggregated Interfaces
- Class of Service on demux Interfaces
- Example: Configuring Per-Unit Schedulers for Channelized Interfaces
- Applying Layer 2 Policers to Gigabit Ethernet Interfaces
-
- play_arrow Configuration Statements and Operational Commands
Manage Ingress Oversubscription with Traffic Class Maps
Ingress Oversubscription at the Packet Forwarding Engine
Ingress oversubscription is a state where the transmission rate of the incoming packets is much higher than the rate that the Packet Forwarding Engine and router can handle, causing important packets to be dropped. If an oversubscribed link or service experiences an excess of traffic, it can result in traffic loss or delay that could potentially affect other services and links.
The Packet Forwarding Engine uses fixed rules to decide the priority of incoming packets. Based on these fixed rules, the Packet Forwarding Engine categorizes incoming packets into high-priority network control packets and low-priority best-effort packets. Packets with protocols such as routing protocols are classified as network control packets. Packets with protocols such as Telnet, FTP, and SSH are classified as best-effort packets.
The limitation of these fixed rules is that even if the trusted and non-network-control packets marked by a CE router are forwarded to the transit router, the transit router might drop these packets. This packet drop happens because, according to the fixed rules, none of these packets are high-priority packets for the transit router.
To overcome this limitation, you can prioritize and classify the traffic entering a
Packet Forwarding Engine by configuring a traffic class map based on CoS values and
associating the values with a traffic class such as real-time
,
network control
, or best-effort
. You can
associate the traffic class map with an interface on the transit router. During
ingress oversubscription, the router interface uses this user-defined traffic class
map to select the packet priority.
Use Feature Explorer to confirm platform and release support for traffic class maps.
Example: Configuring Traffic Class Maps
This example shows the configuration of traffic class maps on an MX Series routers with MPCs.
Use Feature Explorer to confirm platform and release support for traffic class maps.
Requirements
This example uses the following hardware and software components:
One MX Series router
One CE router
Before you configure the traffic class maps, be sure you have:
Connected the CE router to the MX Series router.
Overview and Topology
This example shows the configuration of traffic class maps on an MX Series router that is connected to a CE router.

As shown in Figure 1, the CE router forwards the traffic to interface xe-4/0/0 and xe-4/0/1 on the router.
The traffic class maps need to be configured on the router and associated with the interface xe-4/0/0 and the interface xe-4/0/1 so that the packets can be classified based on the user-defined configuration. When ingress oversubscription occurs, the router uses the user-defined traffic class map to process the packets.
This example shows how to create the following traffic class maps with CoS code points and associate these code points with the traffic class.
IPv4 precedence traffic class map with code points 000 001, 010 011, and 100 101. Map these code points to the real-time, network-control, and best-effort traffic classes, respectively.
MPLS EXP traffic class map with code points 000 001, 010 011, and 100 101. Map these code points to the real-time, network-control, and best-effort traffic classes, respectively.
IEEE 802.1 traffic class map with code points 000 001, 010 011, and 100 101. Map these code points to the real-time, network-control, and best-effort traffic classes, respectively.
DSCP traffic class map with code points 100001 100010 100011, 010011 010100 010101, and 101001 101010 101011. Map these code points to the real-time, network-control, and best-effort traffic classes, respectively.
IEEE 802.1ad traffic class map with code points 0000 0001 1000 1001, 0010 0011 1010 1011, and 0100 0101 1100 1101. Map these code points to the real-time, network-control, and best-effort traffic classes, respectively.
The traffic class maps IPv4 precedence, MPLS EXP, and IEEE 802.1 are associated with the interface xe-4/0/0. The traffic class maps DSCP and IEEE 802.1ad are associated with the interface xe-4/0/1.
Configuration
To configure the traffic class map, perform the following tasks:
- CLI Quick Configuration
- Configuring Interfaces
- Configuring Traffic Class Maps for the Code Points and Mapping the Code Points to a Traffic Class
- Associating Interfaces with Traffic Class Maps
- Results
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them in
a text file, and remove any line breaks. Change any details necessary to
match your network configuration, and paste the commands into the CLI at the
[edit]
hierarchy level.
[edit] set interfaces xe-4/0/0 unit 0 family inet address 198.51.100.0/24 set interfaces xe-4/0/1 vlan-tagging set interfaces xe-4/0/1 unit 0 vlan-id 111 set interfaces xe-4/0/1 unit 0 family inet address 198.51.100.1/24 set class-of-service traffic-class-map inet-precedence inetp traffic-class real-time code-points [ 000 001 ] set class-of-service traffic-class-map inet-precedence inetp traffic-class network-control code-points [ 010 011 ] set class-of-service traffic-class-map inet-precedence inetp traffic-class best-effort code-points [ 100 101 ] set class-of-service traffic-class-map exp mpls_exp traffic-class real-time code-points [ 000 001 ] set class-of-service traffic-class-map exp mpls_exp traffic-class network-control code-points [ 010 011 ] set class-of-service traffic-class-map exp mpls_exp traffic-class best-effort code-points [ 100 101 ] set class-of-service traffic-class-map ieee-802.1 802.1p traffic-class real-time code-points [ 000 001 ] set class-of-service traffic-class-map ieee-802.1 802.1p traffic-class network-control code-points [ 010 011 ] set class-of-service traffic-class-map ieee-802.1 802.1p traffic-class best-effort code-points [ 100 101 ] set class-of-service traffic-class-map dscp dscp_v4 traffic-class real-time code-points [ 100001 100010 100011 ] set class-of-service traffic-class-map dscp dscp_v4 traffic-class network-control code-points [ 010011 010100 010101 ] set class-of-service traffic-class-map dscp dscp_v4 traffic-class best-effort code-points [ 101001 101010 101011 ] set class-of-service traffic-class-map ieee-802.1ad 802.1ad traffic-class real-time code-points [ 0000 0001 1000 1001 ] set class-of-service traffic-class-map ieee-802.1ad 802.1ad traffic-class network-control code-points [ 0010 0011 1010 1011 ] set class-of-service traffic-class-map ieee-802.1ad 802.1ad traffic-class best-effort code-points [ 0100 0101 1100 1101 ] set interfaces xe-4/0/0 traffic-class-map inet-precedence inetp set interfaces xe-4/0/0 traffic-class-map exp mpls_exp set interfaces xe-4/0/0 traffic-class-map ieee-802.1 802.1p vlan-tag inner set interfaces xe-4/0/1 traffic-class-map dscp dscp_v4 set interfaces xe-4/0/1 traffic-class-map ieee-802.1ad 802.1ad vlan-tag inner
Configuring Interfaces
Step-by-Step Procedure
Configure the interfaces. These interfaces need to be associated with traffic class maps.
Configure the interface xe-4/0/0 with unit 0 as its logical interface, inet as protocol family, and 198.51.100.0/24 as the IP address.
content_copy zoom_out_map[edit] user@host#set interfaces xe-4/0/0 unit 0 family inet address 198.51.100.0/24
Configure the interface xe-4/0/1 with unit 0 as its logical interface, inet as protocol family, and 198.51.100.1/24 as the IP address. Also, enable the VLAN tagging and configure a VLAN ID (for example, 111) to receive and transmit VLAN-tagged frames on the interface.
content_copy zoom_out_map[edit] user@host#set interfaces xe-4/0/1 vlan-tagging user@host#set interfaces xe-4/0/1 unit 0 vlan-id 111 user@host#set interfaces xe-4/0/1 unit 0 family inet address 198.51.100.1/24
Configuring Traffic Class Maps for the Code Points and Mapping the Code Points to a Traffic Class
Step-by-Step Procedure
You can prioritize and classify the traffic entering a Packet Forwarding Engine by configuring a traffic class map based on the code points and associating the map with the traffic class.
Create an IPv4 precedence traffic class map inetp and map its code points 000 001, 010 011, and 100 101 to the real-time, network control, and best-effort traffic classes, respectively.
content_copy zoom_out_map[edit class-of-service] user@host# set traffic-class-map inet-precedence inetp traffic-class real-time code-points [ 000 001 ] user@host# set traffic-class-map inet-precedence inetp traffic-class network-control code-points [ 010 011 ] user@host# set traffic-class-map inet-precedence inetp traffic-class best-effort code-points [ 100 101 ]
Create an MPLS EXP traffic class map mpls_exp and map the code points 000 001, 010 011, and 100 101 to the real-time, network control, and best-effort traffic classes, respectively.
content_copy zoom_out_map[edit class-of-service] user@host# set traffic-class-map exp mpls_exp traffic-class real-time code-points [ 000 001 ] user@host# set traffic-class-map exp mpls_exp traffic-class network-control code-points [ 010 011 ] user@host# set traffic-class-map exp mpls_exp traffic-class best-effort code-points [ 100 101 ]
Create an IEEE 802.1 traffic class map 802.1p and map the code points 000 001, 010 011, and 100 101 to the real-time, network control, and best-effort traffic classes, respectively.
content_copy zoom_out_map[edit class-of-service] user@host# set traffic-class-map ieee-802.1 802.1p traffic-class real-time code-points [ 000 001 ] user@host# set traffic-class-map ieee-802.1 802.1p traffic-class network-control code-points [ 010 011 ] user@host# set traffic-class-map ieee-802.1 802.1p traffic-class best-effort code-points [ 100 101 ]
Create a DSCP traffic class map dscp_v4 and map the code points 100001 100010 100011, 010011 010100 010101, and 101001 101010 101011 to the real-time, network control, and best-effort traffic classes, respectively.
content_copy zoom_out_map[edit class-of-service] user@host# set traffic-class-map dscp dscp_v4 traffic-class real-time code-points [ 100001 100010 100011 ] user@host# set traffic-class-map dscp dscp_v4 traffic-class network-control code-points [ 010011 010100 010101 ] user@host# set traffic-class-map dscp dscp_v4 traffic-class best-effort code-points [ 101001 101010 101011 ]
Create an IEEE802.1ad traffic class map 802.1ad and map the code points 0000 0001 1000 1001,0010 0011 1010 1011, and 0100 0101 1100 1101 to the real-time, network control, and best-effort traffic classes, respectively.
content_copy zoom_out_map[edit class-of-service] user@host# set traffic-class-map ieee-802.1ad 802.1ad traffic-class real-time code-points [ 0000 0001 1000 1001 ] user@host# set traffic-class-map ieee-802.1ad 802.1ad traffic-class network-control code-points [ 0010 0011 1010 1011 ] user@host# set traffic-class-map ieee-802.1ad 802.1ad traffic-class best-effort code-points [ 0100 0101 1100 1101 ]
Associating Interfaces with Traffic Class Maps
Step-by-Step Procedure
You need to associate the configured traffic class maps with the interfaces on which you want to prioritize and classify the input traffic.
Associate the traffic class maps inetp, mpls_exp, and 802.1p with the interface xe-4/0/0.
content_copy zoom_out_map[edit class-of-service] user@host# set interfaces xe-4/0/0 traffic-class-map inet-precedence inetp user@host# set interfaces xe-4/0/0 traffic-class-map exp mpls_exp user@host# set interfaces xe-4/0/0 traffic-class-map ieee-802.1 802.1p vlan-tag inner
Associate the traffic class map dscp_v4 and 802.1ad with the interface xe-4/0/1.
content_copy zoom_out_map[edit class-of-service] user@host# set interfaces xe-4/0/1 traffic-class-map dscp dscp_v4 user@host# set interfaces xe-4/0/1 traffic-class-map ieee-802.1ad 802.1ad vlan-tag inner
Results
interfaces { xe-4/0/0 { unit 0 { family inet { address 198.51.100.0/24; } } } xe-4/0/1 { vlan-tagging; unit 0 { vlan-id 111; family inet { address 198.51.100.1/24; } } } } class-of-service { traffic-class-map { inet-precedence inetp { traffic-class real-time code-points [ 000 001 ]; traffic-class network-control code-points [ 010 011 ]; traffic-class best-effort code-points [ 100 101 ]; } dscp dscp_v4 { traffic-class real-time code-points [ 100001 100010 100011 ]; traffic-class network-control code-points [ 010011 010100 010101 ]; traffic-class best-effort code-points [ 101001 101010 101011 ]; } exp mpls_exp { traffic-class real-time code-points [ 000 001 ]; traffic-class network-control code-points [ 010 011 ]; traffic-class best-effort code-points [ 100 101 ]; } ieee-802.1 802.1p { traffic-class real-time code-points [ 000 001 ]; traffic-class network-control code-points [ 010 011 ]; traffic-class best-effort code-points [ 100 101 ]; } ieee-802.1ad 802.1ad { traffic-class real-time code-points [ 0000 0001 1000 1001 ]; traffic-class network-control code-points [ 0010 0011 1010 1011 ]; traffic-class best-effort code-points [ 0100 0101 1100 1101 ]; } } interfaces { xe-4/0/0 { traffic-class-map { inet-precedence inetp; exp mpls_exp; ieee-802.1 802.1p vlan-tag inner; } } xe-4/0/1 { traffic-class-map { dscp dscp_v4; ieee-802.1ad 802.1ad vlan-tag inner; } } } }
Verification
- Verifying Mapping of Code Points to Input Traffic Classes
- Verifying Mapping of Interfaces to Traffic Class Maps
- Verifying Traffic Class Information on the Interface
Verifying Mapping of Code Points to Input Traffic Classes
Purpose
Verify that the code points of traffic class maps are mapped to the corresponding traffic classes.
Action
In operational mode, enter the show class-of-service
traffic-class-map
command.
user@host> show class-of-service traffic-class-map Traffic-class-map: inetp, Code-point type: inet-precedence, Index: 43854 Code point Traffic class 000 real-time 001 real-time 010 network-control 011 network-control 100 best-effort 101 best-effort Traffic-class-map: dscp_v4, Code-point type: dscp, Index: 37469 Code point Traffic class 010011 network-control 010100 network-control 010101 network-control 100001 real-time 100010 real-time 100011 real-time 101001 best-effort 101010 best-effort 101011 best-effort Traffic-class-map: mpls_exp, Code-point type: exp, Index: 39622 Code point Traffic class 000 real-time 001 real-time 010 network-control 011 network-control 100 best-effort 101 best-effort Traffic-class-map: 802.1p, Code-point type: ieee-802.1, Index: 13605 Code point Traffic class 000 real-time 001 real-time 010 network-control 011 network-control 100 best-effort 101 best-effort Traffic-class-map: 802.1ad, Code-point type: ieee-802.1ad, Index: 13677 Code point Traffic class 0000 real-time 0001 real-time 0010 network-control 0011 network-control 0100 best-effort 0101 best-effort 1000 real-time 1001 real-time 1010 network-control 1011 network-control 1100 best-effort 1101 best-effort
Meaning
The display output fields Traffic-class-map
and
Code-point type
indicate the configured traffic
class map and the type of code point information, respectively.
The fields Code point
and Traffic class
show the mapping between the code points and the traffic class.
Verifying Mapping of Interfaces to Traffic Class Maps
Purpose
Verify that the configured interfaces are mapped to the corresponding traffic class maps.
Action
In operational mode, enter the show class-of-service
forwarding-table traffic-class-map mapping
command.
user@host> show class-of-service forwarding-table traffic-class-map mapping Interface Index Table Index Table type xe-4/0/0 162 43854 INET-Precedence 39622 MPLS EXP 13605 IEEE-802.1 xe-4/0/1 163 37469 DSCP 13677 IEEE-802.1AD
Meaning
The output shows that:
Interface
xe-4/0/0
is associated with the traffic class mapsINET-Precedence
,MPLS EXP
, andIEEE-802.1
.Interface
xe-4/0/1
is associated with the traffic class mapsDSCP
andIEEE-802.1AD
.
Verifying Traffic Class Information on the Interface
Purpose
Verify the packet information based on the configured traffic class map.
Action
In operational mode, enter the show interfaces xe-4/0/0
extensive
and show interfaces xe-4/0/1
extensive
commands.
user@host> show interfaces xe-4/0/0 extensive Physical interface: xe-4/0/0, Enabled, Physical link is Up Interface index: 162, SNMP ifIndex: 541, Generation: 165 Link-level type: Ethernet, MTU: 1518, MRU: 0, LAN-PHY mode, Speed: 10Gbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: None, Source filtering: Disabled, Flow control: Enabled ... Preclassifier statistics: Traffic Class Received Packets Transmitted Packets Dropped Packets real-time 3000 3000 0 network-control 2000 2000 0 best-effort 2000 1000 1000 Interface transmit statistics: Enabled ... user@host> show interfaces xe-4/0/1 extensive Physical interface: xe-4/0/1, Enabled, Physical link is Up Interface index: 163, SNMP ifIndex: 525, Generation: 166 Link-level type: Ethernet, MTU: 1518, MRU: 0, LAN-PHY mode, Speed: 10Gbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: None, Source filtering: Disabled, Flow control: Enabled ... Preclassifier statistics: Traffic Class Received Packets Transmitted Packets Dropped Packets real-time 2000 2000 0 network-control 1000 1000 0 best-effort 1000 600 400 Interface transmit statistics: Enabled ...
Meaning
The Preclassifier statistics
field shows the information
for received, transmitted, and dropped packets for each of the
configured traffic class map.