259
Step Command
Remarks
4.
Enable PFC for the specified
802.1p priorities.
priority-flow-control no-drop
dot1p
dot1p-list
By default, PFC is disabled for all
802.1p priorities.
H3C recommends that you enable
PFC for the 802.1p priority of
FCoE traffic. If you enable PFC for
multiple 802.1p priorities, packet
loss might occur during periods of
congestion.
5.
Configure the interface to trust
the 802.1p priority carried in
packets.
qos trust dot1p
By default, the port priority of the
incoming port is trusted.
For more information about the
priority-flow-control
and
priority-flow-control no-drop dot1p
commands,
see
Interface Command Reference
.
Configuring the DCBX version
When the device is connected to a DCBX-enabled peer device, the following apply:
•
If the peer device does not support autonegotiation, the device will change its DCBX version to
match that on the peer device.
•
If the peer device supports autonegotiation and also uses the standard version as the initial version
for negotiation, the standard version will be the negotiated result.
•
If the peer device supports autonegotiation and uses a different DCBX version as the initial version
for negotiation, the standard version or the initial version the peer device uses will be the negotiated
result.
When the negotiated result is not the expected one, you can configure the expected DCBX version.
You can view the DCBX version in use through the
Oper version
field of the
DCBX Control subTLV info
part in the output from the
display lldp local-information
command.
Configuration prerequisites
Before you configure the DCBX version, complete the following tasks:
•
Enable LLDP globally and configure the interface to advertise DCBX TLVs.
•
Configure the APP parameters, ETS parameters, or PFC parameters to be advertised on the
interface.
Configuration procedure
Step Command Remarks
1.
Enter system view.
system-view
N/A
2.
Enter Layer 2 Ethernet
interface view.
interface
interface-type
interface-number
N/A