Reference Guide

320 | Data Center Bridging (DCB)
www.dell.com | support.dell.com
Troubleshooting PFC, ETS, and DCBx Operation
DCBx Oper Status is Down
In the show interfaces pfc | ets | dcbx output, the DCBx operational status may be down for any of the
reasons described in Table 13-9. When DCBx is down, the following values display in the show output
field for DCBx Oper status:
• PFC DCBx Oper status: Down
• ETS DCBx Oper status: Down
• DCBx Oper status: Disabled.
W
Table 13-9. Reasons why DCBx Oper Status is Down
Reason Description
Port Shutdown Port is shut down. All other reasons for DCBx inoperation, if any, are ignored.
LLDP Rx/Tx is disabled LLDP is disabled (Admin Mode set to rx or tx only) globally or on the
interface.
Waiting for Peer Waiting for peer or detected peer connection has aged out.
Multiple Peer Detected Multiple peer connections detected on the interface.
Version Conflict DCBx version on peer version is different than the local or globally
configured DCBx version.
Config-source Down Although DCBx parameters match in auto-upstream or auto-downstream port,
the configuration source (elected dynamically or CLI-configured) is down.
Unrecognized TLV received Invalid TLV length TLV has been received. In case of an invalid PFC or ETS
TLV, the error displays in the show interfaces pfc | ets output; show
interfaces dcbx
output displays PFC or ETS as down.
Admin Mode OFF (Local) Local Admin Mode is disabled.
Admin Mode OFF (Remote) Remote Admin Mode is disabled.
Waiting for ACK from Peer For a legacy DCBx version, a peer has not acknowledged the reception of a
sent packet. This reason displays only when a remote peer is willing to receive
a DCB configuration.
Error Bit set For a legacy DCBx version, a peer has sent packets with an error bit set. This
reason displays only when a remote peer is willing to receive a DCB
configuration.
Enabled with ETS Mismatch
(show interfaces dcbx output)
DCBx is enabled but an ETS validation failure error has occurred.
PFC is down
(show interfaces pfc output)
One of the following PFC-specific errors has occurred:
- No MBC support.
- Configured PFC priorities exceed maximum PFC capability limit.
- New dot1p-to-queue mapping violates the allowed system limit for PFC
Enable status per priority