With those settings your burst is doing nothing really. Kind of a waste of the power of canopy burst in my opinion. Is there a reason you are purposely trying to not give any burst to your clients??
-Sean On Sat, Jan 14, 2017 at 4:38 PM Timothy Alexander <[email protected]> wrote: > We've fought with QoS setting quite a bit. Once issue we found is that the > burst buffer can cause issues if not configured correctly in situations > customer using 100% of bandwidth. We use 2x uplink and downlink rate and > limits if 1x uplink and downlink limit. The issue cambium says is due to > how burst buckets refill and allegedly improved in latest firmware but have > not yet tested it. > > I'd encourage you, whatever you try, test and verify it. We found our > quite a few times we thought "this is working" to find an ap not configured > right, a backhaul without qos setup right or just something that works > differently then we would expect. > > Tim > Amplex Internet > > > Example overrides below for a 10 down 2 up plan with 500kbit high cap good > for about 4 simultaneous calls. > > priorityPrecedence:1 > hiPriorityChannel:1 > hiPriorityDownlinkCIR:500 > hiPriorityUplinkCIR:500 > upLnkDataRate:2500 > upLnkMaxBurstDataRate:5000 > upLnkLimit:2500 > dwnLnkDataRate:10500 > dwnLnkMaxBurstDataRate:21000 > dwnLnkLimit:10500 >
