Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

DSCP Classification for VPLS

You can perform DSCP classification for IPv4 packets on Ethernet interfaces that are part of a VPLS routing instance on the ingress PE router.

To perform DSCP classification for IPv4 packets on Ethernet interfaces that are part of a VPLS routing instance on the ingress PE router, you must ensure the following:

  • The correct encapsulation statement based on PIC type is configured for the interface

  • The DSCP classifier is defined (default is allowed) at the [edit class-of-service classifiers] hierarchy level

  • The defined DSCP classifier is applied to the interface

  • The interface is included in the VPLS routing instance on the ingress of the PE router

A VPLS routing instance configured with the no-tunnel-services option has a default MPLS EXP classifier applied to the LSI for all VPLS packets coming from the remote VPLS PE. You can modify this default classifier.

On routing devices with eight queues, the default classification applied to no-tunnel-services VPLS packets are shown in Table 1.

Table 1: Default VPLS Classifiers

MPLS Label EXP Bits

Forwarding Class/Queue

000

0

001

1

010

2

011

3

100

4

101

5

110

6

111

7
Note:

Forwarding class to queue number mapping is not always one-to-one. Forwarding classes and queues are only the same when default forwarding-class-to-queue mapping is in effect. For more information about configuring forwarding class and queues, see Configuring a Custom Forwarding Class for Each Queue.

VPLS filters and policers act on an L2 frame that includes the MAC header (after the application of any VLAN rewrite or other rules), but does not include the cyclical redundancy check (CRC) field.

Note:

On MX Series routers, if you apply a counter in a firewall for egress MPLS or VPLS packets with the EXP bits set to 0, the counter does not tally these packets.

Related Documentation