This object is used to provide an additional level of
priority that is required for certain queuing disciplines
and when the different queues that comprise a queue set
are serviced using a mix of queuing disciplines. This
object can be used to specify, for example, the order in
which queues will be serviced when priority queuing is
used. It also supports the ability to describe the
servicing hierarchy when a hybrid queuing scheme, such
as priority queuing coupled with weighted fair queuing,
is used.
Queue service priority is assigned such that a lower
service order value indicates a higher priority. For
example, a priority queue with a value of 1 will be
serviced (i.e., drained) before another priority queue
with a service order value of 2.
Note that multiple queues that are logically associated,
based on the queuing discipline that is being employed,
will be assigned the same service order value. Under
this scenario, other parameters that are related to the
queuing discipline determine the order of queue servicing
(e.g., queue drain size is used for 'wfq').
For example, an interface that is associated with a queue
set supporting two priority queues and three queues that
are serviced using WFQ would be modeled as follows:
Q Index Q Discipline Q Drain Size Q Service Order
22 pq(1) - 1
23 pq(1) - 2
24 wfq(3) 500 3
25 wfq(3) 350 3
26 wfq(3) 150 3
The queue set presented in this example would service
all queued traffic in queue 22 first, followed by all of
the queued traffic in queue 23. Next the queued traffic
in queues 24 through 26 would be serviced in a round
robin fashion with queue 24 receiving 50% of the available
bandwidth, queue 25 receiving 35% of the available
bandwidth and queue 26 receiving 15% of the available
bandwidth. This example is presented for expository
purposes and has been simplified accordingly.
Note that, in this example, queues 24, 25 and 26 form a
queue cluster. Members of a queue cluster are all assigned
the same ntnQosIfQueueServiceOrder as there are tightly
coupled. The ntnQosIfQueueDrainSize attribute is used to
determine the additional processing characteristics of
the individual queues in a cluster.
Parsed from file pibNtnEvol_004.mib.txt
Company: baynetworks
Module: NTN-QOS-POLICY-EVOL-PIB
Vendor: Avaya
Module: NTN-QOS-POLICY-EVOL-PIB (NTN-QOS-POLICY-EVOL-PIB.mib)
Type: TABULAR
Access: read-create
Syntax: Integer32
(
1..255 )
Automatically extracted from www.mibdepot.com
ntnQosIfQueueServiceOrder OBJECT-TYPE SYNTAX Integer32 (1..255) MAX-ACCESS read-create STATUS current DESCRIPTION "This object is used to provide an additional level of priority that is required for certain queuing disciplines and when the different queues that comprise a queue set are serviced using a mix of queuing disciplines. This object can be used to specify, for example, the order in which queues will be serviced when priority queuing is used. It also supports the ability to describe the servicing hierarchy when a hybrid queuing scheme, such as priority queuing coupled with weighted fair queuing, is used. Queue service priority is assigned such that a lower service order value indicates a higher priority. For example, a priority queue with a value of 1 will be serviced (i.e., drained) before another priority queue with a service order value of 2. Note that multiple queues that are logically associated, based on the queuing discipline that is being employed, will be assigned the same service order value. Under this scenario, other parameters that are related to the queuing discipline determine the order of queue servicing (e.g., queue drain size is used for 'wfq'). For example, an interface that is associated with a queue set supporting two priority queues and three queues that are serviced using WFQ would be modeled as follows: Q Index Q Discipline Q Drain Size Q Service Order 22 pq(1) - 1 23 pq(1) - 2 24 wfq(3) 500 3 25 wfq(3) 350 3 26 wfq(3) 150 3 The queue set presented in this example would service all queued traffic in queue 22 first, followed by all of the queued traffic in queue 23. Next the queued traffic in queues 24 through 26 would be serviced in a round robin fashion with queue 24 receiving 50% of the available bandwidth, queue 25 receiving 35% of the available bandwidth and queue 26 receiving 15% of the available bandwidth. This example is presented for expository purposes and has been simplified accordingly. Note that, in this example, queues 24, 25 and 26 form a queue cluster. Members of a queue cluster are all assigned the same ntnQosIfQueueServiceOrder as there are tightly coupled. The ntnQosIfQueueDrainSize attribute is used to determine the additional processing characteristics of the individual queues in a cluster." ::= { ntnQosIfQueueEntry 8 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.45.4.7.1.9.2.1.1 | ntnQosIfQueueId | 0 | 0 | An index that uniquely identifies an entry in the ntnQosIfQueueTable. |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.2 | ntnQosIfQueueSetId | 0 | 0 | An index that uniquely identifies a specific queue set. The queue set that is identified with this value is associated with an in… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.3 | ntnQosIfQueueIndex | 0 | 0 | An arbitrary index that uniquely identifies a specific queue within a set of queues that is identified by the ntnQosIfQueueSetId … |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.4 | ntnQosIfQueueDiscipline | 0 | 0 | This object identifies the queuing discipline that is associated with the specified queue. A value of fifo(1) indicates that the … |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.5 | ntnQosIfQueueDrainSize | 0 | 0 | The maximum number of bytes that may be drained from the queue in one cycle. The percentage of the interface bandwidth allocated… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.6 | ntnQosIfQueueAbsBandwidth | 0 | 0 | The maximum interface bandwidth that is available for consumption when servicing this queue. This bandwidth is specified in terms… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.7 | ntnQosIfQueueBandwidthAllocation | 0 | 0 | This attribute specifies whether to configure the queue for an absolute bandwidth limit or one that is relative to other queues o… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.9 | ntnQosIfQueueSize | 0 | 0 | The size of the queue in bytes. Some devices set queue size in terms of packets. These devices must calculate the queue size in… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.10 | ntnQosIfQueueStorage | 0 | 0 | The storage type for this conceptual row. Conceptual rows having the value permanent(4) need not allow write-access to any column… |
| 1.3.6.1.4.1.45.4.7.1.9.2.1.11 | ntnQosIfQueueStatus | 0 | 0 | The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Row… |