On (2015-06-24 16:08 +0100), Dan Peachey wrote: Hey Dan,
> class-of-service { > traffic-control-profiles { > 10M { > scheduler-map 10M_COS; > shaping-rate 10m; guaranteed-rate 10m; # add this > } > Queue State Max Guaranteed Burst Weight Priorities > Drop-Rules > Index rate rate size G E Wred > Tail > ------ ----------- ----------- ------------ ------- ------ ---------- > ---------- > 32 Configured 10000000 0 131072 320 GL EL 4 > 0 > 33 Configured 10000000 0 131072 320 GL EL 4 > 0 > 34 Configured 10000000 0 131072 26 GL EL 4 > 0 > 35 Configured 10000000 0 131072 13 GM EH 4 > 127 > 36 Configured 10000000 0 131072 1 GL EL 0 > 255 > 37 Configured 10000000 2400000 131072 320 GH EH 4 > 193 > 38 Configured 10000000 0 131072 1 GL EL 0 > 255 > 39 Configured 10000000 0 131072 1 GL EL 0 > 255 Notice how g-rate is 0 for all but the policed class, all your queues running in excess area. Setting guarantee-rate == shaping-rate. Right now the % does not mean anything, only thing that means is what is excess priority (EL => excess low, EH => excess high, all EH traffic would be drained before any EL traffic is touched). -- ++ytti _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp