Radwin RADWIN 2000 D+, User Manual

Page: 170 / 229

RADWIN 2000 D+ User Manual Release 3.6.00 16 ‐ 3
Assigning Queue Priorities Chapter 16
If you un ‐ check a queue, it will be disabled for the link. It will not prevent the Slave ODU from
configuring it as “live”. The purpose behind this is to avoid the necessity of reconfiguring QoS
for the Slave ODU, should the queue be reinstated.
16.3.2 Assigning Queue Priorities
Four mechanisms are available to control queue performance:
• Strict ‐ An over ‐ the ‐ air packet is loaded first with data from Real Tome queue (see
Figure 16 ‐ 2 ), and then from the remaining queues in order. If there is too much data for
the first queue, it will “starve” the lower queues and so on.
• Weight ‐ One solution to such “starvation” is to weight input flow to the four queues.
This could still lead to wasted resources. If in the example below, the actual traffic is all
Near Real Time, only 20% will be allocated to Near real time and the rest will be held up.
• Maximum Information Rate (MIR) ‐ This is a simple throttle mechanism, which suffers
from a drawback similar to the previous case.
• Time to Live (TTL) in ms ‐ This device is use to reduce re ‐ transmits of real time data (such
as voice or viewed video).