CISCO-QUEUE-MIB: View SNMP OID List / Download MIB

VENDOR: CISCO


 Home MIB: CISCO-QUEUE-MIB
Download as:   
SNMPv2-CONF, IF-MIB, SNMPv2-SMI, CISCO-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 ciscoQueueMIB 1.3.6.1.4.1.9.9.37
This is the MIB module for objects used to manage interface queuing in Cisco devices.
       ciscoQueueObjects 1.3.6.1.4.1.9.9.37.1
           cQIfTable 1.3.6.1.4.1.9.9.37.1.1 no-access
This table contains objects that describe the queues on a Cisco Interface. 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 or equivalent. This table parallels the ifTable, and indicates the type of queuing in use on the interface, number of queues, and similar parameters.
               cQIfEntry 1.3.6.1.4.1.9.9.37.1.1.1 no-access
A list of queue attributes for an interface.
                   cQIfQType 1.3.6.1.4.1.9.9.37.1.1.1.1 cqalgorithm read-only
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.
                   cQIfTxLimit 1.3.6.1.4.1.9.9.37.1.1.1.2 integer32 read-only
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.
                   cQIfSubqueues 1.3.6.1.4.1.9.9.37.1.1.1.3 integer32 read-only
The number of sub-queues of which the hold queue is built. This is a constant for each value of cQIfQType.
           cQStatsTable 1.3.6.1.4.1.9.9.37.1.2 no-access
This table contains statistical objects that for the sub-queues of a Cisco Interface.
               cQStatsEntry 1.3.6.1.4.1.9.9.37.1.2.1 no-access
A list of sub-queue attributes for an interface.
                   cQStatsQNumber 1.3.6.1.4.1.9.9.37.1.2.1.1 integer32 no-access
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 access list. In Weighted Fair Queuing, it is the queue number associated with the traffic stream (conversation) identified.
                   cQStatsDepth 1.3.6.1.4.1.9.9.37.1.2.1.2 gauge32 read-only
The number of messages in the sub-queue.
                   cQStatsMaxDepth 1.3.6.1.4.1.9.9.37.1.2.1.3 integer32 read-only
The maximum number of messages permitted in the sub-queue.
                   cQStatsDiscards 1.3.6.1.4.1.9.9.37.1.2.1.4 counter32 read-only
The number of messages discarded from this queue since restart by reason of enqueue at a time that cQStatsDepth >= cQStatsMaxDepth.
           cQRotationTable 1.3.6.1.4.1.9.9.37.1.3 no-access
This table describes the rotation of Custom Queuing on an Interface.
               cQRotationEntry 1.3.6.1.4.1.9.9.37.1.3.1 no-access
Custom Queuing sub-queue attributes for an interface.
                   cQRotationOctets 1.3.6.1.4.1.9.9.37.1.3.1.1 integer32 read-only
The number of octets which may be transmitted from a custom queuing sub-queue before it must yield to another queue.
       ciscoQueueTraps 1.3.6.1.4.1.9.9.37.2
       ciscoQueueConformance 1.3.6.1.4.1.9.9.37.3
           cQCompliances 1.3.6.1.4.1.9.9.37.3.1
               cQCompliance 1.3.6.1.4.1.9.9.37.3.1.1
The core compliance statement for all queued interfaces.
           cQGroups 1.3.6.1.4.1.9.9.37.3.2
               cQIfGroup 1.3.6.1.4.1.9.9.37.3.2.1
The configuration of queuing on the interface. Interface Queuing statistics (ifOutQDepth and ifOutDiscards) are kept in the interface table.
               cQStatsGroup 1.3.6.1.4.1.9.9.37.3.2.2
The statistics for individual queues in the interface queuing system.
               cQRotationGroup 1.3.6.1.4.1.9.9.37.3.2.3
The Custom Queuing queue rotation weights.