- play_arrow Configuring Class of Service Components
- play_arrow Assigning Service Levels with Classifiers
- play_arrow Controlling Network Access with Traffic Policing
- Simple Filters and Policers Overview
- Two-Rate Three-Color Policer Overview
- Example: Configuring a Two-Rate Three-Color Policer
- Logical Interface (Aggregate) Policer Overview
- Two-Color Policer Configuration Overview
- Example: Configuring a Two-Color Logical Interface (Aggregate) Policer
- Guidelines for Configuring Simple Filters
- Example: Configuring and Applying a Firewall Filter for a Multifield Classifier
- play_arrow Controlling Output Queues with Forwarding Classes
- Forwarding Classes Overview
- Example: Configuring Forwarding Classes
- Example: Assigning Forwarding Classes to Output Queues
- Example: Classifying All Traffic from a Remote Device by Configuring Fixed Interface-Based Classification
- Understanding the SPC High-Priority Queue
- Example: Configuring the SPC High-Priority Queue
- Understanding Queuing and Marking of Host Outbound Traffic
- Default Routing Engine Protocol Queue Assignments
- play_arrow Altering Outgoing Packets Headers with Rewrite Rules
- play_arrow Defining Output Queue Properties with Schedulers
- Schedulers Overview
- Default Scheduler Settings
- Transmission Scheduling Overview
- Excess Bandwidth Sharing and Minimum Logical Interface Shaping
- Excess Bandwidth Sharing Proportional Rates
- Calculated Weights Mapped to Hardware Weights
- Weight Allocation with Only Shaping Rates or Unshaped Logical Interfaces
- Shared Bandwidth Among Logical Interfaces
- Example: Configuring Class-of-Service Schedulers on a Security Device
- Scheduler Buffer Size Overview
- Example: Configuring a Large Delay Buffer on a Channelized T1 Interface
- Configuring Large Delay Buffers in CoS
- Example: Configuring and Applying Scheduler Maps
- Applying Scheduler Maps and Shaping Rate to DLCIs and VLANs
- Example: Applying Scheduling and Shaping to VLANs
- play_arrow Removing Delays with Strict-Priority Queues
- play_arrow Controlling Congestion with Drop Profiles
- play_arrow Controlling Congestion with Explicit Congestion Notification
- play_arrow Controlling Congestion with Adaptive Shapers
- play_arrow Limiting Traffic Using Virtual Channels
- play_arrow Enabling Queuing for Tunnel Interfaces
- play_arrow Naming Components with Code-Point Aliases
-
- play_arrow Configuring Class of Service Scheduler Hierarchy
- play_arrow Controlling Traffic by Configuring Scheduler Hierarchy
-
- play_arrow Configuring Class of Service for IPv6
- play_arrow Configuring Class of Service for IPv6 Traffic
-
- play_arrow Configuring Class of Service for I/O Cards
- play_arrow Configuring Class of Service for I/O Cards
- PIR-Only and CIR Mode Overview
- Understanding Priority Propagation
- Understanding IOC Hardware Properties
- Understanding IOC Map Queues
- WRED on the IOC Overview
- MDRR on the IOC Overview
- CoS Support on the SRX5000 Module Port Concentrator Overview
- Example: Configuring CoS on SRX5000 Firewalls with an MPC
-
- play_arrow Configuration Statements and Operational Commands
Understanding CoS Default Settings
The Class of Service menu in J-Web allows you to configure most of the Junos OS CoS components for the IPv4 and MPLS traffic on a Juniper Networks device. You can configure forwarding classes for transmitting packets, define which packets are placed into each output queue, schedule the transmission service level for each queue, and manage congestion using a random early detection (RED) algorithm. After defining the CoS components, you must assign classifiers to the required physical and logical interfaces.
Even when you do not configure any CoS settings on your routing platform, the software performs some CoS functions to ensure that user traffic and protocol packets are forwarded with minimum delay when the network is experiencing congestion. Some default mappings are automatically applied to each logical interface that you configure. Other default mappings, such as explicit default classifiers and rewrite rules, are in operation only if you explicitly associate them with an interface.
You can display default CoS settings by running the show class-of-service operational mode command.
You configure CoS when you need to override the default packet forwarding behavior of a Juniper Networks device—especially in the three areas identified in Table 1.
Default Behavior to Override with CoS | CoS Configuration Area |
|---|---|
Packet classification—By default, the Juniper Networks device does not use behavior aggregate (BA) classifiers to classify packets. Packet classification applies to incoming traffic. | Classifiers |
Scheduling queues—By default, the Juniper Networks device has only two queues enabled. Scheduling queues apply to outgoing traffic. | Schedulers |
Packet headers—By default, the Juniper Networks device does not rewrite CoS bits in packet headers. Rewriting packet headers applies to outgoing traffic. | Rewrite rules |
