- 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
Monitoring CoS Forwarding Classes
Purpose
Use the monitoring functionality to view the current assignment of CoS forwarding classes to queue numbers on the system.
Action
To monitor CoS forwarding classes in the CLI, enter the following CLI command:
user@switch> show class-of-service forwarding-class
Meaning
Some switches use different forwarding classes, output queues, and classifiers for unicast and multidestination (multicast, broadcast, destination lookup fail) traffic. These switches support 12 forwarding classes and output queues, eight for unicast traffic and four for multidestination traffic.
Some switches use the same forwarding classes, output queues, and classifiers for unicast and multidestination traffic. These switches support eight forwarding classes and eight output queues.
Table 1 summarizes key output fields on switches that use different forwarding classes and output queues for unicast and multidestination traffic.
Field | Values |
|---|---|
Forwarding Class | Names of forwarding classes assigned to queue numbers. By default, the following unicast forwarding classes are assigned to queues 0, 3, 4, and 7, respectively:
By default, the following multidestination forwarding class is assigned to queue 8:
|
Queue | Queue number corresponding to (mapped to) the forwarding class name. By default, four queues (0, 3, 4, and 7) are assigned to unicast forwarding classes and one queue (8) is assigned to a multidestination forwarding class:
|
No-Loss | Packet drop attribute associated with each forwarding class:
|
OCX Series switches do not support the default lossless
forwarding classes fcoe and no-loss, and do
not support the no-loss packet drop attribute used to configure lossless
forwarding classes. On OCX Series switches, do not map traffic to
the default fcoe and no-loss forwarding classes
(both of these default forwarding classes carry the no-loss packet
drop attribute), and do not configure the no-loss packet drop attribute
on forwarding classes.
Table 2 summarizes key output fields on switches that use the same forwarding classes and output queues for unicast and multidestination traffic.
Field | Values |
|---|---|
Forwarding Class | Names of forwarding classes assigned to queue numbers. By default, the following forwarding classes are assigned to queues 0, 3, 4, and 7, respectively:
|
Queue | Queue number corresponding to (mapped to) the forwarding class name. By default, four queues (0, 3, 4, and 7) are assigned to forwarding classes:
|
No-Loss | Packet drop attribute associated with each forwarding class:
|
