This table is used to configure queue templates. This does not mean that every entry in this table creates a queue. A queue is only created when it is used in a Queue-List and assigned to a WAN interface. This means a template created here can be the basis for any number of queues or none at all.
Example: If an entry named "Test" is created and this entry is then divided into two Queue-List objects, each of which is assigned to a different WAN interface, then the result will be two queues with name "Test", which are completely independent of one another.
The configuration of the queues and their parameters in LANconfig is done under .
- Name
- This is where the name of the queue template is entered. Other tables reference the template by using this name. The name must be unique within the table.
- Metric type
- Here the metric of the columns Commit rate and Excess rate is set.
- Commit rate
- Here you enter how much bandwidth is available to this Queue. The value is also commonly referred to as CIR (Committed Information Rate). The unit of the input is specified in the column Metric Type. The following value ranges apply:
- Percent: 1 < x < 100
- Kbit: 1 < x < 4294967295
- Mbit: 1 < x < 4294967295
- Excess rate
- Here you enter the bandwidth the Queue can use in addition to its Commit-Rate. The value is also commonly referred to as EIR (Excess Information Rate). To prevent higher-priority queues from taking the commit rate of lower-priority queues, the following concept was used:
The QoS operates in time slots, during which each queue can use its commit rate. At the end of the time slot, the unused Commit-Rate from all queues is carried over into the next time slot and used as a pool for the Excess-Rate. This pool then limits the bandwidth that can be used with the Excess-Rate. This fulfills two important aspects: Firstly, the Excess-Rate of a queue is not subtracted from another queue’s current Commit-Rate, but from the unused rate of the previous time slot. Second, the pool for the Excess-Rate is reset at the beginning of each time slot and is not added up, which means the unused Commit-Rate of a time slot can only be used in the following time slot. This prevents an accumulation, which could cause queues with a configured excess rate to starve the lower-priority queues.
Example: Two queues are configured, concatenated into a Queue-List, and assigned to a WAN interface. Queue A has a commit rate of 10 Mbps and an excess rate of 4 Mbps. Queue B has a commit rate of 5 Mbps and an excess rate of 0. If now in time slot 1 Queue A uses 9 Mbps and Queue B uses 4 Mbps, then 2 Mbps are unused rate and added to the pool of the excess rate for time slot 2. In this time slot, Queue A can then use its 10 Mbps commit rate and an additional 2 Mbps from the pool as part of its excess rate. Important is that only as much Excess-Rate can be used as the pool provides.
The unit of the input is specified in the column Metric Type. The following value ranges apply:
- Percent: 0 < x < 100
- Kbit: 0 < x < 4294967295
- Mbit: 0 < x < 4294967295
- Fallback to best effort
- This control determines what happens to packets that cannot be sent as part of the commit rate or excess rate. If Yes the packets are sent via the best-effort queue, otherwise they are discarded.
- Congestion action
- An object from the Congestion Action table is referenced here, which determines when packets are discarded because the send queues are filling up.
- DSCP tags
- The DSCP tags (Differentiated Services Code Point) to be assigned to this queue are entered here. Multiple values can be passed.
