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 of all FCoE frames and FIP frames to 3. If the negotiation succeeds, all the FCoE frames 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 TLVs with frame type 0x8906 (FCoE) only.
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

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create an Ethernet frame header ACL or an IPv4 advanced ACL and enter ACL view.	acl number acl-number [ name acl-name ] [ match-order { auto \| config } ]	An Ethernet frame header ACL number is in the range of 4000 to 4999. An IPv4 advanced ACL number is in the range of 3000 to 3999. DCBX Rev 1.00 supports only Ethernet frame header ACLs. DCBX Rev 1.01 and IEEE Std 802.1Qaz-2011 support both Ethernet frame header ACLs and IPv4 advanced ACLs.
3. Create a rule for the ACL.	For the Ethernet frame header ACL:rule [ rule-id ] permit type protocol-type ffff For the IPv4 advanced ACL:rule [ rule-id ] permit { tcp \| udp } destination-port eq port	Create rules according to the type of the ACL previously created.
4. Return to system view.	quit	N/A
5. Create a class, specify the operator of the class as OR, and enter class view.	traffic classifier classifier-name operator or	N/A
6. Use the specified ACL as the match criterion of the class.	if-match acl acl-number	N/A
7. Return to system view.	quit	N/A
8. Create a traffic behavior and enter traffic behavior view.	traffic behavior behavior-name	N/A
9. Configure the behavior to mark packets with an 802.1p priority.	remark dot1p 8021p	N/A
10. Return to system view.	quit	N/A
11. Create a QoS policy and enter QoS policy view.	qos policy policy-name	N/A
12. Associate the class with the traffic behavior in the QoS policy, and apply the association to DCBX.	classifier classifier-name behavior behavior-name mode dcbx	N/A
13. Return to system view.	quit	N/A
14. Apply the QoS policy.	(Method 1) To the outgoing traffic of all ports:qos apply policy policy-name global outbound (Method 2) To the outgoing traffic of a Layer 2 Ethernet interface: Enter Layer 2 Ethernet interface view:interface interface-type interface-number Apply the QoS policy to the outgoing traffic:qos apply policy policy-name outbound	Configurations made in system view take effect on all ports. Configurations made in Layer 2 Ethernet interface view take effect on the interface.

For more information about the acl, rule, traffic classifier, if-match, traffic behavior, remark dot1p, qos policy, classifier behavior, qos apply policy global, and qos apply policy commands, see ACL and QoS Command Reference.

prev	up	next
Enabling LLDP and DCBX TLV advertising	home	Configuring ETS parameters