Re: [j-nsp] DSCP classifier on CCC interface
pbit based classifiers work fine, I've used them before. The problem is the
traffic will be untagged and therefore I wanted to use DSCP/ToS. I found a
similar reference in the 11.2 release notes for DPC cards. It's not ideal but
at least I know why it doesn't work.
Thanks -Serge
From: Leigh Porter
To: Addy Mathur ; Serge Vautour
Cc: "juniper-nsp@puck.nether.net"
Sent: Tuesday, March 20, 2012 1:59:41 PM
Subject: RE: [j-nsp] DSCP classifier on CCC interface
"Therefore, you do not have to depend on the underlying Layer 2 QoS support."
So it sounds as though is the layer 2 QoS field is there you can use that.
--
Leigh
> -Original Message-
> From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-
> boun...@puck.nether.net] On Behalf Of Addy Mathur
> Sent: 20 March 2012 14:58
> To: Serge Vautour
> Cc: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] DSCP classifier on CCC interface
>
> 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
> 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 10 ];
> > }
> > }
> >
> >
> > 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@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> __
> This email has been scanned by the Symantec Email Security.cloud
> service.
> For more information please visit http://www.symanteccloud.com
> __
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] DSCP classifier on CCC interface
"Therefore, you do not have to depend on the underlying Layer 2 QoS support."
So it sounds as though is the layer 2 QoS field is there you can use that.
--
Leigh
> -Original Message-
> From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-
> boun...@puck.nether.net] On Behalf Of Addy Mathur
> Sent: 20 March 2012 14:58
> To: Serge Vautour
> Cc: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] DSCP classifier on CCC interface
>
> 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
> 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 10 ];
> > }
> > }
> >
> >
> > 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@puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> __
> This email has been scanned by the Symantec Email Security.cloud
> service.
> For more information please visit http://www.symanteccloud.com
> __
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] DSCP classifier on CCC interface
Hello,
I was testing this on a DPC card in an MX960. That link helps. It's not the
news I wanted to hear but it helps.
Thanks,
Serge
From: Addy Mathur
To: Serge Vautour
Cc: "juniper-nsp@puck.nether.net"
Sent: Tuesday, March 20, 2012 11:49:40 AM
Subject: Re: [j-nsp] DSCP classifier on CCC interface
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 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 10 ];
> }
> }
>
>
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] DSCP classifier on CCC interface
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 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 10 ];
> }
> }
>
>
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] DSCP classifier on CCC interface
Did you try setting the 802.1p field and classifying based on that?
I'm about to do this also, but since this is a layer 2 service then you are
right, I don't think the IP header will be looked at. But I expect that it will
look at 802.1p and use that for QoS classification.
--
Leigh
> -Original Message-
> From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-
> boun...@puck.nether.net] On Behalf Of Serge Vautour
> Sent: 19 March 2012 18:32
> To: juniper-nsp@puck.nether.net
> Subject: [j-nsp] DSCP classifier on CCC interface
>
> 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 10 ];
> }
> }
>
>
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> __
> This email has been scanned by the Symantec Email Security.cloud
> service.
> For more information please visit http://www.symanteccloud.com
> __
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] DSCP classifier on CCC interface
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 10 ];
}
}
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@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
