- play_arrow Weighted Random Early Detection (WRED) and Explicit Congestion Notification (ECN)
- play_arrow WRED and Drop Profiles
- play_arrow Explicit Congestion Notification (ECN)
-
- play_arrow CoS Queue Schedulers, Traffic Control Profiles, and Hierarchical Port Scheduling (ETS)
- play_arrow Queue Schedulers and Scheduling Priority
- Understanding Default CoS Scheduling and Classification
- Understanding CoS Scheduling Behavior and Configuration Considerations
- Understanding CoS Output Queue Schedulers
- Defining CoS Queue Schedulers
- Example: Configuring Queue Schedulers
- Defining CoS Queue Scheduling Priority
- Example: Configuring Queue Scheduling Priority
- Monitoring CoS Scheduler Maps
- play_arrow Port Scheduling and Shaping
- play_arrow Troubleshooting Egress Bandwidth Issues
- play_arrow Traffic Control Profiles and Priority Group Scheduling
- Understanding CoS Traffic Control Profiles
- Understanding CoS Priority Group Scheduling
- Understanding CoS Virtual Output Queues (VOQs)
- 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
- play_arrow Hierarchical Port Scheduling (ETS)
-
- play_arrow Data Center Bridging and Lossless FCoE
- play_arrow Data Center Bridging
- Understanding DCB Features and Requirements
- Understanding DCBX
- Configuring the DCBX Mode
- Configuring DCBX Autonegotiation
- Understanding DCBX Application Protocol TLV Exchange
- Defining an Application for DCBX Application Protocol TLV Exchange
- Configuring an Application Map for DCBX Application Protocol TLV Exchange
- Applying an Application Map to an Interface for DCBX Application Protocol TLV Exchange
- Example: Configuring DCBX Application Protocol TLV Exchange
- play_arrow Lossless FCoE
- Example: Configuring CoS PFC for FCoE Traffic
- Example: Configuring CoS for FCoE Transit Switch Traffic Across an MC-LAG
- Example: Configuring CoS Using ELS for FCoE Transit Switch Traffic Across an MC-LAG
- Example: Configuring Lossless FCoE Traffic When the Converged Ethernet Network Does Not Use IEEE 802.1p Priority 3 for FCoE Traffic (FCoE Transit Switch)
- Example: Configuring Two or More Lossless FCoE Priorities on the Same FCoE Transit Switch Interface
- Example: Configuring Two or More Lossless FCoE IEEE 802.1p Priorities on Different FCoE Transit Switch Interfaces
- Example: Configuring Lossless IEEE 802.1p Priorities on Ethernet Interfaces for Multiple Applications (FCoE and iSCSI)
- Troubleshooting Dropped FCoE Traffic
-
- play_arrow CoS Buffers and the Shared Buffer Pool
- play_arrow CoS Buffers Overview
- play_arrow Shared Buffer Pool Examples
- Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-Effort Unicast Traffic
- Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Best-Effort Traffic on Links with Ethernet PAUSE Enabled
- Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Multicast Traffic
- Example: Recommended Configuration of the Shared Buffer Pool for Networks with Mostly Lossless Traffic
-
- play_arrow CoS on EVPN VXLANs
- 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 only to logical interfaces; on some switches, you can 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.
Note:OCX Series switches and NFX250 Network Services platform do not support congestion notification profiles.
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 switches 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 only to logical interfaces; on some switches, you can 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 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
.