[j-nsp] Rewriting customer DSCP with MPLS EXP

[Olivier Benghozi]

Hi,

I know this thread is more than one year old, but I had a not_that_far need (outbound packet 802.1p field rewrite based on DSCP, instead of internal CoS)...
Well, I've just seen that the needed feature is only available in (freshly released) (completely radioactive) 16.1 release.
https://www.juniper.net/documentation/en_US/junos16.1/topics/concept/policy-maps-overview-cos.html <https://www.juniper.net/documentation/en_US/junos16.1/topics/concept/policy-maps-overview-cos.html>
 
Not exactly similar to the byDCSPclassifying, though.

Olivier

> Le 28 mars 2015 à 17:32, Cydon Satyr <cydonsatyr at gmail.com> a écrit :
> 
> I knew it had to do something with LSI interface, just wasn't smart enough
> to follow it trough!!
> Many thanks, this worked.
> 
> One more question if you don't mind please. If instead of:
> 
> set class-of-service routing-instances <vrf> classifiers exp BA-exp     I do
> set class-of-service routing-instances <vrf> classifiers dscp BA-dscp,
> could it classify based on customer DSCP?
> 
> In other words short-pipe model, where I classify traffic on PE based on
> customer DSCP. Is this possible?
> 
> Many thanks again, I'd buy you a beer if I could :)
> 
> 
> 
> On Sat, Mar 28, 2015 at 5:03 PM, Antti Ristimäki <antti.ristimaki at csc.fi>
> wrote:
> 
>> Hi,
>> 
>>> I can't seem to understand why this is happening. The thing I see is
>>> default exp classification is this:
>>> 
>>> 
>>> run show class-of-service classifier type exp name exp-default
>>> Classifier: exp-default, Code point type: exp, Index: 10
>>>  Code point         Forwarding class                    Loss priority
>>>  000                BE                                  low
>>>  001                BE                                  high
>>>  010                REALTIME                            low
>>>  011                REALTIME                            high
>>>  100                VIDEO                               low
>>>  101                VIDEO                               high
>>>  110                CRITICAL                            low
>>>  111                CRITICAL                            high
>>> 
>>> 
>>> In default exp classifier, marking of 101 goes to VIDEO, not REALTIME.
>>> But as you can see I have the correct configuration on all
>> interfaces...or
>>> do I?
>> 
>> Just a guess: do you have vrf-table-label configured? If you have, at
>> egress PE the packet is logically received by LSI interface, so you
>> should apply your EXP classifier to those interfaces, too. This can be
>> accomplished by adding something like "set class-of-service
>> routing-instances <vrf> classifiers exp BA-exp".
>> 
>> AR
>> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp