Hello, We use egress shapers on our Juniper MX. They uses a default burst size that are set automatically based on the size of the shaper. So far, these defaults have served us well. We have notice that some downstream devices that perform rate conversion can't seem to buffer the bursts properly. Ex: -> Traffic flow Start - 1G - DeviceA -1G - MX with 80M shaper - 1G - DeviceB - 100M - End
The setup above works fine when DeviceB is connected at 1G on both interfaces. Likewise, it works fine when Start-DeviceA is also 100M. With the exact setup above, when DeviceB does 1G to 100M conversion, it can't seem to handle the bursts of data handed out by the MX and drops traffic. Configuring the MX burst size to 0 (actual lowest value possible is 1 Byte) seems to solve the problem: no more drops by DeviceB. Is setting the shaper burst size to 0 a good idea? Are there any consequences to doing this? Thanks,Serge _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
