- play_arrow Classifying and Rewriting Traffic
- play_arrow Using Classifiers, Forwarding Classes, and Rewrite Rules
- Understanding CoS Classifiers
- Defining CoS BA Classifiers (DSCP, DSCP IPv6, IEEE 802.1p)
- Example: Configuring Classifiers
- Monitoring CoS Classifiers
- Understanding Default CoS Scheduling and Classification
- Understanding Applying CoS Classifiers and Rewrite Rules to Interfaces
- Understanding CoS Code-Point Aliases
- Defining CoS Code-Point Aliases
- Monitoring CoS Code-Point Value Aliases
- Understanding CoS Forwarding Classes
- Defining CoS Forwarding Classes
- Example: Configuring Forwarding Classes
- Monitoring CoS Forwarding Classes
- Understanding CoS Rewrite Rules
- Defining CoS Rewrite Rules
- Troubleshooting an Unexpected Rewrite Value
- Monitoring CoS Rewrite Rules
-
- play_arrow Scheduling Traffic
- play_arrow Using Schedulers
- Understanding CoS Scheduling Behavior and Configuration Considerations
- Defining CoS Queue Schedulers for Port Scheduling
- Defining CoS Queue Scheduling Priority
- Example: Configuring Queue Scheduling Priority
- Monitoring CoS Scheduler Maps
- Understanding CoS Traffic Control Profiles
- Understanding CoS Priority Group Scheduling
- Defining CoS Traffic Control Profiles (Priority Group Scheduling)
- Example: Configuring Traffic Control Profiles (Priority Group Scheduling)
- Understanding CoS Priority Group and Queue Guaranteed Minimum Bandwidth
- Example: Configuring Minimum Guaranteed Output Bandwidth
- Understanding CoS Priority Group Shaping and Queue Shaping (Maximum Bandwidth)
- Example: Configuring Maximum Output Bandwidth
- Understanding CoS Explicit Congestion Notification
-
- play_arrow Configuration Statements and Operational Commands
Assigning CoS Components to Interfaces
After you define the following CoS components, you assign them to physical or logical interfaces. Components that you assign to physical interfaces are valid for all of the logical interfaces configured on the physical interface. Components that you assign to a logical interface are valid only for that logical interface.
Classifiers—Assign to logical interfaces; on some devices, you apply classifiers to physical Layer 3 interfaces and the classifiers are applied to all logical interfaces on the physical interface.
Congestion notification profiles—Assign only to physical interfaces.
Forwarding classes—Assign to interfaces by mapping to forwarding class sets.
Forwarding class sets—Assign only to physical interfaces.
Output traffic control profiles—Assign only to physical interfaces (with a forwarding class set).
Port schedulers—Assign only to physical interfaces on devices that support port scheduling. Associate the scheduler with a forwarding class in a scheduler map and apply the scheduler map to the physical interface.
Rewrite rules—Assign to logical interfaces; on some devices, you apply classifiers to physical Layer 3 interfaces and the classifiers are applied to all logical interfaces on the physical interface.
You can assign a CoS component to a single interface or to multiple interfaces using wildcards. You can also assign a congestion notification profile or a forwarding class set globally to all interfaces.
To assign CoS components to interfaces:
Assign a CoS component to a physical interface by associating a CoS component (for
example, a forwarding class set named be-priority-group) with an
interface:
[edit class-of-service interfaces] user@switch# set xe-0/0/7 forwarding-class-set be-priority-group
Assign a CoS component to a logical interface by associating a CoS component (for
example, a classifier named be_classifier) with a logical
interface:
[edit class-of-service interfaces] user@switch# set xe-0/0/7 unit 0 classifiers dscp be_classifier
Assign a CoS component to multiple interfaces by associating a CoS component (for
example, a rewrite rule named customup-rw) to all 10-Gigabit
Ethernet interfaces on the switch, use wildcard characters for the interface name
and logical interface (unit) number:
[edit class-of-service interfaces] user@switch# set xe-* unit * rewrite-rules ieee-802.1 customup-rw
Assign a congestion notification profile or a forwarding class set globally to all
interfaces using the set class-of-service interfaces all statement.
For example, to assign a forwarding class set named
be-priority-group to all interfaces:
[edit class-of-service interfaces] user@switch# set all forwarding-class-set be-priority-group
If there is an existing CoS configuration of any type on an interface, the global configuration is not applied to that particular interface. The global configuration is applied to all interfaces that do not have an existing CoS configuration.
For example, if you configure a rewrite rule, assign it to interfaces
xe-0/0/20.0 and xe-0/0/22.0, and then
configure a forwarding class set and apply it to all interfaces, the forwarding
class set is applied to every interface except xe-0/0/20 and
xe-0/0/22.
Wild card configuration takes precedence over interfaces all
configuration under the [edit class-of-service] hierarchy. For
example, in the following configuration:
[edit class-of-service interfaces] user@switch# set xe-* scheduler-map sch0 user@switch# set all unit 0 classifiers dscp cls
the wildcard configuration (xe-*) prevails meaning
classifiers dscp cls is not applied to any logical
interface at all. The logical interfaces will apply default classifiers only. If
you need to apply the classifier to logical interfaces as well, you must
explicitly apply the classifier to specific logical interfaces. For example:
[edit class-of-service interfaces] user@switch# set xe-0/1/1:0 unit 0 classifiers dscp cls user@switch# set xe-0/1/1:2 unit 0 classifiers dscp cls
