Home/Catalog/CISCO-CLASS-BASED-QOS-MIB

CISCO-CLASS-BASED-QOS-MIB

AI MIB Summary

The CISCO-CLASS-BASED-QOS-MIB provides read-only access to the configuration hierarchy (PolicyMaps, ClassMaps, Match Statements) and runtime statistics (packet/byte counts, drop rates, policing actions) for Cisco Modular QoS CLI (MQC) implementations. It enables the monitoring of traffic classification and enforcement mechanisms, including queuing, shaping, policing, and marking, across logical interfaces such as physical ports, sub-interfaces, Frame Relay DLCIs, and ATM virtual circuits.

Cisco Class-Based QoS MIB ********************************** Overview ********************************** This MIB provides read access to Quality of Service (QoS) configuration and statistics information for Cisco platforms that support the Modular Quality of Service Command-line Interface (Modular QoS CLI). We recommend users of this MIB to review the user documentation of MQC based QoS features. Configuration information available through this MIB includes all ClassMap, PolicyMap, Match Statements, and Feature Actions configuration parameters. The definitions of each objects mentioned above are explained in the QoS objects section. Statistics available through this MIB include summary counts/rates by traffic class before and after any configured QoS policies are enforced. In addition, detailed feature-specific statistics are available for select PolicyMap features. Contact your Cisco representative to determine on which platforms the MIB is currently supported. ********************************** QoS Acronyms ********************************** BECN: Frame Relay Backward Explicit Congestion Notification CIR : Committed Information Rate DSCP: Differentiated Service Code Point EB : Estimate Bandwidth ECN : Explicite Congestion Notification FECN: Frame Relay Forward Explicit Congestion Notification IPHC: Internet Protocol Header Compression IPSLAs: IP Service Level Agreement Technologies PIR : Peak Information Rate PREC: Precedence QoS : Quality Of Services RED : Random Early Detect SRP : Spatial Reuse Protocol WRED: Weighted Random Early Detect C3PL: Cisco Common Classification Programming Language ********************************** MIB Objects ********************************** This MIB consists of the following object groups: 1 : cbQosServicePolicy 2 : cbQosInterfacePolicy 3 : cbQosFrameRelayVCPolicy 4 : cbQosATMPVCPolicy 5 : cbQosObjects 6 : cbQosPolicyMapCfg 7 : cbQosClassMapCfg 8 : cbQosMatchStmtCfg 9 : cbQosQueueingCfg 10: cbQosREDCfg 11: cbQosREDClassCfg 12: cbQosPoliceCfg 13: cbQosTSCfg 14: cbQosSetCfg 15: cbQosClassMapStats 16: cbQosMatchStmtStats 17: cbQosPoliceStats 18: cbQosQueueingStats 19: cbQosTSStats 20: cbQosREDClassStats 21: cbQosPoliceActionCfg 22: cbQosIPHCCfg 23: cbQosIPHCStats 24: cbQosSetStats 25: cbQosPoliceColorStats 26: cbQosTableMapCfg 27: cbQosTableMapValueCfg 28: cbQosTableMapSetCfg 29: cbQosEBCfg 30: cbQosEBStats 31: cbQosMeasureIPSLACfg 32: cbQosC3plAccountCfg 33: cbQosC3plAccountStats ********************************** Definitions ********************************** A logical interface in the context of this MIB is either a main-interface, a sub-interface, a Frame Relay DLCI, an ATM virtual circuit or the control-plane on the router. The (aggregate) control-plane on the router is defined as a collection of processes running at process level on the platform (route) processor. This includes the functions related to networking control capabilities such as routing, signaling, provisioning, as well as resource and service discovery. Also includes process switched traffic on the device. The term distributed control plane, in the context of this mib, represents the control-plane functionality at the level of individual linecards. This is only applicable for the case of distributed platforms. ********************************** QoS Objects ********************************** To understand Class-Based QoS features and how to navigate the MIB tables above, the key element is to comprehend the relationships among the different QoS objects. QoS objects consist of ClassMaps, Match Statements and PolicyMaps, and each Feature Actions. Match Statement - The specific match criteria to identify packets for classification purposes. ClassMap - A user-defined traffic class that contains one or many match statements used to classify packets into different categories. Feature Action - An action is a QoS feature. Features include police, traffic-shaping, queueing, random detect and packet marking(set). After the traffic is being classified, based on the traffic classification, we can apply these action to each traffic class. PolicyMap - A user-defined policy that associates each QoS action to the user-defined traffic class (ClassMap). Service Policy - Service policy is a policymap that is being attached to a logical interface. Because a policymap can also be a part of the hierarchical structure (inside a classmap), only a policymap that is directly attached to a logical interface is considered a service policy. Each service policy is uniquely identified by an index called cbQosPolicyIndex. This number is usually identical to its cbQosObjectsIndex as a policymap. ***************************************** Runtime Instance vs Configuration objects ***************************************** Each QoS objects have 2 sets of behaviours : 1: A configuration instance - Each QoS objects has it's configuration portion of information attached to it. This information does not change whether this object is attached on multiple logical interfaces and used multiple times. We uniquely identify each QoS object with identical configuration with the same index - cbQosConfigIndex. This index is used in all configuration related tables. 2: A runtime instance - Each QoS objects has it's statistical portion of information attached to it. This information changes when this object is attached on multiple logical interfaces and used in various different places. We uniquely identify each QoS runtime object instance with an index that is unique across multiple instances of the identical object - cbQosObjectsIndex. This index is used in all statistical related tables. In summary, a QoS object has 2 indexes associated with it: cbQosConfigIndex is used to identify it's configuration, which does not change regardless of number of times and where it is being used; and cbQosObjectsIndex is used to identify it's runtime statistics, depending on which logical interface and where in a given PolicyMap hierarchy this object is used, it may have multiple unique identifiers to distinguish each unique usage (instance) of the same object. ********************************** Navigation ********************************** The recommended method of navigating through all of the MIB tables is to start by learning the cbQosServicePolicyTable and cbQosObjectsTable MIB tables. In particular, Cisco Systems recommends understanding the cbQosObjectsIndex and cbQosParentObjectsIndex of each QoS feature. The cbQosPolicyIndex and cbQosObjectsIndex are system-assigned numbers that identify each unique instance of a QoS feature. These indexes are never reused between router reboots, even when changes are made to the QoS configuration. The cbQosPolicyIndex is designed to identify the service policies attached to logical interfaces, while the cbQosObjectsIndex is designed to identify each QoS feature on a specified device. The cbQosParentObjectsIndex is designed to show the hierarchical relationship of each QoS feature. ********************************** cbQosServicePolicyTable ********************************** Accessing cbQosServicePolicyTable requires cbQosPolicyIndex. This index is a system-assigned number to uniquely identify each service policy hanging off of each logical interface. Given cbQosPolicyIndex the tables provide the type of logical interface/media type on which this policy is applied, the direction in which this policy is enforced, and the SNMP interface index and/or the entity index of the underlying interface/entity. In the case of a policy being applied on a Frame Relay DLCI, the cbQosFrDLCI gives you the Frame Relay DLCI number to which this policy is attached. In the case of policy being attached to an ATM VC, cbQosAtmVPI and cbQosAtmVCI display the VPI and VCI of the ATM interface respectively. ********************************** cbQosObjectsTable ********************************** Accessing cbQosObjectsTable requires two indexes, cbQosPolicyIndex and cbQosObjectsIndex. Given a particular service policy on a given logical interface, there could be PolicyMaps, ClassMaps, Match Statements and Feature Actions being used. Each instance of these objects is uniquely identified by cbQosObjectsIndex. Users need to decide which QoS object is interesting and use the cbQosPolicyIndex and cbQosObjectsIndex to locate the right element of interest. This tables provides cbQosObjectsType, cbQosConfigIndex, and cbQosParentObjectsIndex. To understand the relationship of cbQosObjectsIndex, cbQosParentObjectsIndex and the hierarchical relationship of the QoS objects, consider the following QoS configuration example: Interface ethernet 0/1 Input Service Policy cntlWebTraffic ClassMap http match ip http set ip precedence 5 Output Service Policy cntlSNMP_Telnet ClassMap snmp match ip snmp shape average 8000 32 32 ClassMap Telnet match ip telnet shape average 10000 32 32 Interface ethernet 0/2 Input Service Policy cntlWebTraffic ClassMap http match ip http set ip precedence 5 Output Service Policy cntlSNMP_Telnet ClassMap snmp match ip snmp shape average 8000 32 32 ClassMap Telnet match ip telnet shape average 10000 32 32 *** In Ethernet 0/1 *** Assume the router assigned a cbQosConfigIndex=1024 and cbQosObjectsIndex=1084 to Policy cntlWebTraffic. Because it is attached to an interface, it has no parent QoS object, and thus cbQosParentObjectsIndex=0. In addition, because cntlWebTraffic is also the service policy of the interface, it has a unique cbQosPolicyIndex assigned to it. In most cases, it would be the same as the cbQosObjectsIndex, which is 1084 in this case. Therefore, the indexes are: cbQosPolicyIndex = 1084 cbQosObjectsIndex = 1084 cbQosConfigIndex = 1024 Assuming the router assigned a cbQosObjectsIndex=1085 and cbQosConfigIndex=1025 to ClassMap http, it is directly being used by Policy cntlWebTraffic, and therefore the cbQosParentObjectsIndex of ClassMap http will be 1084. Assuming the router assigned a cbQosConfigIndex=1026 and cbQosObjectsIndex=1086 to match ip http, it is directly used by ClassMap http, therefore the cbQosParentObjectsIndex of match ip http will be 1085. Assuming the router assigned a cbQosConfigIndex=1027 and cbQosObjectsIndex=1087 to set ip precedence 5, it is directly used by ClassMap http, therefore the cbQosParentObjectsIndex of match ip http will be 1085. Assuming the router assigned a cbQosConfigIndex=1028 and cbQosObjectsIndex=1088 to Policy cntlSNMP_Telnet. Because it is attached to an interface, it has no parent QoS object, and thus cbQosParentObjectsIndex=0. In addition, because cntlSNMP_Telnet is also the service policy of the interface, it has a unique cbQosPolicyIndex assigned to it. In most cases, it would be the same as the cbQosObjectsIndex, which is 1088 in this case. Assuming the router assigned a cbQosConfigIndex=1029 and cbQosObjectsIndex=1089 to ClassMap snmp, it is directly being used by Policy cntlSNMP_Telnet, and therefore the cbQosParentObjectsIndex of ClassMap snmp will be 1088. Assuming the router assigned a cbQosConfigIndex=1030 and cbQosObjectsIndex=1090 to match ip snmp, it is directly used by ClassMap snmp, and therefore the cbQosParentObjectsIndex of match ip snmp will be 1089. Assuming the router assigned a cbQosConfigIndex=1031 and cbQosObjectsIndex=1091 to shape average 8000 32 32, it is directly used by ClassMap snmp, therefore the cbQosParentObjectsIndex of match ip snmp will be 1089. Assuming the router assigned a cbQosConfigIndex=1032 and cbQosObjectsIndex=1092 to ClassMap Telnet, it is directly being used by Policy cntlSNMP_Telnet, and therefore the cbQosParentObjectsIndex of ClassMap Telnet will be 1088. Assuming the router assigned a cbQosConfigIndex=1033 and cbQosObjectsIndex=1093 to match ip telnet, it is directly used by ClassMap Telnet, and therefore the cbQosParentObjectsIndex of match ip telnet will be 1092. Assuming the router assigned a cbQosConfigIndex=1034 and cbQosObjectsIndex=1094 to shape 10000 32 32, it is directly used by ClassMap telnet, therefore the cbQosParentObjectsIndex of match ip telnet will be 1092. *** In Ethernet 0/2 *** Every objects will have a unique combination of cbQosPolicyIndex and cbQosObjectsIndex, but cbQosConfigIndex will be shared across the same objects that are applied in different places. ********************************** All Config Tables ********************************** Accessing config related tables requires the same index - cbQosConfigIndex. (Per precedence based tables requires a second index, which is IP precedence value) Users should have already gone through the cbQosObjectsTable at this point and understood each cbQosConfigIndex and the corresponding QoS objects. Users can uniquely identify each QoS object defined on the router and query the entries in each stats table on a per QoS object basis. ********************************** All Stats Tables ********************************** Accessing all stats related tables requires the same 2 indexes. They are cbQosPolicyIndex and cbQosObjectsIndex. (Per precedence based tables requires a third index, which is IP precedence value) Users should have already gone through the cbQosObjectsTable at this point and understood the relationship of each cbQosPolicyIndex and cbQosObjectsIndex pair and the corresponding QoS objects. Users can uniquely identify each QoS object defined on the router and query the entries in each stats table on a per QoS object basis.
278
Objects
Active
Status
7
Dependencies

