- play_arrow Basic CoS Configuration
- play_arrow CoS Overview
- play_arrow Junos OS EZQoS and J-Web
- play_arrow CoS on Interfaces
- play_arrow CoS Code-Point Aliases
- play_arrow CoS Classifiers
- Understanding CoS Classifiers
- Defining CoS Classifiers (CLI Procedure)
- Defining CoS Classifiers (J-Web Procedure)
- Example: Configuring Multidestination (Multicast, Broadcast, DLF) Classifiers
- Configuring and Applying IEEE 802.1ad Classifiers
- Change the Default Queuing and Marking of Host Outbound Traffic
- Monitoring CoS Classifiers
- Troubleshooting a CoS Classifier Configuration for a TCAM Space Error
- play_arrow CoS Rewrite
- Understanding CoS Rewrite Rules
- Defining CoS Rewrite Rules (CLI Procedure)
- Defining CoS Rewrite Rules (J-Web Procedure)
- 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
- Host Outbound Traffic IEEE802.1p Rewrite
- Monitoring CoS Rewrite Rules
- play_arrow Forwarding Classes
- play_arrow Flow Control
- play_arrow CoS Queue Schedulers and Scheduler Maps
-
- play_arrow Congestion Management, Tail Drop Profiles, Queue Shaping, and Explicit Congestion Notification (ECN)
- play_arrow Congestion Management
- play_arrow Tail Drop Profiles
- play_arrow Queue Shaping
- play_arrow Explicit Congestion Notification (ECN)
-
- play_arrow Configuration Statements and Operational Commands
ON THIS PAGE
Configuring CoS on an MPLS Provider Edge Switch Using Circuit Cross-Connect
You can use class of service (CoS) within MPLS networks to prioritize certain types of traffic during periods of congestion. This topic describes configuring CoS components on a provider edge (PE) switch that is using MPLS over circuit-cross connect (CCC).
If you are using MPLS over CCC, you can use only one DSCP or IP precedence classifier and only one IEEE 802.1p classifier on the CCC interfaces.
This procedure is for creating a custom DSCP classifier and a custom EXP rewrite rule on the ingress PE. It also includes enabling a policer on the label-switched path (LSP) of the ingress PE to ensure that the amount of traffic forwarded through the LSP never exceeds the requested bandwidth allocation.
This topic includes:
Configuring an LSP Policer
To configure an LSP policer:
You can also configure schedulers and shapers as needed. See Defining CoS Schedulers and Scheduler Maps (CLI Procedure).