Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Applying Classifiers to Logical Interfaces

You can use interface wildcards for interface-name and logical-unit-number.

For most PICs, if you apply an IEEE 802.1p 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.

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.

In Junos OS Releases 9.6 and later, the DSCP and IPv6 DSCP classifiers are not compatible with older formats. You cannot directly replace the old classifier with the new one. You must first delete the old classifier and then apply the new one, although both steps can be done in one configuration session. Otherwise, the commit will fail.

Note: If an interface is mounted on an M Series router FPC, you can apply only the default exp classifier. If an interface is mounted on 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/L3VPN routing instances (LSI interfaces). The DSCP-based classification for MPLS packets for Layer 2 VPNs is not supported. 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. 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.

Note: If you do not apply a DSCP classifier, the default EXP classifier is applied to MPLS traffic.

• In a Layer 3 VPN (L3VPN) using an LSI routing instance.
  • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.
  • DSCP classifier configured under [edit class-of-service routing-instances] on the egress PE router.
• In VPLS using an LSI routing instance.
  • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.
  • DSCP classifier configured under [edit class-of-service routing-instances] on the egress PE router.
• In a Layer 3 VPN (L3VPN) using a VT routing instance.
  • Supported on the M120, M320, MX960, MX480, MX240, and MX80 routers.
  • DSCP classifier configured 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 configured under [edit class-of-service interfaces] on the ingress core-facing interface on the P or egress PE router.

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

Note: This is not a complete configuration.

Note: This is not a complete 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.