Imported Objects

Objects

278 total
Object Name
ciscoCBQosMIB
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166
RFC1155-SMI
Unknown
.1.3.6.1.4.1.9.9.166
ciscoCBQosMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1
cbQosServicePolicy
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.1
cbQosServicePolicyTable
SEQUENCE OF CbQosServicePolicyEntry
.1.3.6.1.4.1.9.9.166.1.1.1
cbQosServicePolicyEntry
CbQosServicePolicyEntry
.1.3.6.1.4.1.9.9.166.1.1.1.1
cbQosPolicyIndex
Gauge
.1.3.6.1.4.1.9.9.166.1.1.1.1.1
cbQosIfTypero
InterfaceType -- Rsyntax INTEGER { -- mainInterface(1), -- subInterface(2), -- frDLCI(3), -- atmPVC(4) -- }
.1.3.6.1.4.1.9.9.166.1.1.1.1.2
cbQosPolicyDirectionro
TrafficDirection -- Rsyntax INTEGER { -- input(1), -- output(2) -- }
.1.3.6.1.4.1.9.9.166.1.1.1.1.3
cbQosIfIndexro
InterfaceIndex -- Rsyntax INTEGER
.1.3.6.1.4.1.9.9.166.1.1.1.1.4
cbQosFrDLCIro
DlciNumber -- Rsyntax INTEGER
.1.3.6.1.4.1.9.9.166.1.1.1.1.5
cbQosAtmVPIro
Gauge
.1.3.6.1.4.1.9.9.166.1.1.1.1.6
cbQosAtmVCIro
Gauge
.1.3.6.1.4.1.9.9.166.1.1.1.1.7
cbQosInterfacePolicy
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.2
cbQosInterfacePolicyTable
SEQUENCE OF CbQosInterfacePolicyEntry
.1.3.6.1.4.1.9.9.166.1.2.1
cbQosInterfacePolicyEntry
CbQosInterfacePolicyEntry
.1.3.6.1.4.1.9.9.166.1.2.1.1
cbQosIFPolicyIndexro
Gauge
.1.3.6.1.4.1.9.9.166.1.2.1.1.1
cbQosFrameRelayVCPolicy
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.3
cbQosFrameRelayPolicyTable
SEQUENCE OF CbQosFrameRelayPolicyEntry
.1.3.6.1.4.1.9.9.166.1.3.1
cbQosFrameRelayPolicyEntry
CbQosFrameRelayPolicyEntry
.1.3.6.1.4.1.9.9.166.1.3.1.1
cbQosFRPolicyIndexro
Gauge
.1.3.6.1.4.1.9.9.166.1.3.1.1.1
cbQosATMPVCPolicy
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.4
cbQosATMPVCPolicyTable
SEQUENCE OF CbQosATMPVCPolicyEntry
.1.3.6.1.4.1.9.9.166.1.4.1
cbQosATMPVCPolicyEntry
CbQosATMPVCPolicyEntry
.1.3.6.1.4.1.9.9.166.1.4.1.1
cbQosATMPolicyIndexro
Gauge
.1.3.6.1.4.1.9.9.166.1.4.1.1.1
cbQosObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.5
cbQosObjectsTable
SEQUENCE OF CbQosObjectsEntry
.1.3.6.1.4.1.9.9.166.1.5.1
cbQosObjectsEntry
CbQosObjectsEntry
.1.3.6.1.4.1.9.9.166.1.5.1.1
cbQosObjectsIndex
Gauge
.1.3.6.1.4.1.9.9.166.1.5.1.1.1
cbQosConfigIndexro
Gauge
.1.3.6.1.4.1.9.9.166.1.5.1.1.2
cbQosObjectsTypero
QosObjectType -- Rsyntax INTEGER { -- policymap(1), -- classmap(2), -- matchStatement(3), -- queueing(4), -- randomDetect(5), -- trafficShaping(6), -- police(7), -- set(8) -- }
.1.3.6.1.4.1.9.9.166.1.5.1.1.3
cbQosParentObjectsIndexro
Gauge
.1.3.6.1.4.1.9.9.166.1.5.1.1.4
cbQosPolicyMapCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.6
cbQosPolicyMapCfgTable
SEQUENCE OF CbQosPolicyMapCfgEntry
.1.3.6.1.4.1.9.9.166.1.6.1
cbQosPolicyMapCfgEntry
CbQosPolicyMapCfgEntry
.1.3.6.1.4.1.9.9.166.1.6.1.1
cbQosPolicyMapNamero
DisplayString
.1.3.6.1.4.1.9.9.166.1.6.1.1.1
cbQosPolicyMapDescro
DisplayString
.1.3.6.1.4.1.9.9.166.1.6.1.1.2
cbQosClassMapCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.7
cbQosCMCfgTable
SEQUENCE OF CbQosCMCfgEntry
.1.3.6.1.4.1.9.9.166.1.7.1
cbQosCMCfgEntry
CbQosCMCfgEntry
.1.3.6.1.4.1.9.9.166.1.7.1.1
cbQosCMNamero
DisplayString
.1.3.6.1.4.1.9.9.166.1.7.1.1.1
cbQosCMDescro
DisplayString
.1.3.6.1.4.1.9.9.166.1.7.1.1.2
cbQosCMInforo
QosClassInfo -- Rsyntax INTEGER { -- none(1), -- matchAll(2), -- matchAny(3) -- }
.1.3.6.1.4.1.9.9.166.1.7.1.1.3
cbQosMatchStmtCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.8
cbQosMatchStmtCfgTable
SEQUENCE OF CbQosMatchStmtCfgEntry
.1.3.6.1.4.1.9.9.166.1.8.1
cbQosMatchStmtCfgEntry
CbQosMatchStmtCfgEntry
.1.3.6.1.4.1.9.9.166.1.8.1.1
cbQosMatchStmtNamero
DisplayString
.1.3.6.1.4.1.9.9.166.1.8.1.1.1
cbQosMatchStmtInforo
QosMatchInfo -- Rsyntax INTEGER { -- none(1), -- matchNot(2) -- }
.1.3.6.1.4.1.9.9.166.1.8.1.1.2
cbQosQueueingCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.9
cbQosQueueingCfgTable
SEQUENCE OF CbQosQueueingCfgEntry
.1.3.6.1.4.1.9.9.166.1.9.1
cbQosQueueingCfgEntry
CbQosQueueingCfgEntry
.1.3.6.1.4.1.9.9.166.1.9.1.1
cbQosQueueingCfgBandwidthro
INTEGER
.1.3.6.1.4.1.9.9.166.1.9.1.1.1
cbQosQueueingCfgBandwidthUnitsro
QueueingBandwidthUnits -- Rsyntax INTEGER { -- kbps(1), -- percentage(2), -- percentageRemaining(3) -- }
.1.3.6.1.4.1.9.9.166.1.9.1.1.2
cbQosQueueingCfgFlowEnabledro
TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- }
.1.3.6.1.4.1.9.9.166.1.9.1.1.3
cbQosQueueingCfgPriorityEnabledro
TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- }
.1.3.6.1.4.1.9.9.166.1.9.1.1.4
cbQosQueueingCfgAggregateQSizerodeprecated
INTEGER
.1.3.6.1.4.1.9.9.166.1.9.1.1.5
cbQosQueueingCfgIndividualQSizero
INTEGER
.1.3.6.1.4.1.9.9.166.1.9.1.1.6
cbQosQueueingCfgDynamicQNumberro
INTEGER
.1.3.6.1.4.1.9.9.166.1.9.1.1.7
cbQosQueueingCfgPrioBurstSizero
Gauge
.1.3.6.1.4.1.9.9.166.1.9.1.1.8
cbQosQueueingCfgQLimitUnitsro
CbQosQueueUnitType -- Rsyntax INTEGER { -- packets(1), -- cells(2), -- bytes(3) -- }
.1.3.6.1.4.1.9.9.166.1.9.1.1.9
cbQosQueueingCfgAggregateQLimitro
CbQosQueueDepth -- Rsyntax Gauge
.1.3.6.1.4.1.9.9.166.1.9.1.1.10
cbQosREDCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.10
cbQosREDCfgTable
SEQUENCE OF CbQosREDCfgEntry
.1.3.6.1.4.1.9.9.166.1.10.1
cbQosREDCfgEntry
CbQosREDCfgEntry
.1.3.6.1.4.1.9.9.166.1.10.1.1
cbQosREDCfgExponWeightro
INTEGER
.1.3.6.1.4.1.9.9.166.1.10.1.1.1
cbQosREDCfgMeanQsizerodeprecated
INTEGER
.1.3.6.1.4.1.9.9.166.1.10.1.1.2
cbQosREDCfgDscpPrecro
REDMechanism -- Rsyntax INTEGER { -- precedence(1), -- dscp(2) -- }
.1.3.6.1.4.1.9.9.166.1.10.1.1.3
cbQosREDCfgECNEnabledro
TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- }
.1.3.6.1.4.1.9.9.166.1.10.1.1.4
cbQosREDClassCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.11
cbQosREDClassCfgTable
SEQUENCE OF CbQosREDClassCfgEntry
.1.3.6.1.4.1.9.9.166.1.11.1
cbQosREDClassCfgEntry
CbQosREDClassCfgEntry
.1.3.6.1.4.1.9.9.166.1.11.1.1
cbQosREDValue
INTEGER
.1.3.6.1.4.1.9.9.166.1.11.1.1.1
cbQosREDCfgMinThresholdrodeprecated
INTEGER
.1.3.6.1.4.1.9.9.166.1.11.1.1.2
cbQosREDCfgMaxThresholdrodeprecated
INTEGER
.1.3.6.1.4.1.9.9.166.1.11.1.1.3
cbQosREDCfgPktDropProbro
INTEGER
.1.3.6.1.4.1.9.9.166.1.11.1.1.4
cbQosREDClassCfgThresholdUnitro
CbQosQueueUnitType -- Rsyntax INTEGER { -- packets(1), -- cells(2), -- bytes(3) -- }
.1.3.6.1.4.1.9.9.166.1.11.1.1.5
cbQosREDClassCfgMinThresholdro
CbQosQueueDepth -- Rsyntax Gauge
.1.3.6.1.4.1.9.9.166.1.11.1.1.6
cbQosREDClassCfgMaxThresholdro
CbQosQueueDepth -- Rsyntax Gauge
.1.3.6.1.4.1.9.9.166.1.11.1.1.7
cbQosPoliceCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.12
cbQosPoliceCfgTable
SEQUENCE OF CbQosPoliceCfgEntry
.1.3.6.1.4.1.9.9.166.1.12.1
cbQosPoliceCfgEntry
CbQosPoliceCfgEntry
.1.3.6.1.4.1.9.9.166.1.12.1.1
cbQosPoliceCfgRatero
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.1
cbQosPoliceCfgBurstSizero
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.2
cbQosPoliceCfgExtBurstSizero
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.3
cbQosPoliceCfgConformActionrodeprecated
PoliceAction -- Rsyntax INTEGER { -- transmit(1), -- setIpDSCP(2), -- setIpPrecedence(3), -- setQosGroup(4), -- drop(5), -- setMplsExp(6), -- setAtmClp(7), -- setFrDe(8), -- setL2Cos(9), -- setDiscardClass(10) -- }
.1.3.6.1.4.1.9.9.166.1.12.1.1.4
cbQosPoliceCfgConformSetValuerodeprecated
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.5
cbQosPoliceCfgExceedActionrodeprecated
PoliceAction -- Rsyntax INTEGER { -- transmit(1), -- setIpDSCP(2), -- setIpPrecedence(3), -- setQosGroup(4), -- drop(5), -- setMplsExp(6), -- setAtmClp(7), -- setFrDe(8), -- setL2Cos(9), -- setDiscardClass(10) -- }
.1.3.6.1.4.1.9.9.166.1.12.1.1.6
cbQosPoliceCfgExceedSetValuerodeprecated
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.7
cbQosPoliceCfgViolateActionrodeprecated
PoliceAction -- Rsyntax INTEGER { -- transmit(1), -- setIpDSCP(2), -- setIpPrecedence(3), -- setQosGroup(4), -- drop(5), -- setMplsExp(6), -- setAtmClp(7), -- setFrDe(8), -- setL2Cos(9), -- setDiscardClass(10) -- }
.1.3.6.1.4.1.9.9.166.1.12.1.1.8
cbQosPoliceCfgViolateSetValuerodeprecated
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.9
cbQosPoliceCfgPirro
Gauge
.1.3.6.1.4.1.9.9.166.1.12.1.1.10
cbQosPoliceCfgRate64ro
--?? syntax is not convertable to SMIv1 Unsigned64 -- Rsyntax Counter -- Units -- bits/second
.1.3.6.1.4.1.9.9.166.1.12.1.1.11
cbQosTSCfg
OBJECT IDENTIFIER
.1.3.6.1.4.1.9.9.166.1.13
cbQosTSCfgTable
SEQUENCE OF CbQosTSCfgEntry
.1.3.6.1.4.1.9.9.166.1.13.1
cbQosTSCfgEntry
CbQosTSCfgEntry
.1.3.6.1.4.1.9.9.166.1.13.1.1
cbQosTSCfgRatero
INTEGER
.1.3.6.1.4.1.9.9.166.1.13.1.1.1
cbQosTSCfgBurstSizero
INTEGER
.1.3.6.1.4.1.9.9.166.1.13.1.1.2
cbQosTSCfgExtBurstSizero
INTEGER
.1.3.6.1.4.1.9.9.166.1.13.1.1.3
cbQosTSCfgAdaptiveEnabledro
TruthValue -- Rsyntax INTEGER { -- true(1), -- false(2) -- }
.1.3.6.1.4.1.9.9.166.1.13.1.1.4
cbQosTSCfgAdaptiveRatero
INTEGER
.1.3.6.1.4.1.9.9.166.1.13.1.1.5
Showing 100 of 278 OID objects

