Tested working: (Example is 5 down 2 up with 1000 kbit high priority and
802.1p) I know it sounds counter intuitive that changing things like the
burst allocation or the burst rate would cause issues but we replicated
the packet loss on high priority flagged traffic in other configurations
not matching the layout I described of sustained x2 for max rate and
burst bucket size = sustained rate. I've never opened a ticket with
Cambium about it since, to be honest, dealing with the T1 support is a
nightmare and I don't feel like wasting hours being quoted a manual page
when the test date proves otherwise.
Sustained Uplink Data Rate : 2000
Sustained Downlink Data Rate : 5000
Uplink Burst Allocation : 2000
Downlink Burst Allocation : 5000
Max Burst Uplink Data Rate : 4000
Max Burst Downlink Data Rate : 10000
Hi Priority Channel : enabled
Priority Precedence : 802.1p then diffserv
Hi Priority Uplink CIR : 1000
Hi Priority Downlink CIR : 1000
Timothy Alexander
Amplex Internet
www.amplex.net
Date: Wed, 20 Apr 2016 11:42:27 -0500
From: Brian Sullivan<installe...@foxvalley.net>
Subject: Re: [AFMUG] High Priority Uplink / Downlink
Message-ID:<5717b173.6010...@foxvalley.net>
Timothy, The Sustained rate is is in kbps and the allocation is in
kbits. Could you give me an example or screenshot of your QOS (Session
Status > Configuration) settings so I can better understand?
