CISCO-QUEUE-MIB
The CISCO-QUEUE-MIB provides SNMP access to monitor and configure interface queuing parameters, including queue depth, drop statistics, and scheduling configurations, specifically on Cisco IOS and IOS-XE devices. This module enables granular visibility into traffic shaping, policing, and congestion management mechanisms to diagnose packet loss and optimize Quality of Service (QoS) performance.
Imported Objects
Objects
25 total| Object Name |
|---|
ciscoQueueMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37 |
SNMPv2-SMI-v1 Unknown .1.3.6.1.4.1.9.9.37 |
ciscoQueueObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.1 |
cQIfTableThis 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. SEQUENCE OF CQIfEntry .1.3.6.1.4.1.9.9.37.1.1 |
cQIfEntryA list of queue attributes for an interface. CQIfEntry .1.3.6.1.4.1.9.9.37.1.1.1 |
cQIfQTypeThe 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.ro CQAlgorithm -- Rsyntax INTEGER { -- fifo(1), -- priority(2), -- custom(3), -- weightedFair(4) -- } .1.3.6.1.4.1.9.9.37.1.1.1.1 |
cQIfTxLimitThe 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.ro Integer32 .1.3.6.1.4.1.9.9.37.1.1.1.2 |
cQIfSubqueuesThe number of sub-queues of which the hold queue is built.
This is a constant for each value of cQIfQType.ro Integer32 .1.3.6.1.4.1.9.9.37.1.1.1.3 |
cQStatsTableThis table contains statistical objects that for the
sub-queues of a Cisco Interface. SEQUENCE OF CQStatsEntry .1.3.6.1.4.1.9.9.37.1.2 |
cQStatsEntryA list of sub-queue attributes for an interface. CQStatsEntry .1.3.6.1.4.1.9.9.37.1.2.1 |
cQStatsQNumberThe 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. Integer32 .1.3.6.1.4.1.9.9.37.1.2.1.1 |
cQStatsDepthThe number of messages in the sub-queue.ro Gauge32 .1.3.6.1.4.1.9.9.37.1.2.1.2 |
cQStatsMaxDepthThe maximum number of messages permitted in the sub-queue.ro Integer32 .1.3.6.1.4.1.9.9.37.1.2.1.3 |
cQStatsDiscardsThe number of messages discarded from this queue since restart
by reason of enqueue at a time that cQStatsDepth >= cQStatsMaxDepth.ro Counter32 .1.3.6.1.4.1.9.9.37.1.2.1.4 |
cQRotationTableThis table describes the rotation of Custom Queuing on an
Interface. SEQUENCE OF CQRotationEntry .1.3.6.1.4.1.9.9.37.1.3 |
cQRotationEntryCustom Queuing sub-queue attributes for an interface. CQRotationEntry .1.3.6.1.4.1.9.9.37.1.3.1 |
cQRotationOctetsThe number of octets which may be transmitted from a custom
queuing sub-queue before it must yield to another queue.ro Integer32 .1.3.6.1.4.1.9.9.37.1.3.1.1 |
ciscoQueueTraps OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.2 |
ciscoQueueConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3 |
cQCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.1 |
cQCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.1.1 |
cQGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.2 |
cQIfGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.2.1 |
cQStatsGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.2.2 |
cQRotationGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.37.3.2.3 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.