CISCO-CLASS-BASED-QOS-MIB Technical Reference Overview

The CISCO-CLASS-BASED-QOS-MIB SNMP MIB module published by Cisco defines 278 managed OID objects, including 171 scalar/column metrics, 21 SNMP tables, and 0 trap/notification events. Key tabular structures include cbQosServicePolicyTable, cbQosInterfacePolicyTable, cbQosFrameRelayPolicyTable, cbQosATMPVCPolicyTable, cbQosObjectsTable, cbQosPolicyMapCfgTable.

Key OID Definitions in CISCO-CLASS-BASED-QOS-MIB

cbQosServicePolicyTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.1.1

This table describes the interfaces/media types and the policymap that are attached to it.

cbQosInterfacePolicyTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.2.1

This table describes the service polices that are attached to main and sub interfaces.

cbQosFrameRelayPolicyTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.3.1

This table describes the service polices that are attached to Frame Relay DLCIs.

cbQosATMPVCPolicyTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.4.1

This table describes the policies that are attached to a ATM PVC.

cbQosObjectsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.5.1

This table specifies QoS objects (classmap, policymap, match statements, and actions) hierarchy. This table also provide relationship between each PolicyIndex/ObjectsIndex pair and the ConfigIndex. ConfigIndex is essential for querying any configuration tables.

cbQosPolicyMapCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.6.1

This table specifies Policymap configuration information

cbQosCMCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.7.1

This table specifies ClassMap configuration information

cbQosMatchStmtCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.8.1

This table specifies ClassMap configuration information

cbQosQueueingCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.9.1

This table specifies Queueing Action configuration information

cbQosREDCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.10.1

This table specifies WRED Action configuration information

cbQosREDClassCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.11.1

This table specifies WRED Action configuration information on a per IP precedence basis.

cbQosPoliceCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.12.1

This table specifies Police Action configuration information.

cbQosPoliceActionCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.21.1

This table specifies Police Action configuration information.

cbQosTSCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.13.1

This table specifies traffic-shaping Action configuration information.

cbQosSetCfgTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.14.1

This table specifies Packet Marking Action configuration information.

cbQosCMStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.15.1

This table specifies ClassMap related Statistical information.

cbQosMatchStmtStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.16.1

This table specifies Match Statement related statistical information.

cbQosPoliceStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.17.1

This table specifies Police Action related Statistical information.

cbQosQueueingStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.18.1

This table specifies Queueing Action related Statistical information.

cbQosTSStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.19.1

This table specifies traffic-shaping Action related Statistical information.

cbQosREDClassStatsTableSEQUENCEnot-accessible
.1.3.6.1.4.1.9.9.166.1.20.1

