Hello, Yes I've seen and confirmed this behavior a while back as well. If you ask I'm sure you'll be told this is not a bug and would require a feature request to change. See: http://www.juniper.net/documentation/en_US/junos14.2/topics/reference/general/hw-cos-default-re-queues-reference-cos-config-guide.html "For all protocol packets sent to queue 3 over a VLAN-taggedinterface, the software sets the 802.1p bits to 110. However, whenprotocol packets such as BFD are handled by the Packet ForwardingEngine, the software sets the 802.1p bits to 000." As you can see on top of putting all packets in queue 3, the pbits aren't even marked correctly :( Serge From: Huan Pham <drie.huanp...@gmail.com> To: "juniper-nsp@puck.nether.net" <juniper-nsp@puck.nether.net> Sent: Thursday, May 14, 2015 9:22 PM Subject: [j-nsp] Distributed PPM and LACP always goes into Queue 3. host-outbound-traffic knob has no effect -- bug? Hi list,
I've tested in the lab and confirm that distributed PPM (e.g. one hop BFD) and LACP on MX does not honour host-outbound-traffic class of service nor outbound RE-reclassificaiton filter. This traffic always gets into queue 3. Depending on your design, this behaviour could be a problem, especially if your queue 3 is not designed for critical traffic. Is is a bug? Is there any way to move this control traffic to a different queue? Thanks very much in advance. Huan _______________________________________________ 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
