- 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 Class of Service
- play_arrow Assigning Service Levels with Behavior Aggregate Classifiers
- Understanding How Behavior Aggregate Classifiers Prioritize Trusted Traffic
- Default IP Precedence Classifier
- Default DSCP and DSCP IPv6 Classifiers
- Default MPLS EXP Classifier
- Default IEEE 802.1p Classifier
- Default IEEE 802.1ad Classifier
- Default Aliases for CoS Value Bit Patterns Overview
- Defining Aliases for CoS Value Bit Patterns
- Configuring Behavior Aggregate Classifiers
- Applying Behavior Aggregate Classifiers to Logical Interfaces
- Example: Configuring and Applying a Default DSCP Behavior Aggregate Classifier
- Example: Configuring Behavior Aggregate Classifiers
- Understanding DSCP Classification for VPLS
- Example: Configuring DSCP Classification for VPLS
- Configuring Class of Service for MPLS LSPs
- Applying DSCP Classifiers to MPLS Traffic
- Applying MPLS EXP Classifiers to Routing Instances
- Applying MPLS EXP Classifiers for Explicit-Null Labels
- Manage Ingress Oversubscription with Traffic Class Maps
- play_arrow Assigning Service Levels with Multifield Classifiers
- Overview of Assigning Service Levels to Packets Based on Multiple Packet Header Fields
- Configuring Multifield Classifiers
- Using Multifield Classifiers to Set Packet Loss Priority
- Example: Configuring and Applying a Firewall Filter for a Multifield Classifier
- Example: Classifying Packets Based on Their Destination Address
- Example: Configuring and Verifying a Complex Multifield Filter
- play_arrow Controlling Network Access with Traffic Policing
- Controlling Network Access Using Traffic Policing Overview
- Effect of Two-Color Policers on Shaping Rate Changes
- Configuring Policers Based on Logical Interface Bandwidth
- Example: Limiting Inbound Traffic at Your Network Border by Configuring an Ingress Single-Rate Two-Color Policer
- Example: Performing CoS at an Egress Network Boundary by Configuring an Egress Single-Rate Two-Color Policer
- Example: Limiting Inbound Traffic Within Your Network by Configuring an Ingress Single-Rate Two-Color Policer and Configuring Multifield Classifiers
- Example: Limiting Outbound Traffic Within Your Network by Configuring an Egress Single-Rate Two-Color Policer and Configuring Multifield Classifiers
- Overview of Tricolor Marking Architecture
- Enabling Tricolor Marking and Limitations of Three-Color Policers
- Configuring and Applying Tricolor Marking Policers
- Configuring Single-Rate Tricolor Marking
- Configuring Two-Rate Tricolor Marking
- Example: Configuring and Verifying Two-Rate Tricolor Marking
- Applying Firewall Filter Tricolor Marking Policers to Interfaces
- Policer Overhead to Account for Rate Shaping in the Traffic Manager
- play_arrow Defining Forwarding Behavior with Forwarding Classes
- Understanding How Forwarding Classes Assign Classes to Output Queues
- Default Forwarding Classes
- Configuring a Custom Forwarding Class for Each Queue
- Configuring Up to 16 Custom Forwarding Classes
- Classifying Packets by Egress Interface
- Forwarding Policy Options Overview
- Configuring CoS-Based Forwarding
- Example: Configuring CoS-Based Forwarding
- Example: Configuring CoS-Based Forwarding for Different Traffic Types
- Example: Configuring CoS-Based Forwarding for IPv6
- Applying Forwarding Classes to Interfaces
- Understanding Queuing and Marking of Host Outbound Traffic
- Forwarding Classes and Fabric Priority Queues
- Default Routing Engine Protocol Queue Assignments
- Assigning Forwarding Class and DSCP Value for Routing Engine-Generated Traffic
- Example: Writing Different DSCP and EXP Values in MPLS-Tagged IP Packets
- Change the Default Queuing and Marking of Host Outbound Traffic
- Example: Configure Different Queuing and Marking Defaults for Outbound Routing Engine and Distributed Protocol Handler Traffic
- Overriding the Input Classification
- play_arrow Defining Output Queue Properties with Schedulers
- How Schedulers Define Output Queue Properties
- Default Schedulers Overview
- Configuring Schedulers
- Configuring Scheduler Maps
- Applying Scheduler Maps Overview
- Applying Scheduler Maps to Physical Interfaces
- Configuring Traffic Control Profiles for Shared Scheduling and Shaping
- Configuring an Input Scheduler on an Interface
- Understanding Interface Sets
- Configuring Interface Sets
- Interface Set Caveats
- Configuring Internal Scheduler Nodes
- Example: Configuring and Applying Scheduler Maps
- play_arrow Controlling Bandwidth with Scheduler Rates
- Oversubscribing Interface Bandwidth
- Configuring Scheduler Transmission Rate
- Providing a Guaranteed Minimum Rate
- PIR-Only and CIR Mode
- Excess Rate and Excess Priority Configuration Examples
- Controlling Remaining Traffic
- Bandwidth Sharing on Nonqueuing Packet Forwarding Engines Overview
- Configuring Rate Limits on Nonqueuing Packet Forwarding Engines
- Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs
- Example: Applying Scheduler Maps and Shaping Rate to DLCIs
- Example: Applying Scheduling and Shaping to VLANs
- Applying a Shaping Rate to Physical Interfaces Overview
- Configuring the Shaping Rate for Physical Interfaces
- Example: Limiting Egress Traffic on an Interface Using Port Shaping for CoS
- Configuring Input Shaping Rates for Both Physical and Logical Interfaces
- play_arrow Setting Transmission Order with Scheduler Priorities and Hierarchical Scheduling
- Priority Scheduling Overview
- Configuring Schedulers for Priority Scheduling
- Associating Schedulers with Fabric Priorities
- Hierarchical Class of Service Overview
- Hierarchical Class of Service Network Scenarios
- Understanding Hierarchical Scheduling
- Priority Propagation in Hierarchical Scheduling
- Hierarchical CoS for Metro Ethernet Environments
- Hierarchical Schedulers and Traffic Control Profiles
- Example: Building a Four-Level Hierarchy of Schedulers
- Hierarchical Class of Service for Network Slicing
- Configuring Ingress Hierarchical CoS
- play_arrow Controlling Congestion with Scheduler RED Drop Profiles, Buffers, PFC, and ECN
- RED Drop Profiles for Congestion Management
- Determining Packet Drop Behavior by Configuring Drop Profile Maps for Schedulers
- Managing Congestion by Setting Packet Loss Priority for Different Traffic Flows
- Mapping PLP to RED Drop Profiles
- Managing Congestion on the Egress Interface by Configuring the Scheduler Buffer Size
- Managing Transient Traffic Bursts by Configuring Weighted RED Buffer Occupancy
- Example: Managing Transient Traffic Bursts by Configuring Weighted RED Buffer Occupancy
- Understanding PFC Using DSCP at Layer 3 for Untagged Traffic
- Configuring DSCP-based PFC for Layer 3 Untagged Traffic
- PFC Watchdog
- CoS Explicit Congestion Notification
- Example: Configuring Static and Dynamic ECN
- play_arrow Altering Outgoing Packet Headers Using Rewrite Rules
- Rewriting Packet Headers to Ensure Forwarding Behavior
- Applying Default Rewrite Rules
- Configuring Rewrite Rules
- Configuring Rewrite Rules Based on PLP
- Applying IEEE 802.1p Rewrite Rules to Dual VLAN Tags
- Applying IEEE 802.1ad Rewrite Rules to Dual VLAN Tags
- Rewriting IEEE 802.1p Packet Headers with an MPLS EXP Value
- Setting IPv6 DSCP and MPLS EXP Values Independently
- Configuring DSCP Values for IPv6 Packets Entering the MPLS Tunnel
- Setting Ingress DSCP Bits for Multicast Traffic over Layer 3 VPNs
- Applying Rewrite Rules to Output Logical Interfaces
- Rewriting MPLS and IPv4 Packet Headers
- Rewriting the EXP Bits of All Three Labels of an Outgoing Packet
- Defining a Custom Frame Relay Loss Priority Map
- Example: Per-Node Rewriting of EXP Bits
- Example: Rewriting CoS Information at the Network Border to Enforce CoS Strategies
- Example: Remarking Diffserv Code Points to MPLS EXPs to Carry CoS Profiles Across a Service Provider’s L3VPN MPLS Network
- Example: Remarking Diffserv Code Points to 802.1P PCPs to Carry CoS Profiles Across a Service Provider’s VPLS Network
- Assigning Rewrite Rules on a Per-Customer Basis Using Policy Maps
- Host Outbound Traffic IEEE802.1p Rewrite
- play_arrow Altering Class of Service Values in Packets Exiting the Network Using IPv6 DiffServ
- Resources for CoS with DiffServ for IPv6
- System Requirements for CoS with DiffServ for IPv6
- Terms and Acronyms for CoS with DiffServ for IPv6
- Default DSCP Mappings
- Default Forwarding Classes
- Juniper Networks Default Forwarding Classes
- Roadmap for Configuring CoS with IPv6 DiffServ
- Configuring a Firewall Filter for an MF Classifier on Customer Interfaces
- Applying the Firewall Filter to Customer Interfaces
- Assigning Forwarding Classes to Output Queues
- Configuring Rewrite Rules
- DSCP IPv6 Rewrites and Forwarding Class Maps
- Applying Rewrite Rules to an Interface
- Configuring RED Drop Profiles
- Configuring BA Classifiers
- Applying a BA Classifier to an Interface
- Configuring a Scheduler
- Configuring Scheduler Maps
- Applying a Scheduler Map to an Interface
- Example: Configuring DiffServ for IPv6
-
- 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
Hierarchical Class of Service in ACX Series Routers
Scheduling properties can be applied at physical as well as logical interface and logical interface set levels. Service providers can support hierarchical class of service (HCoS) at multiple levels to meet the service level agreements and bandwidth allocations for subscribers.
Hierarchical Scheduling on the Physical Interface
By default, the queuing mode on all the physical interfaces in ACX routers that support HCoS is 4 queues per physical interface (port). In the hierarchical scheduler mode, you can configure up to 3 levels (physical interface, logical interface, and queues) or 4 levels (including logical interfaces sets) of scheduling, depending on the platform.
You can enable hierarchical scheduling by including the
hierarchical-scheduler
CLI command under the [edit interfaces
interface-name]
hierarchy:
[edit] interfaces xe-0/0/1 { hierarchical-scheduler; }
If you change the physical interface queuing mode from default to hierarchical scheduler mode or vice-versa, the traffic flowing out of the physical interface during the mode change results in a transient loss of traffic data.
Traffic Control Profiles
Traffic control profiles hold parameters for levels above the queue level of the scheduler hierarchy. You configure the scheduling and shaping on the scheduler nodes using traffic control profiles and scheduler maps for the queue level. The traffic control profile defines the following characteristics of a scheduler node:
Scheduler-map
Shaping rate
Guaranteed rate
You attach traffic control profiles at the physical interface, logical interface set, and
logical interface level. You define scheduling and shaping characteristics for the scheduler
node using shaping-rate
and guaranteed-rate
. The following
is a sample traffic control profile configuration:
[edit class-of-service traffic-control-profiles] tcp-500m-shaping-rate { shaping-rate 500m; } tcp-vlan0 { shaping-rate 200m; guaranteed-rate 100m; scheduler-map tcp-map-vlan0; # Applies scheduler maps to customer VLANs. } tcp-vlan1 { shaping-rate 100m; guaranteed-rate 40m; scheduler-map tcp-map-vlan1; # Applies scheduler maps to customer VLANs. }
Schedulers
A scheduler defines scheduling and queuing characteristics of a queue and holds the information about the queues, the last level of the hierarchy. The following is a sample scheduler configuration:
[edit class-of-service schedulers] sched-vlan0-q0 { priority low; transmit-rate 20m; buffer-size temporal 100ms; drop-profile loss-priority low dp-low; drop-profile loss-priority high dp-high; } sched-vlanl-q1 { priority strict-high; shaping-rate 20m; }
We do not support transmit-rate
with priority queues on ACX Series
routers.
Deep Buffer Control
With deep buffer control, also known as fine-grained buffer control, you can configure buffers on a per-queue basis.
On ACX routers running Junos OS Evolved, by default all queues on HQoS enabled logical interfaces have a dedicated buffer of 4KB and a shared buffer of 10msec. Table 1 and Table 2 show the guaranteed and shared per queue default buffers on ACX routers running Junos OS Evolved.
Interface Speed (GB) | Minimum Guaranteed Buffer (KB) |
---|---|
1/10 | 125 |
25/40/50 | 625 |
100 | 1250 |
200 | 2500 |
400 | 5000 |
Interface Speed (GB) | Shared buffer size (MB) | Shared buffer size (ms) |
---|---|---|
1 | 5 | 40 |
10 | 50 | 40 |
25 | 250 | 80 |
40 | 250 | 50 |
50 | 250 | 40 |
100 | 500 | 40 |
200 | 500 | 20 |
400 | 500 | 10 |
You can configure the shared and guaranteed buffers for each queue on HCoS-enabled ports and logical interfaces. See buffer-size (Schedulers).
Use the temporal
option to configure shared buffers.
Drop Profiles
Drop profiles allow you to specify queue specific behavior to drop packets based on WRED profile under congestion. The following is a sample drop profile configuration:
[edit class-of-service drop-profiles] dp-low { fill-level 80 drop-probability 0; fill-level 100 drop-probability 100; } dp-high { fill-level 60 drop-probability 0; fill-level 80 drop-probability 100; }
Scheduler Maps
A scheduler map is referenced by traffic control profiles to define queues. The scheduler map establishes the number of queues over a scheduler node, associating a forwarding-class with a scheduler. The following is a sample scheduler map configuration:
[edit class-of-service scheduler-maps] tcp-map-vlan0 { forwarding-class voice scheduler sched-vlan0-q0; forwarding-class video scheduler sched-vlan0-q1; forwarding-class data scheduler sched-vlan0-q2; } tcp-map-vlan1 { forwarding-class voice scheduler sched-vlan1-q0; forwarding-class video scheduler sched-vlan1-q1; forwarding-class data scheduler sched-vlan1-q2; }
Applying the Traffic Control Profiles
You can attach output-traffic-control-profile
and
output-traffic-control-profile-remaining
at various levels of the
scheduler hierarchy to achieve hierarchical class of service. On an interface set,
output-traffic-control-profile-remaining
is active if there is at least
one member logical interface with an attached
output-traffic-control-profile
and at least one without.
Although a shaping rate can be applied directly to the physical interface, hierarchical schedulers must use a traffic control profile to hold this parameter.
All logical interfaces that are part of an interface set inherit the traffic control profile of the interface set.
The following is a sample configuration to apply traffic control profiles:
[edit class-of-service interfaces] ge-1/0/0 { output-traffic-control-profile tcp-500m-shaping-rate; output-traffic-control-profile-remaining tcp-500m-shaping-rate; unit 0 { output-traffic-control-profile tcp-cvlan0; } unit 1 { output-traffic-control-profile tcp-cvlan1; } } interface-set svlan0 { output-traffic-control-profile tcp-svlan0; } interface-set svlan1 { output-traffic-control-profile tcp-svlan1; }
HCoS on Aggregated Ethernet Interfaces
Configuring HCoS on aggregated Ethernet (AE) interfaces is exactly the same as configuring HCoS on physical interfaces. Apply all HCoS configuration to the AE interface.
You cannot apply HCoS configuration to a physical interface that is a member of an AE interface. To apply HCoS to an AE interface, do not configure HCoS on a physical interface and then add the physical interface to the AE interface. First configure the AE interface, then configure HCoS on the AE interface.
HCoS configuration on an AE interface is automatically applied to each member interface. How the system applies the configuration to each member interfaces (that is, whether the configuration is normalized or not) depends on the AE interface configuration mode:
Link protection mode — system applies configuration directly to each member interface without normalization.
Non-link protection replica mode — system applies configuration directly to each member interface without normalization.
Non-link protection scale mode (default mode) — system does normalize the configuraiton before applying to each member interface.
HCoS configuration has the following requirements when the configuration must be normalized across member interfaces:
transmit-rate
at scheduler/queue level — both percent and absolute configuration allowedshaping-rate
at scheduler/queue level — both percent and absolute configuration allowedguaranteed-rate
at traffic control profile level — only absolute configuration allowedshaping-rate
at traffic control profile level — only absolute configuration allowedshaping-rate
at port level — only absolute configuration allowed
If the configuration must be normalized, rates configured as a percent require no normalization. If the configuration must be normalized, rates configured as absolute must be normalized. You can calculated the normalized value for each interface by deviding the absolute configured value by the number of member interfaces in the AE interface.
Subscriber Services
Supported ACX routers support hierarchical class of service functionality for subscriber services such as Layer 3 VPN, Layer 2 VPN, Ethernet pseudowire (VPWS), and VPLS for logical interface instance on the AC (Access Port).
Hierarchical class of service is not supported for Layer 2 bridging (bridge domain VLAN) service.
The following sections explain the hierarchical class of service configuration for subscriber services:
- Configuring hierarchical class of service for Layer 3 VPN Service
- Configuring hierarchical class of service for Layer 2 VPN (Ethernet Pseudowires) Service
- Configuring hierarchical class of service for VPLS Service
- Verifying the hierarchical class of service configurations
Configuring hierarchical class of service for Layer 3 VPN Service
Supported ACX routers can be configured to provide Layer 3 VPN services to subscribers by connecting the UNI port to a CE device. The physical port can be configured to provide Layer 3 VPN services to multiple subscribers. You can schedule traffic for different Layer 3 VPN instances based on the SLA parameters agreed with the subscriber.
The following is a sample UNI and NNI logical interface configuration on the PE router providing the Layer 3 VPN service:
[edit interfaces] xe-0/0/1 { description “NNI IFL”; unit 0 { family inet { address 100.1.1.1/24; } family mpls; } } ge-0/0/1 { description “UNI IFL”; hierarchical-scheduler; flexible-vlan-tagging; unit 0 { vlan-id 100; family inet { address 20.20.0.1/24; } } unit 1 { vlan-id 101; family inet { address 20.20.1.1/24; } } unit 2 { vlan-id 2; family inet { address 20.20.2.1/24; } } unit 3 { vlan-id 3; family inet { address 20.20.3.1/24; } } unit 4 { vlan-id 4; family inet { address 20.20.4.1/24; } } ... }
Scheduling can be enabled on the interfaces to achieve hierarchical class of service support for traffic flowing from NNI towards UNI direction.
Configuring hierarchical class of service for Layer 2 VPN (Ethernet Pseudowires) Service
Supported ACX routers can be configured to provide Layer 2 VPN services to subscribers based on Ethernet pseudowires where the UNI port is connected to a CE device. The physical port can be configured to provide Layer 2 VPN services to multiple subscribers. You can schedule traffic for different pseudowires based on the SLA parameters agreed with the subscriber. Hierarchical class of service can be enabled per UNI logical interface represented as the attachment point of the Ethernet pseudowire to achieve the functionality.
The following is a sample to configure the UNI logical interface on the PE router providing the Layer 2 VPN service based on Ethernet pseudowire:
[edit interfaces] ge-0/0/1 { hierarchical-scheduler; vlan-tagging; unit 0 { encapsulation vlan-ccc; vlan-id 0; } unit 1 { encapsulation vlan-ccc; vlan-id 1; } unit 2 { encapsulation vlan-ccc; vlan-id 2; } unit 3 { encapsulation vlan-ccc; vlan-id 3; } unit 4 { encapsulation vlan-ccc; vlan-id 4; } }
You can enable scheduling on the interfaces to achieve hierarchical class of service for traffic flowing from NNI towards UNI direction.
Configuring hierarchical class of service for VPLS Service
Supported ACX routers can be configured to provide Layer 2 VPN services to subscribers based on VPLS where the UNI port can be connected to a CE device. Subscriber network is attached to UNI logical interface at the PE router and have a VPLS instance. The same physical port can service multiple VPLS instances for various subscribers. The service provider can schedule traffic for different VPLS instances based on the SLA parameters agreed with the subscriber. You can enable hierarchical class of service per UNI logical interface representing the VPLS instance for the subscriber to achieve the functionality.
The following is a sample to configure the UNI logical interface on the PE router providing the VPLS service:
[edit interfaces] ge-0/0/1 { hierarchical-scheduler; vlan-tagging; encapsulation vlan-vpls; unit 0 { encapsulation vlan-vpls; vlan-id 0; } unit 1 { encapsulation vlan-vpls; vlan-id 1; } unit 2 { encapsulation vlan-vpls; vlan-id 2; } unit 3 { encapsulation vlan-vpls; vlan-id 3; } unit 4 { encapsulation vlan-vpls; vlan-id 4; } }
Scheduling can be enabled on the interfaces to achieve hierarchical class of service for the traffic flowing from NNI towards UNI direction.
Verifying the hierarchical class of service configurations
You can use the following CLI commands to verify the configuration:
show interfaces queue
—Shows physical interface aggregate, physical interface remaining, and logical interface traffic statistics to monitor the traffic received and transmitted. The following are some sample outputs ofshow interfaces queue
CLI command:content_copy zoom_out_mapuser@host# run show interfaces queue ge-0/0/4.2 Logical interface ge-0/0/4.2 (Index 555) (SNMP ifIndex 671) Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Burst size: 0 Queue: 0, Forwarding classes: 8q0 Queued: Packets : 1121476 7642 pps Bytes : 587885024 32237416 bps Transmitted: Packets : 594964 3160 pps Bytes : 304621568 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 1121476 7642 pps Bytes : 587885154 32237416 bps Transmitted: Packets : 594959 3160 pps Bytes : 304619008 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526517 4482 pps Total-dropped bytes : 283266146 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 1119456 7321 pps Bytes : 595127702 31122568 bps Transmitted: Packets : 274601 1500 pps Bytes : 140595712 6144000 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 844855 5821 pps Total-dropped bytes : 454531990 24978568 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 1119464 7303 pps Bytes : 595131980 31122568 bps Transmitted: Packets : 274602 1500 pps Bytes : 140596224 6144000 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 844862 5803 pps Total-dropped bytes : 454535756 24978568 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 1121476 7642 pps Bytes : 587885024 32237416 bps Transmitted: Packets : 594964 3160 pps Bytes : 304621568 12946280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 1121476 7660 pps Bytes : 587885024 32310560 bps Transmitted: Packets : 594964 3178 pps Bytes : 304621568 13019424 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 526512 4482 pps Total-dropped bytes : 283263456 19291136 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 1121476 7017 pps Bytes : 587190842 29535136 bps Transmitted: Packets : 621684 3589 pps Bytes : 318302208 14701712 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 499792 3428 pps Total-dropped bytes : 268888634 14833424 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 1121477 6481 pps Bytes : 586036910 27137704 bps Transmitted: Packets : 666066 3660 pps Bytes : 341025792 14994280 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 455411 2821 pps Total-dropped bytes : 245011118 12143424 bps Queue Buffer Usage: Reserved buffer : 0 pkts 0 bytes Shared buffer : 0 pkts 0 bytes
content_copy zoom_out_mapuser@host# run show interfaces queue ge-0/0/4 aggregate Physical interface: ge-0/0/4, Enabled, Physical link is Up Interface index: 648, SNMP ifIndex: 1763 Description: UNI side - connected to ixia 6/9 Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Queue: 0, Forwarding classes: 8q0 Queued: Packets : 16762731 33205 pps Bytes : 8738362264 139058280 bps Transmitted: Packets : 8779233 13724 pps Bytes : 4494967296 56220880 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983498 19481 pps Total-dropped bytes : 4243394968 82837400 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 52 pkts 10816 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 16762732 33237 pps Bytes : 8738359966 139190408 bps Transmitted: Packets : 8779363 13756 pps Bytes : 4495033856 56353008 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983369 19481 pps Total-dropped bytes : 4243326110 82837400 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 43 pkts 8944 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 16754769 30221 pps Bytes : 8826383526 127522040 bps Transmitted: Packets : 4052168 6369 pps Bytes : 2074710016 26095472 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 12702601 23852 pps Total-dropped bytes : 6751673510 101426568 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 24232 pkts 5040256 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 16754937 30328 pps Bytes : 8826406908 127965968 bps Transmitted: Packets : 4052173 6378 pps Bytes : 2074646336 26134456 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 12702764 23950 pps Total-dropped bytes : 6751760572 101831512 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 24205 pkts 5034640 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 16762735 33406 pps Bytes : 8738360722 139886136 bps Transmitted: Packets : 8779404 13828 pps Bytes : 4495054848 56648672 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983331 19578 pps Total-dropped bytes : 4243305874 83237464 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 46 pkts 9568 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 16762734 33285 pps Bytes : 8738359924 139389112 bps Transmitted: Packets : 8779416 13788 pps Bytes : 4495060992 56485136 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7983318 19497 pps Total-dropped bytes : 4243298932 82903976 bps Queue Buffer Usage: Reserved buffer : 32 pkts 6656 bytes Shared buffer : 52 pkts 10816 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 16762732 27688 pps Bytes : 8721917186 115931832 bps Transmitted: Packets : 9618678 12111 pps Bytes : 4924763136 49614432 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 7144054 15577 pps Total-dropped bytes : 3797154050 66317400 bps Queue Buffer Usage: Reserved buffer : 24 pkts 4992 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 16762733 26045 pps Bytes : 8710804790 108947832 bps Transmitted: Packets : 10187546 11805 pps Bytes : 5216023552 48359208 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 6575187 14240 pps Total-dropped bytes : 3494781238 60588624 bps Queue Buffer Usage: Reserved buffer : 21 pkts 4368 bytes Shared buffer : 0 pkts 0 bytes
content_copy zoom_out_mapuser@host# run show interfaces queue ge-0/0/4 remaining-traffic Physical interface: ge-0/0/4, Enabled, Physical link is Up Interface index: 648, SNMP ifIndex: 1763 Description: UNI side - connected to ixia 6/9 Forwarding classes: 16 supported, 8 in use Egress queues: 8 supported, 8 in use Queue: 0, Forwarding classes: 8q0 Queued: Packets : 77501 6106 pps Bytes : 41609646 26235344 bps Transmitted: Packets : 3206 243 pps Bytes : 1641472 999248 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 74295 5863 pps Total-dropped bytes : 39968174 25236096 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1495 pkts 310960 bytes Queue: 1, Forwarding classes: 8q1 Queued: Packets : 77489 6100 pps Bytes : 41444318 26107008 bps Transmitted: Packets : 9330 732 pps Bytes : 4776960 3002344 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 68159 5368 pps Total-dropped bytes : 36667358 23104664 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1435 pkts 298480 bytes Queue: 2, Forwarding classes: 8q2 Queued: Packets : 77485 6099 pps Bytes : 41362188 26054080 bps Transmitted: Packets : 12417 975 pps Bytes : 6357504 3996992 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 65068 5124 pps Total-dropped bytes : 35004684 22057088 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1507 pkts 313456 bytes Queue: 3, Forwarding classes: 8q3 Queued: Packets : 77547 6114 pps Bytes : 41609314 26271632 bps Transmitted: Packets : 3261 243 pps Bytes : 1646862 999248 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 74286 5871 pps Total-dropped bytes : 39962452 25272384 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1381 pkts 287248 bytes Queue: 4, Forwarding classes: 8q4 Queued: Packets : 77502 6105 pps Bytes : 41450894 26131200 bps Transmitted: Packets : 9349 732 pps Bytes : 4786688 3002344 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 68153 5373 pps Total-dropped bytes : 36664206 23128856 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1366 pkts 284128 bytes Queue: 5, Forwarding classes: 8q5 Queued: Packets : 77480 6094 pps Bytes : 41358904 26032304 bps Transmitted: Packets : 12444 975 pps Bytes : 6371328 3996992 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 65036 5119 pps Total-dropped bytes : 34987576 22035312 bps Queue Buffer Usage: Reserved buffer : 8 pkts 1664 bytes Shared buffer : 1552 pkts 322816 bytes Queue: 6, Forwarding classes: 8q6 Queued: Packets : 77970 6099 pps Bytes : 41151002 25749384 bps Transmitted: Packets : 30585 2440 pps Bytes : 15659520 9997088 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 47385 3659 pps Total-dropped bytes : 25491482 15752296 bps Queue Buffer Usage: Reserved buffer : 3 pkts 624 bytes Shared buffer : 0 pkts 0 bytes Queue: 7, Forwarding classes: 8q7 Queued: Packets : 77971 6099 pps Bytes : 41151540 25749384 bps Transmitted: Packets : 30585 2440 pps Bytes : 15659520 9997088 bps Tail-dropped packets : Not Available RL-dropped packets : 0 0 pps RL-dropped bytes : 0 0 bps Total-dropped packets: 47386 3659 pps Total-dropped bytes : 25492020 15752296 bps Queue Buffer Usage: Reserved buffer : 3 pkts 624 bytes Shared buffer : 0 pkts 0 bytes
show class-of-service packet-buffer usage
—Shows the total buffer usage of the system. The following is a sample output of theshow class-of-service packet-buffer usage
CLI command:content_copy zoom_out_mapuser@host# run show class-of-service packet-buffer usage Egress: Total Buffer Bytes : 10652.89 KB in use out of 12480.00 KB Total Buffer Pkts : 52445 in use out of 61440 Dedicated Buffer Bytes : 48.14 KB in use out of 738.16 KB Dedicated Buffer Pkts : 237 in use out of 3634 Shared Buffer Bytes : 10604.75 KB in use out of 11741.84 KB Shared Buffer Pkts : 52208 in use out of 57806
For interface sets, you can run the following commands:
show interfaces interface-set voq
—Show VOQ statistics for the interface-set.show interfaces interface-set detail
—Display detailed output for the interface set.show interfaces interface-set voq remaining-traffic
—Show remaining traffic queue statistics for the interface set.
You can use the syslog to view the log messages and error reports.