This table specifies per Precedence WRED Action related Statistical information.

cbQosServicePolicyEntryCbQosServicePolicyEntrynot-accessible
.1.3.6.1.4.1.9.9.166.1.1.1.1

Each entry in this table describes to which a logical interface a given policymap is attached. Depending on the interface/media type, some fields may have meaningful values, and some may not. Please see each individual descriptions.

cbQosPolicyIndexGaugenot-accessible
.1.3.6.1.4.1.9.9.166.1.1.1.1.1

An arbitrary (system-assigned) index for all service policies (PolicyMap that has been attached to a given logical interface).

cbQosIfTypeInterfaceTyperead-only
.1.3.6.1.4.1.9.9.166.1.1.1.1.2

This describes the interface/media type to which this service policy is attached.

More MIBs from Cisco

Browse all CiscoMIBs →
CISCO-UNIFIED-COMPUTING-COMPUTE-MIB

The CISCO-UNIFIED-COMPUTING-COMPUTE-MIB provides SNMP-based monitoring and management of Cisco UCS compute blades, servers, and chassis components, exposing critical metrics such as CPU utilization, memory usage, thermal sensor readings, power supply status, and interface operational states. This module enables granular visibility into the health and performance of the Cisco Unified Computing System's compute subsystems for capacity planning and fault isolation.

