Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring EXP-Based Traffic Classification for VPLS

date_range 23-Nov-23

You can enable EXP classification on traffic entering core facing VPLS LSI interfaces on a VPLS routing instance by configuring either a logical tunnel interface (lt-) or the no-tunnel-services statement. By configuring either of these, a default EXP classifier is enabled on every core facing interface that includes family mpls in its configuration. This feature works on MX Series routers and EX Series switches only. You can configure an EXP classifier explicitly at the [edit class-of-service] hierarchy level. For more information about EXP classifiers, see the Class of Service User Guide (Routers and EX9200 Switches).

To enable EXP classification on traffic entering core facing VPLS LSI interfaces on a VPLS routing instance, include the no-tunnel-services statement:

content_copy zoom_out_map

You can include this statement at the following hierarchy levels:

  • [edit routing-instances routing-instance-name protocols vpls]

  • [edit logical-systems logical-system-name routing-instances routing-instance-name protocols vpls]

footer-navigation