Re: [j-nsp] DSCP field not matched

On Mon, 1 Jun 2020 at 10:23, james list wrote: > Can you share why EX4650 would do the job and EX4300 cannot? Do you have a > reference on juniper.com? Flexible filter allows you to set a bit offset and a value, i.e. you can match anything you want as long as it is in a predictable offset, like

Re: [j-nsp] DSCP field not matched

Hi ytti Can you share why EX4650 would do the job and EX4300 cannot? Do you have a reference on juniper.com? I am not sure what you mean with flexible filter, can you share an example? Cheers James Il Lun 1 Giu 2020, 08:23 Saku Ytti ha scritto: > On Sun, 31 May 2020 at 22:51, james list wrot

Re: [j-nsp] DSCP field not matched

On Sun, 31 May 2020 at 22:51, james list wrote: > It seems EX4300 is not able to intercept family MPLS dscp field. > > Any idea ? Pretty sure you need another device, like EX4650 with a flexible filter or run 802.1Q for classification. You have implied ether-type 0x800 there, but even if you cha

[j-nsp] DSCP field not matched

Dear experts I’ve two EX4300 (17.3R3-S3.3) connecting a WAN link and running macsec over the WAN link, behind these EX4300 and on top to this link we’ve MX104 running MPLS traffic which pass through. Since I’d like to run QoS on this WAN link, I see that EX4300 do not matches dscp nor ip-preceden