[j-nsp] DSCP classifier on CCC interface

Addy Mathur addy.mathur at gmail.com
Tue Mar 20 10:49:40 EDT 2012


Serge:

What platform/line-card are you trying this on?  This is possible in JUNOS
11.4 when using Trio/MPC line-cards on the MX.  See 11.4 release notes:

http://www.juniper.net/techpubs/en_US/junos11.4/information-products/topic-collections/release-notes/11.4/index.html?topic-62949.html#jd0e3519

--Addy.

On Mon, Mar 19, 2012 at 2:27 PM, Serge Vautour <sergevautour at yahoo.ca>wrote:

> Hello,
>
> Would anyone know if it's possible to apply a DSCP classifier on a CCC
> interface? Here's what I have:
>
>
> Interface:
>
> ge-1/2/1 {
>     encapsulation ethernet-ccc;
>     unit 0;
> }
>
> Routing-Instance:
>
> instance-type l2vpn;
> interface ge-1/2/1.0;
> vrf-target target:123:41;
> protocols {
>     l2vpn {
>         encapsulation-type ethernet;
>         no-control-word;
>         site Site1 {
>             site-identifier 1;
>             interface ge-1/2/1.0;
>         }
>     }
> }
>
> Class-of-Service interface:
>
> ge-1/2/1 {
>     unit 0 {
>         classifiers {
>             dscp dscp-classifier;
>         }
>     }
> }
>
>
> Class-of-service classifier:
>
> dscp dscp-classifier {
>     import default;
>     forwarding-class expedited-forwarding {
>         loss-priority low code-points [ 101000 101001 101010 101011 101100
> 101101 101110 101111 ];
>     }
> }
>
>
> Note that the L2VPN is port based. Any valid ethernet frame will go
> through.
>
>
> To test this I generate a ping and set the ToS field to 101. The
> classifier above should drive this to the EF class but it isn't.
>
>
> I'm wondering if maybe you can't use a DSCP classifier on a non-IP
> interface? Anybody tried this before? I thought I'd try this mailing list
> before opening a case.
>
> Thanks,
> Serge
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>


More information about the juniper-nsp mailing list