Field
Description
Local DCBx Status: Protocol State
Current operational state of DCBx protocol: ACK or IN-SYNC.
Peer DCBx Status: DCBx Operational Version
DCBx version advertised in Control TLVs received from peer device.
Peer DCBx Status: DCBx Max Version Supported
Highest DCBx version supported in Control TLVs received from
peer device.
Peer DCBx Status: Sequence Number
Sequence number transmitted in Control TLVs received from peer
device.
Peer DCBx Status: Acknowledgment Number
Acknowledgement number transmitted in Control TLVs received
from peer device.
Total DCBx Frames transmitted
Number of DCBx frames sent from local port.
Total DCBx Frames received
Number of DCBx frames received from remote peer port.
Total DCBx Frame errors
Number of DCBx frames with errors received.
Total DCBx Frames unrecognized
Number of unrecognizable DCBx frames received.
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
), DCB policies applied to an interface may become invalid if you reconfigure dot1p-queue mapping. If the configured
DCB policy remains valid, the change in the dot1p-queue assignment is allowed.
NOTE:
Although, each port on the S4810, S4820T, and S5000 devices support 8 QoS queues, you can configure only 4 QoS
queues (0-3) to manage data traffic. The remaining 4 queues (4-7) are reserved for control traffic.
dot1p Value in
the Incoming
Frame
Egress Queue Assignment
0
0
1
0
2
0
3
1
288
Data Center Bridging (DCB)
Summary of Contents for S4048T-ON
Page 1: ...Dell Configuration Guide for the S4048 ON System 9 11 2 1 ...
Page 148: ...Figure 10 BFD Three Way Handshake State Changes 148 Bidirectional Forwarding Detection BFD ...
Page 251: ...Dell Control Plane Policing CoPP 251 ...
Page 363: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 363 ...
Page 511: ...Figure 64 Inspecting the LAG Configuration Link Aggregation Control Protocol LACP 511 ...
Page 558: ...Figure 84 Configuring Interfaces for MSDP 558 Multicast Source Discovery Protocol MSDP ...
Page 559: ...Figure 85 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 559 ...
Page 564: ...Figure 88 MSDP Default Peer Scenario 2 564 Multicast Source Discovery Protocol MSDP ...
Page 565: ...Figure 89 MSDP Default Peer Scenario 3 Multicast Source Discovery Protocol MSDP 565 ...
Page 841: ...Figure 115 Single and Double Tag TPID Match Service Provider Bridging 841 ...
Page 842: ...Figure 116 Single and Double Tag First byte TPID Match 842 Service Provider Bridging ...