[j-nsp] Move traffic to strict-priority-queue on MX

Mark Tinka mark.tinka at seacom.mu
Mon Dec 1 02:37:04 EST 2014


On Monday, December 01, 2014 08:46:40 AM Per Granath wrote:

> With this you are setting the forwarding-class, which is
> internal to the MX.

Well, the forwarding class will determine how his packets 
are treated on egress. But for that, we need to see his 
[class-of-service] setup to figure out if it's done right.

> If you also want to rewrite the DHCP bits in the packet
> headers, then you also need to configure 'rewrite' for
> these forwarding classes, on the egress interfaces (core
> facing in this case).
> 
> I can't remember what the default rewrite rules are, but
> I believe they do not do what you want.

On the Trio, you can remark on ingress with a firewall 
filter ("then dscp" or "then traffic-class") as the OP has 
done. But yes, remarking on egress has been typical in 
Juniper until recently.

Mark.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20141201/cdb5b6fd/attachment.sig>


More information about the juniper-nsp mailing list