Converged Enhanced Ethernet Administrator’s Guide 91
53-1002163-02
DCBX interaction with other vendor devices 9
DRAFT: BROCADE CONFIDENTIAL
PFC is defined by a one-byte bitmap. Each bit position stands for a user priority. If a bit is set, the
flow control is enabled in both directions (Rx and Tx).
DCBX interaction with other vendor devices
When the Brocade FCoE hardware interacts with other vendor devices, the other vendor devices
might not have support for the same DCBX version as the Brocade FCoE hardware.
The Brocade FCoE hardware supports two DCBX versions:
CEE version (1.0.1)—Based on the CEE standard.
Pre-CEE version.
To accommodate the different DCBX versions, the Brocade FCoE hardware provides the following
options.
Auto-sense (plug and play)
This is the default. The Brocade FCoE hardware detects the version used by the link neighbor
and automatically switches between the CEE version and the pre-CEE version.
CEE version
Forces the use of the CEE version for the link (auto-sense is off).
Pre-CEE version
Forces the use of the pre-CEE version for the link (auto-sense is off).
LLDP configuration guidelines and restrictions
Follow these LLDP configuration guidelines and restrictions when configuring LLDP:
Brocade’s implementation of LLDP supports Brocade-specific TLV exchange in addition to the
standard LLDP information.
Mandatory TLVs are always advertised.
The exchange of LLD P link-level param eters is transparent to the other Layer 2 protocols. The
LLDP link-level parameters are reported by LLDP to other interested protocols.
NOTE
DCBX configuration simply involves configuring DCBX-related TLVs to be advertised. Detailed
information is provided in the “LLDP configuration and management” on page92.
Default LLDP configuration
Table 21 lists the default LLDP configuration.
TABLE 21 Default LLDP configuration
Parameter Default setting
LLDP global state Enabled
LLDP receive Enabled