Reference Guide

DCBX configuration notes
● To exchange link-level configurations in a converged network, DCBX is a prerequisite for using DCB features, such as PFC
and ETS. DCBX is also deployed in topologies that support lossless operation for FCoE or iSCSI traffic. In these scenarios, all
network devices must be DCBX-enabled so that DCBX is enabled end-to-end.
● DCBX uses LLDP to advertise and automatically negotiate the administrative state and PFC/ETS configuration with directly
connected DCB peers. If you disable LLDP on an interface, DCBX cannot run. Enable LLDP on all DCBX ports,
● DCBX is disabled at a global level by default. Enable DCBX globally on a switch to activate the exchange of DCBX TLV
messages with PFC, ETS, and iSCSI configurations.
● DCBX is enabled by default on OS10 interfaces. You can manually reconfigure DCBX settings on a per-interface basis. For
example, you can disable DCBX on an interface (no lldp tlv-select dcbxp command) or change the DCBX version
(dcbx version command).
● For DCBX to be operational, DCBX must be enabled at both the global and interface levels. If the show lldp dcbx
interface command returns the message DCBX feature not enabled, DCBX is not enabled at both levels.
● OS10 supports DCBX versions: CEE and IEEE2.5.
● By default, DCBX advertises all TLVs—PFC, ETS Recommendation, ETS Configuration, DCBXP, and basic TLVs.
● A DCBX-enabled port operates in a manual role by default. The port operates only with user-configured settings and does
not auto-configure with DCB settings received from a DCBX peer. When you enable DCBX, the port advertises its PFC and
ETS configurations to peer devices but does not accept external, or propagate internal, DCB configurations.
● DCBX detects misconfiguration on a peer device when DCB features are not compatibly configured with the local
switch. Misconfiguration detection is feature-specific because some DCB features support asymmetric (non-identical)
configurations.
Configure DCBX
DCBX allows data center devices to advertise and exchange configuration settings with directly connected peers using LLDP.
LLDP is enabled by default.
To ensure the consistent and efficient operation of a converged data center network, DCBX detects peer misconfiguration.
DCBX is disabled at a global level and enabled at an interface level by default. For DCBX to be operational, DCBX must be
enabled at both the global and interface levels. You can manually reconfigure DCBX settings or disable DCBX on a per-interface
basis.
1. Configure the DCBX version used on a port in INTERFACE mode.
dcbx version {auto | cee | ieee}
● auto — Automatically selects the DCBX version based on the peer response (default).
● cee — Sets the DCBX version to CEE.
● ieee — Sets the DCBX version to IEEE 802.1Qaz.
2. (Optional) A DCBX-enabled port advertises all TLVs by default. If PFC or ETS TLVs are disabled, enter the command in
INTERFACE mode to re-enable PFC or ETS TLV advertisements.
dcbx tlv-select {ets-conf | ets-reco | pfc}
● ets-conf — Enables ETS configuration TLVs.
● ets-reco — Enables ETS recommendation TLVs.
● pfc — Enables PFC TLVs.
3. (Optional) DCBX is enabled on a port by default. If DCBX is disabled, enable it in INTERFACE mode.
lldp tlv-select dcbxp
4. Return to CONFIGURATION mode.
exit
5. Enable DCBX on all switch ports in CONFIGURATION mode to activate the exchange of DCBX TLV messages with PFC,
ETS, and iSCSI configurations.
dcbx enable
718
Converged data center services