Hi Serge, You raised a good point. The behaviour in this case could be infact hardware dependent. I am testing on an MX5 (MX80 with 5G license, OS version 11.2 I think). I have not tested on other hardware platforms.
Please note that according to the doc I sent before, my interpretation is that the rate-limit command only kicks in when there is congestion with traffic from othr classes!!! This means we need to test with a lot of traffic in other queues to see the effect ( rate is capped for the class that is subject to "rate-limit" command). I only tested with one traffic source to show that I can use "unused bandwidth", and send more than the "capped rate". That behavior is the same as documented. Thanks, HP On 15/10/2012, at 3:51 AM, Serge Vautour <sergevaut...@yahoo.ca> wrote: > MPC: > -Rate-limit: Command takes but it does nothing. The queue isn't > capped and traffic can reach sub-interface or interface shaped rate. > -Exact: The result looks like a shaper. > -Shaping-Rate: Results look exactly like the "exact" command. Traffic > looks shaped. _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
