CHAPTER 11
Configuring Class of Service and Firewall
Filters in VPLS
Configuring EXP-Based Traffic Classification for VPLS
Related
Documentation
Configuring Firewall Filters and Policers for VPLS
Copyright © 2016, Juniper Networks, Inc.
Configuring EXP-Based Traffic Classification for VPLS on page 85
Configuring Firewall Filters and Policers for VPLS on page 85
Firewall Filter Match Conditions for VPLS Traffic on page 90
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 (
statement. By configuring either of these, a default EXP classifier is
no-tunnel-services
enabled on every core facing interface that includes
feature works on MX Series routers and EX Series switches only. You can configure an
EXP classifier explicitly at the
about EXP classifiers, see the Class of Service Feature Guide for Routing Devices.
To enable EXP classification on traffic entering core facing VPLS LSI interfaces on a VPLS
routing instance, include the
no-tunnel-services;
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]
Configuring Firewall Filters and Policers for VPLS on page 85
Firewall Filter Match Conditions for VPLS Traffic on page 90
You can configure both firewall filters and policers for VPLS. Firewall filters allow you to
filter packets based on their components and to perform an action on packets that match
family mpls
hierarchy level. For more information
[edit class-of-service]
statement:
no-tunnel-services
) or the
lt-
in its configuration. This
85
Need help?
Do you have a question about the EX9200 and is the answer not in the manual?
Questions and answers