Dell N1100-ON Reference Manual page 1133

The indirect mapping between the 802.1p priorities and the associated Traffic
Class Group mapping is advertised by DCBX as part of ETS TLVs. For this
indirect mapping to be valid, the following parameters need to be configured
in addition to the configuration of the TCGs.
1 Configure 802.1p priority to CoS mapping for the ingress ports.
2 Enable Trust mode on the ingress ports to trust the 802.1p priority present
in the frames.
ETS TLVs use DCBX Asymmetric attribute exchange mechanism to
exchange ETS information between the peers. In this exchange, each peer
device sends its ETS configuration via the "configuration" ETS TLV and
recommended ETS settings for the peer using the "recommend" ETS TLV.
Both the configuration and recommendation ETS TLVs are implemented for
Dell EMC Networking switches.
The peer ETS TLVs are stored in the DCBX database and are accessible using
show commands.
The Application Priority TLV is accepted from auto-upstream devices and
propagated to auto-downstream devices. In addition, if iSCSI CoS is enabled,
an additional entry in the Application Priority TLV is added as discussed in
the iSCSI section.
Data Center Bridging Exchange Protocol Main Objective
The DCBX protocol implementation conforms to the IEEE 802.1Qaz
specification with some exceptions. To be interoperable with legacy industry
implementations of DCBX protocol, a hybrid model is used to support both
the IEEE version of DCBX and legacy DCBX versions. The hybrid version of
the DCBX conforms to all aspects of the legacy standards to the degree
necessary to support interoperability with a wide variety of FCoE capable
switches.
The main objective of DCBX is to perform the following operations:
• Discovery of DCB capability in a peer
DCBX is used to learn about the capabilities of the peer device. It is a
means to determine if the peer device supports a particular feature such as
PFC.
• DCB feature misconfiguration detection
Data Center Technology Commands
1133