OID reference

qosIfQueueServiceOrder

1.3.6.1.4.1.45.4.2.1.1.2.1.9

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 prior…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.45.4.2.1.1.2.1 (qosIfQueueEntry)
Node code
9
Node name
qosIfQueueServiceOrder
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.45.4.2.1.1.2.1.9
URN notation
urn:oid:1.3.6.1.4.1.45.4.2.1.1.2.1.9
Type
OBJECT-TYPE
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 45 4 2 1 1 2 1 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) qosPolicyGenPibClasses(1) qosIfParameters(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) qosPolicyGenPibClasses(1) qosIfParameters(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) qosPolicyGenPibClasses(1) bnCsConfRowEntry(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) qosPolicyGenPibClasses(1) bnCsConfRowEntry(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) bnCsConfTable(1) qosIfParameters(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) bnCsConfTable(1) qosIfParameters(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) bnCsConfTable(1) bnCsConfRowEntry(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) qosPolicyIpPib(2) bnCsConfTable(1) bnCsConfRowEntry(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) qosPolicyGenPibClasses(1) qosIfParameters(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) qosPolicyGenPibClasses(1) qosIfParameters(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) qosPolicyGenPibClasses(1) bnCsConfRowEntry(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) qosPolicyGenPibClasses(1) bnCsConfRowEntry(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) bnCsConfTable(1) qosIfParameters(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) bnCsConfTable(1) qosIfParameters(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) bnCsConfTable(1) bnCsConfRowEntry(1) qosIfQueueTable(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) synoptics(45) policy(4) bnCsConfig(2) bnCsConfTable(1) bnCsConfRowEntry(1) bnCsConfType(2) qosIfQueueEntry(1) qosIfQueueServiceOrder(9)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/45/4/2/1/1/2/1/9
  • /ISO/Identified-Organization/6/1/4/1/45/4/2/1/1/2/1/9
  • /ISO/3/6/1/4/1/45/4/2/1/1/2/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/qosPolicyGenPibClasses/qosIfParameters/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/qosPolicyGenPibClasses/qosIfParameters/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/qosPolicyGenPibClasses/bnCsConfRowEntry/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/qosPolicyGenPibClasses/bnCsConfRowEntry/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/bnCsConfTable/qosIfParameters/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/bnCsConfTable/qosIfParameters/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/bnCsConfTable/bnCsConfRowEntry/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/qosPolicyIpPib/bnCsConfTable/bnCsConfRowEntry/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/qosPolicyGenPibClasses/qosIfParameters/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/qosPolicyGenPibClasses/qosIfParameters/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/qosPolicyGenPibClasses/bnCsConfRowEntry/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/qosPolicyGenPibClasses/bnCsConfRowEntry/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/bnCsConfTable/qosIfParameters/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/bnCsConfTable/qosIfParameters/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/bnCsConfTable/bnCsConfRowEntry/qosIfQueueTable/qosIfQueueEntry/qosIfQueueServiceOrder
  • /iso/identified-organization/dod/internet/private/enterprise/synoptics/policy/bnCsConfig/bnCsConfTable/bnCsConfRowEntry/bnCsConfType/qosIfQueueEntry/qosIfQueueServiceOrder
  • Additional combinations skipped.

SNMP properties

Value type
QosInterfaceQueueCount
Maximum access defined by MIB
read-create
Status in MIB
current

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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 qosIfQueueServiceOrder as there are tightly
coupled. The qosIfQueueDrainSize attribute is used to
determine the additional processing characteristics of
the individual queues in a cluster.
Sources for this description

Circitor

Parsed from QOS-POLICY-IP-PIB.mib · QOS-POLICY-IP-PIB

Source file: Download QOS-POLICY-IP-PIB.mib · Publisher's file

Vendor MIB copy from the Netdisco archive.

Source file: Download QOS-POLICY-IP-PIB · Publisher's file

Vendor MIB copy from the Observium Community archive. Nortel support.

Related source files and packages:

Source file: Download QOS-POLICY-IP-PIB.mib

Browse all files from Circitor

Historical records

Additional source information

Information from OID Repository
Vendor: SynOptics
Module: QOS-POLICY-IP-PIB

[Automatically extracted from oidview.com]
Information from MIBdepot
qosIfQueueServiceOrder OBJECT-TYPE
    SYNTAX         QosInterfaceQueueCount
    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 qosIfQueueServiceOrder as there are tightly
        coupled. The qosIfQueueDrainSize attribute is used to 
        determine the additional processing characteristics of 
        the individual queues in a cluster."

    ::= { qosIfQueueEntry 9 }
Information from Circitor
qosIfQueueServiceOrder OBJECT-TYPE
    SYNTAX         QosInterfaceQueueCount
    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 qosIfQueueServiceOrder as there are tightly
        coupled. The qosIfQueueDrainSize attribute is used to 
        determine the additional processing characteristics of 
        the individual queues in a cluster."

    ::= { qosIfQueueEntry 9 }

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.45)

Perkins David

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.45.4.2.1.1.2.1.1 qosIfQueueId00 An index that uniquely identifies this row in the table,
i.e., this PRI.
1.3.6.1.4.1.45.4.2.1.1.2.1.2 qosIfQueueSetId00 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.2.1.1.2.1.3 qosIfQueueIndex00 An arbitrary index that uniquely identifies a specific
queue within a set of queues that is identified by the
qosIfQueueSetId val…
1.3.6.1.4.1.45.4.2.1.1.2.1.4 qosIfQueueGenDiscipline00 This object identifies the queuing discipline that is
associated with the specified queue. Several general
purpose and well-known…
1.3.6.1.4.1.45.4.2.1.1.2.1.5 qosIfQueueExtDiscipline00 This object identifies the queuing discipline that is
associated with the specified queue. This attribute
provides a means throu…
1.3.6.1.4.1.45.4.2.1.1.2.1.6 qosIfQueueDrainSize00 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.2.1.1.2.1.7 qosIfQueueAbsBandwidth00 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.2.1.1.2.1.8 qosIfQueueBandwidthAllocation00 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.2.1.1.2.1.10 qosIfQueueSize00 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.2.1.1.2.1.11 qosIfQueueStorageType00 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.2.1.1.2.1.12 qosIfQueueStatus00 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
…