SummaryIn the Exinda, burt priority dictates which policy gets available bandwidth in the environment in what order. It can be seen that on occasion, this burst priority does not work.
OverviewPolicies, in general, have a 'guarnateed bandwidth' and a 'max (burst) bandwidth'. This means that when a pipe is completely saturated, each policy will be given a certain amount of bandwidth (their guaranteed). When a pipe is not saturated and there is bandwidth available, a policy will take as much as possible, up to its defined max bandwidth. When more than one policy requests more bandwidth, the order in which they get bandwidth from the available resources is determined by 'burst priority'.
The burst priority is a scale from 1-9, where low numbers are actually higher priorities and high numbers are lower priorities. As a result, a burst priority of '1' is the highest possible priority and insinuates that any policy that has that burst priority will take available bandwidth first. When multiple policies are requesting available bandwidth, the Exinda looks at the burst priority and will deal it out in the order of ascending burst priority (ie 1, then 2, then so on). As a result, those low numbers should be given to bandwidth users like audio/video or applications that require low jitter or latency.
However in some occasions, it is seen that traffic will ignore burst priorities.