Defining an Application for DCBX Application Protocol TLV Exchange

Define each application for which you want DCBX to exchange application protocol information. You can define Layer 2 and Layer 4 applications. After you define applications, you map them to IEEE 802.1p code points, and then apply the application map to the interfaces on which you want DCBX to exchange application protocol information with connected peers. (See Related Documentation for how to configure application maps and apply them to interfaces, and for an example of the entire procedure that also includes classifier configuration.)

Note:

In Junos OS Release 12.1, the FCoE application was configured by default, so you did not need to configure it in an application map. In Junos OS Release 12.2, if you want DCBX to advertise the FCoE application on an interface and you apply an application map to that interface, you must explicitly configure FCoE in the application map. You also must enable priority-based flow control (PFC) on the FCoE code point on all interfaces that you want to advertise FCoE. If you apply an application map to an interface, the interface sends DCBX TLVs only for the applications configured in the application map.

Define Layer 2 applications by mapping an application name to an EtherType. Define Layer 4 applications by mapping an application name to a protocol (TCP or UDP) and a destination port.

To define a Layer 2 application, specify the name of the application and its EtherType:
For example, to configure an application named PTP (for Precision Time Protocol) that uses the EtherType 0x88F7:
To define a Layer 4 application, specify the name of the application, its protocol (TCP or UDP), and its destination port:
For example, to configure an application named iscsi (for Internet Small Computer System Interface) that uses the protocol TCP and the destination port 3260: