This table contains objects that describe the queues on a
An interface queue is modeled as a collection of one or more
secondary queues that feed into a device's hardware queue. The
hardware queue has a maximum depth set by the MCI tx-queue-limit
command or equivalent. The secondary queues (also known as the
'hold queue') have maximum depths set by the hold-queue command
This table parallels the ifTable, and indicates the type of
queuing in use on the interface, number of queues, and similar
The type of queuing used in the Hold Queue.
First In First Out Queuing implies that the interface always
transmits messages in the order that they are received.
Priority Queuing sorts messages out by the use of access lists.
Messages in a higher priority queue are always sent in
preference to messages in a lower priority queue.
Custom Queuing sorts messages out by the use of access lists.
Sub-queues are selected in round robin order as either the
sub-queue is drained or a given number of octets is moved from
the sub-queue to the transmission queue.
Weighted Fair Queuing sorts messages by 'conversation', which
is source-destination pair of addresses and sockets or ports,
as defined by the network layer protocol. Messages are removed
from queues in a sequence that gives each conversation a
proportion of the available bandwidth.
The maximum number of messages placed into the hardware
transmission queue. This is a first come first serve queue, fed
by the hold queue. If the hold queue contains information,
this queue is presumably full.
The number of the queue within the queue set.
In FIFO queuing, this value is always 2.
In Priority Queuing, it corresponds to the various priorities:
high = 0
medium = 1
normal = 2
low = 3
In Custom Queuing, it is the queue number referenced in the
In Weighted Fair Queuing, it is the queue number associated
with the traffic stream (conversation) identified.