Administrator Guide

Table 23. show interface DCBx detail Command Description
Field Description
Interface Interface type with chassis slot and port number.
Port-Role Configured DCBx port role: auto-upstream, auto-downstream,
config-source, or manual.
DCBx Operational Status Operational status (enabled or disabled) used to elect a
configuration source and internally propagate a DCB configuration.
The DCBx operational status is the combination of PFC and ETS
operational status.
Configuration Source Specifies whether the port serves as the DCBx configuration
source on the switch: true (yes) or false (no).
Local DCBx Compatibility mode DCBx version accepted in a DCB configuration as compatible. In
auto-upstream mode, a port can only received a DCBx version
supported on the remote peer.
Local DCBx Configured mode DCBx version configured on the port: CEE, CIN, IEEE v2.5, or Auto
(port auto-configures to use the DCBx version received from a
peer).
Peer Operating version DCBx version that the peer uses to exchange DCB parameters.
Local DCBx TLVs Transmitted Transmission status (enabled or disabled) of advertised DCB TLVs
(see TLV code at the top of the show command output).
Local DCBx Status: DCBx Operational Version DCBx version advertised in Control TLVs.
Local DCBx Status: DCBx Max Version Supported Highest DCBx version supported in Control TLVs.
Local DCBx Status: Sequence Number Sequence number transmitted in Control TLVs.
Local DCBx Status: Acknowledgment Number Acknowledgement number transmitted in Control TLVs.
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.
Performing PFC Using DSCP Bits Instead of
802.1p Bits
Priority based Flow Control (PFC) is currently supported on Dell Networking OS for tagged packets based on the packet Dot1p. In certain
data center deployments, VLAN configuration is avoided on the servers and all packets from the servers are untagged. These packets will
carry IP header and can be differentiated based on the DSCP fields they carry on the server facing switch ports. Requirement is to classify
these untagged packets from the server based on their DSCP and provide PFC treatment.
Dell Networking OS Releases 9.3(0.0) and earlier provide CLI support to specify the priorities for which PFC is enabled on each port. This
feature is applicable only for the tagged packets based on the incoming packet Dot1p and Dot1p based queue classification. This document
will discuss the configurations required to support PFC for untagged packets based on incoming packet DSCP.
Data Center Bridging (DCB)
265