Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Applying Behavior Aggregate Classifiers to Logical Interfaces

This topic describes how to apply behavior aggregate (BA) classifiers to logical interfaces.

When you apply BA classifiers to a logical interface, you can use interface wildcards for the interface-name and logical-unit-number.

For most PICs, if you apply an IEEE 802.1 classifier to a logical interface, you cannot apply non-IEEE classifiers to other logical interfaces on the same physical interface. This restriction does not apply to Gigabit Ethernet IQ2 PICs.

There are some restrictions on applying multiple BA classifiers to a single logical interface. Table 1 shows the supported combinations. In this table, the OSE PICs refer to the 10-port 10-Gigabit OSE PICs.

Table 1: Logical Interface Classifier Combinations

Classifier Combinations

Gigabit Ethernet IQ2 PICs

OSE PICs

Other PICs on M320, MX Series, T Series routers and on EX Series Switches

Other M Series with Regular FPCs

Other M Series with Enhanced FPCs

dscp and inet-precedence

No

No

No

No

No

dscp-ipv6 and (dscp | inet-precedence)

Yes

Yes

Yes

No

No

exp and ieee 802.1

Yes

Yes

No

No

No

ieee 802.1 and (dscp | dscp-ipv6 | exp | inet-precedence)

Yes

Yes

No

No

Yes

exp and (dscp | dscp-ipv6 | inet-precedence)

Yes

Yes

Yes

No

Yes

For Gigabit Ethernet IQ2 and 10-port 10-Gigabit Oversubscribed Ethernet (OSE) interfaces, family-specific classifiers take precedence over IEEE 802.1p BA classifiers. For example, if you configure a logical interface to use both an MPLS EXP and an IEEE 802.1p classifier, the EXP classifier takes precedence. MPLS-labeled packets are evaluated by the EXP classifier, and all other packets are evaluated by the IEEE 802.1p classifier. The same is true about other classifiers when combined with IEEE 802.1p classifiers on the same logical interface.

Note:

For an interface on an M Series FPC, you can apply only the default exp classifier. For an enhanced FPC, you can create a new exp classifier and apply it to an interface.

On MX960, MX480, MX240, MX80, M120, and M320 routers and EX Series switches with Enhanced Type III FPCs only, you can configure user-defined DSCP-based BA classification for MPLS interfaces (this feature is not available for IQE PICs or on MX Series routers and EX Series switches when ingress queuing is used) or VPLS or Layer 3 VPN routing instances (LSI interfaces). The DSCP-based classification for MPLS packets for Layer 2 VPNs is not supported.

Note:

If you do not apply a DSCP classifier, the default EXP classifier is applied to MPLS traffic. At times you might need to maintain the original classifier of the incoming packet, where you neither want to configure a custom classifier for the interface nor accept the default classifier, which would override the original classifier. In that case, on MX Series devices only, you can apply the no-default option for the interface. For example:

You can apply DSCP classification for MPLS traffic in the following usage scenarios:

  • In a Layer 3 VPN using a label-switched interface (LSI) routing instance.

    • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.

    • DSCP classifier applied under [edit class-of-service routing-instances] on the egress provider edge (PE) router.

  • In VPLS using an LSI routing instance.

    • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.

    • DSCP classifier applied under [edit class-of-service routing-instances] on the egress PE router.

  • In a Layer 3 VPN using a virtual tunnel (VT) routing instance.

    • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.

    • DSCP classifier applied under [edit class-of-service interfaces] on the core-facing interface on the egress PE router.

  • In VPLS using the VT routing instance.

  • MPLS forwarding.

    • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers (not supported on IQE and MX when ingress queuing is enabled).

    • DSCP classifier applied under [edit class-of-service interfaces] on the ingress core-facing interface on the provider (P) or egress PE router.

MPLS forwarding when the label stacking is greater than 2 is not supported.

You can apply BA classifiers to a routing instance or a logical interface, depending on where you want to classify the packets:

  • To classify MPLS packets on the routing instance at the egress PE, include the dscp or dscp-ipv6 statements at the [edit class-of-service routing-instances routing-instance-name classifiers] hierarchy level. For details, see Applying MPLS EXP Classifiers to Routing Instances.

  • To classify MPLS packets at the core-facing interface, apply the classifier at the [edit class-of-service interface interface-name unit unit-name classifiers (dscp | dscp-ipv6) classifier-name family mpls] hierarchy level. The following procedure describes this method.

In the following example, you define a DSCP classifier for IPv4 named dscp-ipv4-classifier and a corresponding IPv6 DSCP classifier for the fc-af11-class forwarding class. You then apply the IPv4 classifier to MPLS traffic and the IPv6 classifier to Internet traffic on interface ge-2/0/3.0 or apply the same classifier to both MPLS and IP traffic on interface ge-2/2/0. This example shows both of these methods.

  1. Define the IPv4 classifier.
  2. Define the IPv6 classifier.
  3. (Optional) Apply the IPv4 classifier to MPLS traffic and the IPv6 classifier to Internet traffic on interface ge-2/0/3.0.
  4. Confirm the configuration.
  5. (Optional) Apply the same classifier, named dscp-mpls-and-inet, to both MPLS and IP traffic on interface ge-2/2/0.
  6. Confirm the configuration.
Note:

This is not a complete configuration.

Note:

You can apply DSCP and DSCP IPv6 classifiers to explicit null MPLS packets. The family mpls statement works the same on both explicit null and non-null MPLS labels.

Related Documentation