If you just want to do a sort of default classifier you can use

#set class-of-service interfaces all unit * forwarding-class be

which at least gets rid of NC queue issue you mentioned.

If you want to actually bleach customer dscp on ingress, you can do it with
MF classifier. There are several drawback, and one is that you can only
bleach it to 0 (usually good enough).

And if you require more granular ingress remark, as Mark suggested after
14.2R3.8 you can use policy-maps.

Best

Dragan

On Mon, Oct 17, 2016 at 6:01 PM, Mark Tinka <mark.ti...@seacom.mu> wrote:

>
>
> On 17/Oct/16 17:03, John Luthcinson wrote:
>
> > Hi
> >
> > What's the best way to "bleach" the possible QoS (802.1P or DSCP) bits in
> > CE facing ingress interfaces? The default classifier
> (ipprec-compatibility)
> > allows customers to transmit packets to NC queue which is very bad.
> >
> > The optimal way would be something like this:
> > - classify everything in every IFL as BE
> > - manually specify the exceptions
> >
> > set class-of-service interfaces x/y/z.a forwarding-class best-effort (for
> > every IFL/IFD (one can use *))
> > OR
> > specify FW filter with "then forwarding-class best-effort" in every IFL
> (or
> > w/ apply-groups)
> >
> > Is there a better way?
>
> If you have Trio line cards, use Policy Map:
>
> https://www.juniper.net/techpubs/en_US/junos16.1/topics/reference/
> configuration-statement/policy-map-edit-cos.html
>
> It's the easiest way to remark the traffic on ingress in Junos.
>
> Mark.
> _______________________________________________
> 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

Reply via email to