1401 objects→
CISCO-UNIFIED-COMPUTING-STORAGE-MIB

The CISCO-UNIFIED-COMPUTING-STORAGE-MIB facilitates SNMP-based monitoring and management of storage subsystems, including Fibre Channel and iSCSI interfaces, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers. It exposes critical operational metrics such as port status, error counters, throughput statistics, and storage controller health states to enable granular visibility into the storage infrastructure.

1295 objects→
CISCO-UNIFIED-COMPUTING-VNIC-MIB

The CISCO-UNIFIED-COMPUTING-VNIC-MIB enables SNMP-based monitoring and management of Virtual Network Interface Card (vNIC) attributes, including operational status, traffic counters, and binding configurations, within the Cisco Unified Computing System (UCS) fabric interconnects and server blades.

1161 objects→
CERENT-GENERIC-MIB

SNMP MIB module

984 objects→
CISCO-UNIFIED-COMPUTING-BIOS-MIB

The CISCO-UNIFIED-COMPUTING-BIOS-MIB enables SNMP-based monitoring and configuration of BIOS-level parameters, firmware versions, and hardware initialization states within Cisco Unified Computing System (UCS) servers. It provides visibility into critical server boot diagnostics, BIOS settings, and hardware readiness indicators to facilitate low-level infrastructure management and troubleshooting.

937 objects→
CISCO-UNIFIED-COMPUTING-ETHER-MIB

The CISCO-UNIFIED-COMPUTING-ETHER-MIB provides SNMP management interfaces for monitoring Ethernet interface statistics, link states, and error counters on Cisco Unified Computing System (UCS) fabric interconnects and blade server line cards. This module enables the tracking of physical layer connectivity, port throughput, and packet error rates within the UCS Ethernet switching infrastructure.

920 objects→