explicitly associate a default classifier with a logical interface, you are in effect overriding
the implicit default classifier with an explicit default classifier.
NOTE: Only the IEEE 802.1p classifier is supported in Layer 2-only interfaces.
You must explicitly apply this classifier to the interface as shown in Default
IEEE 802.1p Classifier.
NOTE: Although several CoS values map to the expedited-forwarding (ef)
and assured-forwarding (af) classes, by default no resources are assigned
to these forwarding classes. All af classes other than af1x are mapped to
best-effort, because RFC 2597, Assured Forwarding PHB Group, prohibits a
node from aggregating classes.
You can apply IEEE 802.1p classifiers to interfaces that are part of VPLS routing instances.
Release History Table DescriptionRelease
Support was added for filtering on Differentiated Services Code Point (DSCP)
and forwarding class for Routing Engine sourced packets, including IS-IS
packets encapsulated in generic routing encapsulation (GRE).
13.3R7
Related
Documentation
Default IP Precedence Classifier on page 954•
• Default DSCP and DSCP IPv6 Classifiers
• Default MPLS EXP Classifier
• Default IEEE 802.1p Classifier
• Default IEEE 802.1ad Classifier
• Configuring Behavior Aggregate Classifiers
• Applying Behavior Aggregate Classifiers to Logical Interfaces
• Overview of Assigning Service Levels to Packets Based on Multiple Packet Header
Fields on page 891
• Rewriting Packet Headers to Ensure Forwarding Behavior
Default Behavior Aggregate Classification Overview in ACX Series
The software automatically assigns an implicit default IP precedence classifier to all
physical interfaces.
Other default classifiers (such as those for IEEE 802.1p bits and DSCP) require that you
explicitly associate a default classification table with a physical interface. When you
953Copyright © 2017, Juniper Networks, Inc.
Chapter 28: Configuring Behavior Aggregate Classifiers
To Next Page
Loading...
Need help?
General
