Qos Dot1P Traffic Classification And Queue Assignment - Dell Z9500 Configuration Manual

Field
Peer Operating version
Local DCBx TLVs Transmitted
Local DCBx Status: DCBx Operational Version
Local DCBx Status: DCBx Max Version Supported
Local DCBx Status: Sequence Number
Local DCBx Status: Acknowledgment Number
Local DCBx Status: Protocol State
Peer DCBx Status: DCBx Operational Version
Peer DCBx Status: DCBx Max Version Supported
Peer DCBx Status: Sequence Number
Peer DCBx Status: Acknowledgment Number
Total DCBx Frames transmitted
Total DCBx Frames received
Total DCBx Frame errors
Total DCBx Frames unrecognized
QoS dot1p Traffic Classification and Queue
Assignment
The following section describes QoS dot1P traffic classification and assignments.
DCB supports PFC, ETS, and DCBx to handle converged Ethernet traffic that is assigned to an egress queue according to the
following QoS methods:
Honor dot1p You can honor dot1p priorities in ingress traffic at the port or global switch level (refer to Default dot1p to
Queue Mapping) using the service-class dynamic dot1p command in INTERFACE configuration
mode.
Layer 2 class maps You can use dot1p priorities to classify traffic in a class map and apply a service policy to an ingress port
to map traffic to egress queues.
NOTE: Dell Networking does not recommend mapping all ingress traffic to a single queue when using PFC and ETS.
However, Dell Networking does recommend using Ingress traffic classification using the service-class dynamic
dot1p command (honor dot1p) on all DCB-enabled interfaces. If you use L2 class maps to map dot1p priority traffic to
egress queues, take into account the default dot1p-queue assignments in the following table and the maximum number of
two lossless queues supported on a port (refer to
Although Dell Networking OS allows you to change the default dot1p priority-queue assignments (refer to
Priorities for Incoming
mapping. If the configured DCB policy remains valid, the change in the dot1p-queue assignment is allowed.
Traffic), DCB policies applied to an interface may become invalid if you reconfigure dot1p-queue
Description
DCBx version that the peer uses to exchange DCB
parameters.
Transmission status (enabled or disabled) of advertised DCB
TLVs (see TLV code at the top of the show command output).
DCBx version advertised in Control TLVs.
Highest DCBx version supported in Control TLVs.
Sequence number transmitted in Control TLVs.
Acknowledgement number transmitted in Control TLVs.
Current operational state of DCBx protocol: ACK or IN-SYNC.
DCBx version advertised in Control TLVs received from peer
device.
Highest DCBx version supported in Control TLVs received
from peer device.
Sequence number transmitted in Control TLVs received from
peer device.
Acknowledgement number transmitted in Control TLVs
received from peer device.
Number of DCBx frames sent from local port.
Number of DCBx frames received from remote peer port.
Number of DCBx frames with errors received.
Number of unrecognizable DCBx frames received.
Configuring Lossless Queues).
Setting dot1p
Data Center Bridging (DCB) 266