234
Setting the DCBX version
When you set the DCBX version, follow these restrictions and guidelines:
•
For DCBX to work correctly, configure the same DCBX version on the local port and peer port.
As a best practice, configure the highest version supported on both ends. IEEE Std
802.1Qaz-2011, DCBX Rev 1.01, and DCBX Rev 1.00 are in descending order.
•
After the configuration, LLDP frames sent by the local port carry information about the
configured DCBX version. The local port and peer port do not negotiate the DCBX version.
•
When the DCBX version is autonegotiated, the version IEEE Std 802.1Qaz-2011 is preferably
negotiated.
To set the DCBX version:
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
3.
Set the DCBX version.
dcbx version
{
rev100
|
rev101
|
standard
}
By default, the DCBX version
is not configured. It is
autonegotiated by the local
port and peer port.
Configuring APP parameters
The device negotiates with the server adapter by using the APP parameters to achieve the following
purposes:
•
Control the 802.1p priority values of the protocol packets that the server adapter sends.
•
Identify traffic based on the 802.1p priority values.
For example, the device can use the APP parameters to negotiate with the server adapter to set
802.1p priority 3 for all FCoE and FIP frames. When the negotiation succeeds, all FCoE and FIP
frames that the server adapter sends to the device carry the 802.1p priority 3.
Configuration restrictions and guidelines
When you configure APP parameters, follow these restrictions and guidelines:
•
An Ethernet frame header ACL identifies application protocol packets by frame type.
•
An IPv4 advanced ACL identifies application protocol packets by TCP/UDP port number.
•
DCBX Rev 1.00 identifies application protocol packets only by frame type and advertises only
TLVs with frame type 0x8906 (FCoE).
•
DCBX Rev 1.01 has the following attributes:
{
Supports identifying application protocol packets by both frame type and TCP/UDP port
number.
{
Does not restrict the frame type or TCP/UDP port number for advertising TLVs.
{
Can advertise up to 77 TLVs according to the remaining length of the current packet.
•
In a QoS policy, you can configure multiple class-behavior associations. A packet might be
configured with multiple 802.1p priority marking or mapping actions, and the one configured first
takes effect.
Configuration procedure
To configure APP parameters:
Summary of Contents for H3C S7500E-X
Page 70: ...57 ...