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 new and unique 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.
Parsed from file CISCO-CLASS-BASED-QOS-MIB.mib
Module: CISCO-CLASS-BASED-QOS-MIB
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 new and unique 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.
Parsed from file CISCO-CLASS-BASED-QOS-MIB.my.txt
Company: None
Module: CISCO-CLASS-BASED-QOS-MIB
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.
ciscoCBQosMIB MODULE-IDENTITY LAST-UPDATED "200904240000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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 new and unique 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." REVISION "200904240000Z" DESCRIPTION "- Added cbQosSetCfgFrDe to hold the Fr-De marking configuration value in cbQosSetCfgTable. - Updated the optional groups of ciscocbQosMIBComplianceRev7 with cbQosSetCfgFrDeGroup. - Added MODULE-COMPLIANCE ciscocbQosMIBComplianceRev8." REVISION "200901260000Z" DESCRIPTION "Added account feature in QosObjectType." REVISION "200811200000Z" DESCRIPTION "Added cbQosC3plAccountCfgGroup and cbQosC3plAccountStatsGroup." REVISION "200806170000Z" DESCRIPTION "-Added ratioRemaining in QueueingBandwidthUnits -Added l2CosInner in SetFeatureType -Added cbQosQueueingCfgPriorityLevel in cbQosQueueingCfgTable -Added cbQosSetCfgL2CosInnerValue in cbQosSetCfgTable -Added in cbQosREDClassCfgTable cbQosREDClassCfgMaxThresholdUnit, cbQosREDClassCfgMinThresholdUnit -Added cbQosQueueingClassCfgTable - Added following OBJECT-GROUPs cbQosQueueingCfgGroupRev2 cbQosSetCfgL2Group cbQosQueueingClassCfgGroup cbQosPoliceCfgGroupRev3 - Added MODULE-COMPLIANCE cisco cbQosMIBComplianceRev6" REVISION "200710090000Z" DESCRIPTION "1. Added cbQosTSCfgRate64 to cbQosTSCfgTable to support shaping rates greater than that fit in the range defined for cbQosTSCfgRate. 2. Created cbQosTSCfgExtGroup. 3. Created new compliance module ciscocbQosMIBComplianceRev5 which deprecates ciscocbQosMIBComplianceRev4." REVISION "200708300000Z" DESCRIPTION "Added 'setL2CosInner' value to PoliceAction TC." REVISION "200707100000Z" DESCRIPTION "Added following enumerations to RedMechanism TC: mplsExp redDefault redUserDefault" REVISION "200409200000Z" DESCRIPTION "1. Added vlan-port as a new InterfaceType. 2. Created cbQosServicePolicyExtGroup." REVISION "200404120000Z" DESCRIPTION "Added support for Estimate Bandwidth and its Corvil implementation. Corvil's algorithm generates the estimated bandwidth for a class of traffic from knowledge of the QoS targets such as delay and drop, and the observed traffic behavior." REVISION "200307240000Z" DESCRIPTION "Added setIpDscpTunnel, setIpPrecedenceTunnel to the PoliceAction TC. Added srpPriority, frFecnBecn, ipDscpTunnel, ipPrecedenceTunnel to the SetFeatureType TC. Added l2Cos, atmClp to the REDMechanism TC. Added cps to the CbQosRateType TC. Added CbQosTMSetType TC. Added cbQosQueueingCfgAggrQLimitTime to the cbQosQueueingCfgTable. Added cbQosREDClassCfgMinThresholdTime, cbQosREDClassCfgMaxThresholdTime to the cbQosREDClassCfgTable. Added cbQosPoliceCfgCellRate, cbQosPoliceCfgCellPir, cbQosPoliceCfgBurstCell, cbQosPoliceCfgExtBurstCell, cbQosPoliceCfgBurstTime, cbQosPoliceCfgExtBurstTime, cbQosPoliceCfgCdvt, cbQosPoliceCfgConformColor, cbQosPoliceCfgExceedColor to the cbQosPoliceCfgTable. Added cbQosTSCfgBurstTime, cbQosTSCfgExtBurstTime to the cbQosTSCfgTable. Added cbQosSetCfgSrpPriority, cbQosSetCfgFrFecnBecn to the cbQosSetCfgTable. Added cbQosSetStatsTable. Added cbQosPoliceColorStatsTable. Added cbQosTableMapCfgTable. Added cbQosTableMapValueCfgTable. Added cbQosTableMapSetCfgTable." REVISION "200306090000Z" DESCRIPTION "Added controlPlane to the InterfaceType TC. Added cbQosEntityIndex to the cbQosServicePolicyTable." REVISION "200301210000Z" DESCRIPTION "Added compression(9) in QosObjectType TC for IPHC; Added setMplsExpTopMost(11) in PoliceAction TC for POLICE; Added mplsExpTopMost(8) in SetFeatureType TC for SET; Added discardClass(13) in REDMechanism TC for WRED; Added CbQosRateType TC for POLICE and SHAPE; Added IPHCOption TC for IPHC; Added cbQosPoliceCfgRateType, cbQosPoliceCfgPercentRateValue, cbQosPoliceCfgPercentPirValue for POLICE; Added cbQosTSCfgRateType, cbQosTSCfgPercentRateValue for SHAPE; Added cbQosSetCfgMplsExpTopMostValue for SET; Added cbQosIPHCCfg and cbQosIPHCStats tables for IPHC." REVISION "200212030000Z" DESCRIPTION "Added new cbQosPoliceCfgRate64 to cbQosPoliceCfgEntry table to support policing rates greater than fit in the range defined for cbQosPoliceCfgRate" REVISION "200207240000Z" DESCRIPTION "Added support for ECN; Pir policing; multiple police actions; added MPLS-EXP/ATM-CLP/DR-DE/ L2Cos/DiscardClass marking in police action; added MPLS-EXP and DiscardClass marking; modified ATM-CLP and FR-DE marking. Added objects to handle queue depth unit type and queue depth pair related objects (e.g., cbQosQueueingCfgQLimitUnits and cbQosQueueingCfgAggregateQLimit pair) to support queue depth in different units." REVISION "200103140000Z" DESCRIPTION "Added support for FR DE, ATM CLP and L2 marking. Added Bandwidth remaining percent option" REVISION "200012080000Z" DESCRIPTION "Added support for Police Violate counters and DSCP WRED counters" REVISION "200007130000Z" DESCRIPTION "Initial version of Class-based QoS configuration and statistical parameters MIB" ::= { ciscoMgmt 166 }
ciscoCBQosMIB OBJECT IDENTIFIER ::= { ciscoMgmt 166 }
Vendor: Cisco
Module: CISCO-CLASS-BASED-QOS-MIB
[Automatically extracted from oidview.com]
ciscoCBQosMIB MODULE-IDENTITY LAST-UPDATED "200904240000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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 new and unique 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." REVISION "200904240000Z" DESCRIPTION "- Added cbQosSetCfgFrDe to hold the Fr-De marking configuration value in cbQosSetCfgTable. - Updated the optional groups of ciscocbQosMIBComplianceRev7 with cbQosSetCfgFrDeGroup. - Added MODULE-COMPLIANCE ciscocbQosMIBComplianceRev8." REVISION "200901260000Z" DESCRIPTION "Added account feature in QosObjectType." REVISION "200811200000Z" DESCRIPTION "Added cbQosC3plAccountCfgGroup and cbQosC3plAccountStatsGroup." REVISION "200806170000Z" DESCRIPTION "-Added ratioRemaining in QueueingBandwidthUnits -Added l2CosInner in SetFeatureType -Added cbQosQueueingCfgPriorityLevel in cbQosQueueingCfgTable -Added cbQosSetCfgL2CosInnerValue in cbQosSetCfgTable -Added in cbQosREDClassCfgTable cbQosREDClassCfgMaxThresholdUnit, cbQosREDClassCfgMinThresholdUnit -Added cbQosQueueingClassCfgTable - Added following OBJECT-GROUPs cbQosQueueingCfgGroupRev2 cbQosSetCfgL2Group cbQosQueueingClassCfgGroup cbQosPoliceCfgGroupRev3 - Added MODULE-COMPLIANCE cisco cbQosMIBComplianceRev6" REVISION "200710090000Z" DESCRIPTION "1. Added cbQosTSCfgRate64 to cbQosTSCfgTable to support shaping rates greater than that fit in the range defined for cbQosTSCfgRate. 2. Created cbQosTSCfgExtGroup. 3. Created new compliance module ciscocbQosMIBComplianceRev5 which deprecates ciscocbQosMIBComplianceRev4." REVISION "200708300000Z" DESCRIPTION "Added 'setL2CosInner' value to PoliceAction TC." REVISION "200707100000Z" DESCRIPTION "Added following enumerations to RedMechanism TC: mplsExp redDefault redUserDefault" REVISION "200409200000Z" DESCRIPTION "1. Added vlan-port as a new InterfaceType. 2. Created cbQosServicePolicyExtGroup." REVISION "200404120000Z" DESCRIPTION "Added support for Estimate Bandwidth and its Corvil implementation. Corvil's algorithm generates the estimated bandwidth for a class of traffic from knowledge of the QoS targets such as delay and drop, and the observed traffic behavior." REVISION "200307240000Z" DESCRIPTION "Added setIpDscpTunnel, setIpPrecedenceTunnel to the PoliceAction TC. Added srpPriority, frFecnBecn, ipDscpTunnel, ipPrecedenceTunnel to the SetFeatureType TC. Added l2Cos, atmClp to the REDMechanism TC. Added cps to the CbQosRateType TC. Added CbQosTMSetType TC. Added cbQosQueueingCfgAggrQLimitTime to the cbQosQueueingCfgTable. Added cbQosREDClassCfgMinThresholdTime, cbQosREDClassCfgMaxThresholdTime to the cbQosREDClassCfgTable. Added cbQosPoliceCfgCellRate, cbQosPoliceCfgCellPir, cbQosPoliceCfgBurstCell, cbQosPoliceCfgExtBurstCell, cbQosPoliceCfgBurstTime, cbQosPoliceCfgExtBurstTime, cbQosPoliceCfgCdvt, cbQosPoliceCfgConformColor, cbQosPoliceCfgExceedColor to the cbQosPoliceCfgTable. Added cbQosTSCfgBurstTime, cbQosTSCfgExtBurstTime to the cbQosTSCfgTable. Added cbQosSetCfgSrpPriority, cbQosSetCfgFrFecnBecn to the cbQosSetCfgTable. Added cbQosSetStatsTable. Added cbQosPoliceColorStatsTable. Added cbQosTableMapCfgTable. Added cbQosTableMapValueCfgTable. Added cbQosTableMapSetCfgTable." REVISION "200306090000Z" DESCRIPTION "Added controlPlane to the InterfaceType TC. Added cbQosEntityIndex to the cbQosServicePolicyTable." REVISION "200301210000Z" DESCRIPTION "Added compression(9) in QosObjectType TC for IPHC; Added setMplsExpTopMost(11) in PoliceAction TC for POLICE; Added mplsExpTopMost(8) in SetFeatureType TC for SET; Added discardClass(13) in REDMechanism TC for WRED; Added CbQosRateType TC for POLICE and SHAPE; Added IPHCOption TC for IPHC; Added cbQosPoliceCfgRateType, cbQosPoliceCfgPercentRateValue, cbQosPoliceCfgPercentPirValue for POLICE; Added cbQosTSCfgRateType, cbQosTSCfgPercentRateValue for SHAPE; Added cbQosSetCfgMplsExpTopMostValue for SET; Added cbQosIPHCCfg and cbQosIPHCStats tables for IPHC." REVISION "200212030000Z" DESCRIPTION "Added new cbQosPoliceCfgRate64 to cbQosPoliceCfgEntry table to support policing rates greater than fit in the range defined for cbQosPoliceCfgRate" REVISION "200207240000Z" DESCRIPTION "Added support for ECN; Pir policing; multiple police actions; added MPLS-EXP/ATM-CLP/DR-DE/ L2Cos/DiscardClass marking in police action; added MPLS-EXP and DiscardClass marking; modified ATM-CLP and FR-DE marking. Added objects to handle queue depth unit type and queue depth pair related objects (e.g., cbQosQueueingCfgQLimitUnits and cbQosQueueingCfgAggregateQLimit pair) to support queue depth in different units." REVISION "200103140000Z" DESCRIPTION "Added support for FR DE, ATM CLP and L2 marking. Added Bandwidth remaining percent option" REVISION "200012080000Z" DESCRIPTION "Added support for Police Violate counters and DSCP WRED counters" REVISION "200007130000Z" DESCRIPTION "Initial version of Class-based QoS configuration and statistical parameters MIB" ::= { ciscoMgmt 166 }
ciscoCBQosMIB MODULE-IDENTITY LAST-UPDATED "201401240000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134-1706 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "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." REVISION "201401240000Z" DESCRIPTION "Added new object cbQosParentPolicyIndex in cbQosServicePolicyTable" REVISION "201310100000Z" DESCRIPTION "Added cbQosQueueingStatsGroupRev1 Added ciscocbQosMIBComplianceRev13" REVISION "201306200000Z" DESCRIPTION "Added the following 64-bit Objects cbQosCMPrePolicyBitRate64 cbQosCMPostPolicyBitRate64 cbQosCMDropBitRate64 cbQosPoliceConformedBitRate64 cbQosPoliceExceededBitRate64 cbQosPoliceViolatedBitRate64" REVISION "201302150000Z" DESCRIPTION "Added Percentage as a unit for cbQoSQueueUnitType" REVISION "201207240000Z" DESCRIPTION "The following 2 objects are expanded to include perThousand and perMillion units. 1. QueueingBandwidthUnits 2. CbQosRateType" REVISION "201203220000Z" DESCRIPTION "The following 4 changes have been made 1. Added the following 64 bit objects and deprecated the corresponding 32 bit objects ================================================= cbQosQueueingCfgBandwidth64, cbQosQueueingCfgIndividualQSize64, cbQosPoliceCfgBurstSize64, cbQosPoliceCfgExtBurstSize64, cbQosPoliceCfgPir64, cbQosTSCfgBurstSize64, cbQosTSCfgExtBurstSize64 2. Range expanded for ================== cbQosQueueingCfgBandwidth, cbQosQueueingCfgIndividualQSize, cbQosPoliceCfgBurstSize, cbQosPoliceCfgExtBurstSize, cbQosPoliceCfgPir, cbQosTSCfgBurstSize, cbQosTSCfgExtBurstSize, cbQosREDCfgMinThreshold, cbQosREDCfgMaxThreshold, cbQosPoliceCfgRate, cbQosPoliceCfgBurstCell, cbQosPoliceCfgExtBurstCell, cbQosPoliceCfgBurstTime, cbQosPoliceCfgExtBurstTime, cbQosPoliceCfgCdvt, cbQosTSCfgRate,cbQosTSCfgBurstTime, cbQosTSCfgExtBurstTime 3. New object added ================ cbQosPolicyDiscontinuityTime 4. Added new type (srp-priority) to ================================== PoliceAction" REVISION "200911250000Z" DESCRIPTION "Added setDei(16), setDeiImposition(17) to the TC PoliceAction. Added dei(14), deiImposition(15) to the TC SetFeatureType. Added dei(9) to the TC REDMechanism. Added objects cbQosSetCfgIpPrecedenceTunnelValue, cbQosSetCfgIpDscpTunnelValue, cbQosSetCfgDei, cbQosSetCfgDeiImposition to CbQosSetCfgEntry Added objects cbQosPoliceCfmColorCfmRate, cbQosPoliceCfmColorExdRate, cbQosPoliceCfmColorVltRate, cbQosPoliceExdColorExdRate, cbQosPoliceExdColorVltRate, cbQosPoliceVltColorVltRate to cbQosPoliceColorStatsEntry. Added Objects cbQosIPHCCfgEnabled to cbQosIPHCCfgEntry Added Objects cbQosIPHCRtpFullHdrPktOverflow, cbQosIPHCRtpFullHdrPkt, cbQosIPHCRtpFullHdrPkt64, cbQosIPHCTcpFullHdrPktOverflow, cbQosIPHCTcpFullHdrPkt, cbQosIPHCTcpFullHdrPkt64 to cbQosIPHCStatsEntry Added ciscocbQosMIBComplianceRev10." REVISION "200909160000Z" DESCRIPTION "Added unconfigured(15) value to PoliceAction TC. Added cbQosCMFragmentPktOverflow, cbQosCMFragmentPkt, cbQosCMFragmentPkt64, cbQosCMFragmentByteOverflow, cbQosCMFragmentByte, cbQosCMFragmentByte64 in CbQosCMStatsEntry. Added evc(7) enum value in InterfaceType TC. Added cbQosEVC in CbQosServicePolicyEntry Changed comments for cbQosPolicyIndex and cbQosObjectsIndex. Added ciscocbQosMIBComplianceRev9." REVISION "200904240000Z" DESCRIPTION "- Added cbQosSetCfgFrDe to hold the Fr-De marking configuration value in cbQosSetCfgTable. - Updated the optional groups of ciscocbQosMIBComplianceRev7 with cbQosSetCfgFrDeGroup. - Added MODULE-COMPLIANCE ciscocbQosMIBComplianceRev8." REVISION "200901260000Z" DESCRIPTION "Added account feature in QosObjectType." REVISION "200811200000Z" DESCRIPTION "Added cbQosC3plAccountCfgGroup and cbQosC3plAccountStatsGroup." REVISION "200806170000Z" DESCRIPTION "-Added ratioRemaining in QueueingBandwidthUnits -Added l2CosInner in SetFeatureType -Added cbQosQueueingCfgPriorityLevel in cbQosQueueingCfgTable -Added cbQosSetCfgL2CosInnerValue in cbQosSetCfgTable -Added in cbQosREDClassCfgTable cbQosREDClassCfgMaxThresholdUnit, cbQosREDClassCfgMinThresholdUnit -Added cbQosQueueingClassCfgTable - Added following OBJECT-GROUPs cbQosQueueingCfgGroupRev2 cbQosSetCfgL2Group cbQosQueueingClassCfgGroup cbQosPoliceCfgGroupRev3 - Added MODULE-COMPLIANCE cisco cbQosMIBComplianceRev6" REVISION "200710090000Z" DESCRIPTION "1. Added cbQosTSCfgRate64 to cbQosTSCfgTable to support shaping rates greater than that fit in the range defined for cbQosTSCfgRate. 2. Created cbQosTSCfgExtGroup. 3. Created new compliance module ciscocbQosMIBComplianceRev5 which deprecates ciscocbQosMIBComplianceRev4." REVISION "200708300000Z" DESCRIPTION "Added 'setL2CosInner' value to PoliceAction TC." REVISION "200707100000Z" DESCRIPTION "Added following enumerations to RedMechanism TC: mplsExp redDefault redUserDefault" REVISION "200409200000Z" DESCRIPTION "1. Added vlan-port as a new InterfaceType. 2. Created cbQosServicePolicyExtGroup." REVISION "200404120000Z" DESCRIPTION "Added support for Estimate Bandwidth and its Corvil implementation. Corvil's algorithm generates the estimated bandwidth for a class of traffic from knowledge of the QoS targets such as delay and drop, and the observed traffic behavior." REVISION "200307240000Z" DESCRIPTION "Added setIpDscpTunnel, setIpPrecedenceTunnel to the PoliceAction TC. Added srpPriority, frFecnBecn, ipDscpTunnel, ipPrecedenceTunnel to the SetFeatureType TC. Added l2Cos, atmClp to the REDMechanism TC. Added cps to the CbQosRateType TC. Added CbQosTMSetType TC. Added cbQosQueueingCfgAggrQLimitTime to the cbQosQueueingCfgTable. Added cbQosREDClassCfgMinThresholdTime, cbQosREDClassCfgMaxThresholdTime to the cbQosREDClassCfgTable. Added cbQosPoliceCfgCellRate, cbQosPoliceCfgCellPir, cbQosPoliceCfgBurstCell, cbQosPoliceCfgExtBurstCell, cbQosPoliceCfgBurstTime, cbQosPoliceCfgExtBurstTime, cbQosPoliceCfgCdvt, cbQosPoliceCfgConformColor, cbQosPoliceCfgExceedColor to the cbQosPoliceCfgTable. Added cbQosTSCfgBurstTime, cbQosTSCfgExtBurstTime to the cbQosTSCfgTable. Added cbQosSetCfgSrpPriority, cbQosSetCfgFrFecnBecn to the cbQosSetCfgTable. Added cbQosSetStatsTable. Added cbQosPoliceColorStatsTable. Added cbQosTableMapCfgTable. Added cbQosTableMapValueCfgTable. Added cbQosTableMapSetCfgTable." REVISION "200306090000Z" DESCRIPTION "Added controlPlane to the InterfaceType TC. Added cbQosEntityIndex to the cbQosServicePolicyTable." REVISION "200301210000Z" DESCRIPTION "Added compression(9) in QosObjectType TC for IPHC; Added setMplsExpTopMost(11) in PoliceAction TC for POLICE; Added mplsExpTopMost(8) in SetFeatureType TC for SET; Added discardClass(13) in REDMechanism TC for WRED; Added CbQosRateType TC for POLICE and SHAPE; Added IPHCOption TC for IPHC; Added cbQosPoliceCfgRateType, cbQosPoliceCfgPercentRateValue, cbQosPoliceCfgPercentPirValue for POLICE; Added cbQosTSCfgRateType, cbQosTSCfgPercentRateValue for SHAPE; Added cbQosSetCfgMplsExpTopMostValue for SET; Added cbQosIPHCCfg and cbQosIPHCStats tables for IPHC." REVISION "200212030000Z" DESCRIPTION "Added new cbQosPoliceCfgRate64 to cbQosPoliceCfgEntry table to support policing rates greater than fit in the range defined for cbQosPoliceCfgRate" REVISION "200207240000Z" DESCRIPTION "Added support for ECN; Pir policing; multiple police actions; added MPLS-EXP/ATM-CLP/DR-DE/ L2Cos/DiscardClass marking in police action; added MPLS-EXP and DiscardClass marking; modified ATM-CLP and FR-DE marking. Added objects to handle queue depth unit type and queue depth pair related objects (e.g., cbQosQueueingCfgQLimitUnits and cbQosQueueingCfgAggregateQLimit pair) to support queue depth in different units." REVISION "200103140000Z" DESCRIPTION "Added support for FR DE, ATM CLP and L2 marking. Added Bandwidth remaining percent option" REVISION "200012080000Z" DESCRIPTION "Added support for Police Violate counters and DSCP WRED counters" REVISION "200007130000Z" DESCRIPTION "Initial version of Class-based QoS configuration and statistical parameters MIB" ::= { ciscoMgmt 166 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.166.1 | ciscoCBQosMIBObjects | 34 | 443 | None |
| 1.3.6.1.4.1.9.9.166.2 | ciscocbQosMIBConformance | 2 | 99 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.116 | ciscoDocsExtMIB | 3 | 235 | This is the MIB module for the Cisco specific extension objects of Data Over Cable Service, Radio Frequency interface. There is … |
| 1.3.6.1.4.1.9.9.117 | ciscoEntityFRUControlMIB | 3 | 147 | The CISCO-ENTITY-FRU-CONTROL-MIB is used to monitor and configure operational status of Field Replaceable Units (FRUs) and other … |
| 1.3.6.1.4.1.9.9.118 | ciscoUdldpMIB | 3 | 51 | Cisco Uni Direction Link Detection Protocol MIB |
| 1.3.6.1.4.1.9.9.120 | ciscoNetworkRegistrarMIB | 3 | 125 | MIB for Cisco Network Registrar (CNR). |
| 1.3.6.1.4.1.9.9.121 | ciscoAtmNetworkClockMIB | 3 | 53 | The MIB module for management of network clock distribution and the Network Clock Distribution Protocol (NCDP) in Cisco de… |
| 1.3.6.1.4.1.9.9.122 | ciscoCasaMIB | 3 | 78 | This MIB contains the basic objects for managing a Cisco Appliance Services Architecture (CASA) Entity. A CASA Entity can be a Ma… |
| 1.3.6.1.4.1.9.9.124 | ciscoCallResourcePoolMIB | 3 | 114 | The MIB module for call resource pool management. This MIB supports the resource pool manager feature of CISCO IOS. This feature … |
| 1.3.6.1.4.1.9.9.125 | ciscoWANRsrcPartMIB | 2 | 55 | The MIB module to manage resource partition objects. A resource partition is configured on a virtual interface (ifType value atmV… |
| 1.3.6.1.4.1.9.9.126 | ciscoSonetMIB | 3 | 136 | The MIB module to describe SONET/SDH interfaces objects. This is an extension to the standard SONET MIB(RFC 2558). |
| 1.3.6.1.4.1.9.9.128 | ciscoVlanIfTableRelationshipMIB | 1 | 12 | ciscoVlanIftableRelationshipMIB |
| 1.3.6.1.4.1.9.9.129 | ciscoAtmVirtualIfMIB | 2 | 139 | The MIB module to manage ATM Virtual interface objects. ATM virtual interfaces are configured on a physical line. |
| 1.3.6.1.4.1.9.9.130 | ciscoAdslDmtLineMIB | 3 | 72 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.131 | ciscoSystemMIB | 3 | 57 | The systemGroup (see RFC 1907) provides a standard set of basic system information. This MIB module contains Cisco-defined exten… |
| 1.3.6.1.4.1.9.9.132 | ciscoDs3MIB | 2 | 140 | The MIB module to describe DS3 line objects. This is an extension to the standard DS3 MIB(RFC 2496). |
| 1.3.6.1.4.1.9.9.133 | ciscoAtmCellLayerMIB | 1 | 138 | The MIB module to describe ATM cell layer objects and statistics of a physical line. |
| 1.3.6.1.4.1.9.9.134 | ciscoClusterMIB | 3 | 49 | The MIB module for the management of a group of devices called a 'cluster'. A cluster comprises: 1. A command switch, which is a… |
| 1.3.6.1.4.1.9.9.135 | ciscoWirelessP2pBpiMIB | 3 | 66 | This is the MIB Module for the Baseline Privacy Interface (BPI) at Point to Point Wireless Radio Card. This is a specialization o… |
| 1.3.6.1.4.1.9.9.136 | ciscoWirelessIfMIB | 3 | 307 | This is the MIB Module for the Cisco Wireless Radio Point to Point interface specification. I) Relationship of the Cisco Wireless… |
| 1.3.6.1.4.1.9.9.137 | ciscoWirelessTextualConventions | 0 | 0 | This module defines textual conventions used in Cisco Wireless MIBs. |
| 1.3.6.1.4.1.9.9.138 | ciscoEntityAlarmMIB | 3 | 66 | This MIB module defines the managed objects that support the monitoring of alarms generated by physical entities contained by the… |
| 1.3.6.1.4.1.9.9.139 | ciscoEntityProvMIB | 3 | 13 | This MIB module defines the objects that support provisioning of 'container' class physical entities. Provisioning sets up a 'co… |
| 1.3.6.1.4.1.9.9.140 | ciscoCopsClientMIB | 3 | 43 | This MIB module is for configuration & statistic query of Common Open Policy Service(COPS) client feature on the Cisco device. C… |
| 1.3.6.1.4.1.9.9.141 | ciscoVSIControllerMIB | 2 | 21 | This MIB module is used for configuring ATM Capable Switch to be aware of VSI Controller information. Terminolgies used: VSI … |
| 1.3.6.1.4.1.9.9.144 | ciscoTransactionConnectionMIB | 2 | 66 | The MIB module for retrieving Cisco Transaction Connection configuration and status. Cisco Transaction Connection routes transac… |
| 1.3.6.1.4.1.9.9.145 | ciscoWanModuleMIB | 3 | 32 | The MIB to configure Connection Specific parameters and statistics related information in a Service Module. The Service Module(SM… |
| 1.3.6.1.4.1.9.9.146 | ciscoCallApplicationMIB | 2 | 548 | This MIB allows management of call applications on a network device. A 'call application' is a software module that processes cal… |
| 1.3.6.1.4.1.9.9.147 | ciscoFirewallMIB | 3 | 75 | MIB module for monitoring Cisco Firewalls. |
| 1.3.6.1.4.1.9.9.148 | ciscoBgpPolAcctMIB | 2 | 15 | BGP policy based accounting information |
| 1.3.6.1.4.1.9.9.149 | ciscoAdslLineCapMIB | 3 | 46 | This MIB module serves as an enterprise-specific extension of the ADSL-LINE-MIB. The structure of this MIB module shadows the st… |
| 1.3.6.1.4.1.9.9.150 | ciscoAAASessionMIB | 3 | 31 | This MIB module provides data for accounting sessions based on Authentication, Authorization, Accounting (AAA) protocols. Referenc… |
| 1.3.6.1.4.1.9.9.151 | ciscoL2L3IfConfigMIB | 2 | 11 | Interface switchport mode configuration management MIB. This MIB is used to monitor and control configuration of interface switch… |
| 1.3.6.1.4.1.9.9.152 | ciscoSipUaMIB | 4 | 504 | Cisco User Agent Session Initiation Protocol (SIP) MIB module. SIP is an application-layer signalling protocol for creating, mod… |
| 1.3.6.1.4.1.9.9.154 | ciscoIdslLineMIB | 3 | 148 | This MIB module describes IDSL (ISDN Digital Line Subscriber) line interfaces. The structure of this module resembles that of th… |
| 1.3.6.1.4.1.9.9.155 | ciscoSdslLineMIB | 3 | 170 | This MIB module describes all variations of the symmetric DSL line interfaces. The structure of this module resembles and mainta… |
| 1.3.6.1.4.1.9.9.156 | ciscoCcmMIB | 3 | 487 | The MIB Module for the management of a Cisco Unified Communications Manager (CUCM) application running with a Cisco Communication… |
| 1.3.6.1.4.1.9.9.157 | ciscoCdmaPdsnMIB | 3 | 984 | This MIB is to support the CDMA PDSN (Packet Data Serving Node) feature. A CDMA2000 network supports wireless data communication… |
| 1.3.6.1.4.1.9.9.158 | ciscoAAAClientMIB | 3 | 25 | This MIB module provides data for authentication method priority based on Authentication, Authorization, Accounting (AAA) protoco… |
| 1.3.6.1.4.1.9.9.159 | ciscoQosPolicyConfigMIB | 3 | 35 | This MIB module defines managed objects that support the policy source configuration of Quality of Service (QoS) on the device. T… |
| 1.3.6.1.4.1.9.9.160 | ciscoCircuitInterfaceMIB | 2 | 11 | The MIB module to configure the circuit description for an interface. The circuit description can be used to describe and identify… |
| 1.3.6.1.4.1.9.9.161 | ciscoSlbMIB | 3 | 279 | The MIB for managing Server Load Balancing Manager(s), such as the Cisco IOS SLB product. This MIB includes instrumentation for t… |
| 1.3.6.1.4.1.9.9.162 | ciscoVsiMasterMIB | 3 | 100 | This MIB module contains objects related to the master side of the Virtual Switch Interface protocol used for control of ATM swit… |
| 1.3.6.1.4.1.9.9.163 | ciscoCallTrackerMIB | 3 | 104 | CISCO-CALL-TRACKER-MIB |
| 1.3.6.1.4.1.9.9.164 | ciscoCallTrackerTCPMIB | 3 | 25 | This MIB module provides TCP service connection related data for tracking the progress and status of a call. This module extends t… |
| 1.3.6.1.4.1.9.9.165 | ciscoCallTrackerModemMIB | 3 | 97 | This MIB module provides modem call related data for tracking the progress and status of a call. This module extends tables defin… |
| 1.3.6.1.4.1.9.9.167 | ciscoWirelessDocsIfMib | 3 | 140 | This is the MIB Module for MCNS compliant Radio Frequency (RF) interfaces in wireless point-to-multipoint subscriber units (SU) a… |
| 1.3.6.1.4.1.9.9.168 | ciscoNtpMIB | 3 | 87 | This MIB module defines a MIB which provides mechanisms to monitor an NTP server. The MIB is derived from the Technical Report #Ma… |
| 1.3.6.1.4.1.9.9.169 | ciscoWirelessDocsExtMIB | 3 | 99 | This MIB module defines Cisco-specific objects that add to the functionality defined in CISCO-WIRELESS-DOCS-IF-MIB. These objects … |
| 1.3.6.1.4.1.9.9.170 | ciscoWirelessPhyMIB | 2 | 112 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface. |
| 1.3.6.1.4.1.9.9.171 | ciscoIpSecFlowMonitorMIB | 3 | 507 | This is a MIB Module for monitoring the structures in IPSec-based Virtual Private Networks. The MIB has been designed to be adopt… |
| 1.3.6.1.4.1.9.9.172 | ciscoIpSecPolMapMIB | 3 | 21 | The MIB module maps the IPSec entities created dynamically to the policy entities that caused them. This is an appendix to the IPS… |
| 1.3.6.1.4.1.9.9.173 | ciscoPrivateVlanMIB | 2 | 56 | The MIB module to support Private VLAN feature on Cisco's switching devices. |
| 1.3.6.1.4.1.9.9.174 | ciscoMobileIpMIB | 3 | 533 | An extension to the IETF MIB module defined in RFC-2006 for managing Mobile IP implementations. Mobile IP introduces the followin… |
| 1.3.6.1.4.1.9.9.175 | ciscoIfLinkConfigMIB | 2 | 15 | The MIB module for configuration of bulk distribution (de-multiplexing of traffic from higher-bandwidth to lower-bandwidth interf… |
| 1.3.6.1.4.1.9.9.176 | ciscoRFMIB | 3 | 117 | This MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logic… |
| 1.3.6.1.4.1.9.9.177 | ciscoSaaApmMIB | 3 | 38 | Acronyms and Terms: SAA - Service Assurance Agent APM - Application Performance Monitoring A MIB for controlling SAA APM. APM provi… |
| 1.3.6.1.4.1.9.9.178 | ciscoContentEngineMIB | 3 | 263 | The MIB module for the Cisco Content Engine from Cisco Systems, Inc. |
| 1.3.6.1.4.1.9.9.179 | ciscoCatOSAclQosMIB | 3 | 470 | This MIB module is for Access Control Lists(ACLs) configuration of Quality of Service (QoS) as well as Security feature on the Ci… |
| 1.3.6.1.4.1.9.9.180 | ciscoWirelessRfMetricsMIB | 5 | 99 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface specification. |
| 1.3.6.1.4.1.9.9.181 | ciscoWirelessLinkMetricsMIB | 4 | 141 | This is the MIB Module for the Cisco Wireless Radio Point to MultiPoint interface link metrics specification. Glossary The followin… |
| 1.3.6.1.4.1.9.9.183 | ciscoGprsAccPtMIB | 3 | 338 | This MIB module supports access point configuration for GGSN in a GPRS system. GPRS [1] is a GSM network providing mobile wireles… |
| 1.3.6.1.4.1.9.9.184 | ciscoPimMIB | 3 | 36 | This MIB module defines the cisco specific variables for Protocol Independent Multicast (PIM) management. These definitions are a… |
| 1.3.6.1.4.1.9.9.185 | ciscoBertMIB | 2 | 46 | The MIB module to configure and perform Bit Error Rate Testing (BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces. Bit error rate… |
| 1.3.6.1.4.1.9.9.187 | ciscoBgp4MIB | 4 | 137 | An extension to the IETF BGP4 MIB module defined in RFC 1657. Following is the terminology associated with Border Gateway Protocol… |
| 1.3.6.1.4.1.9.9.188 | cGtpMIB | 3 | 248 | This MIB module manages the GPRS Tunnelling Protocol (GTP) on GGSN and SGSN. GPRS provides wireless access to packet data network… |
| 1.3.6.1.4.1.9.9.189 | ciscoPortQosMIB | 3 | 114 | Cisco PORT QOS MIB - Overview This MIB module is for the management of Cisco's per port rate-limiting and traffic shaping on L3 sw… |
| 1.3.6.1.4.1.9.9.190 | ciscoVoiceAppsMIB | 3 | 40 | The MIB Module for the management of Cisco Voice Applications. This MIB is designed to work in conjunction with the SYSAPPL-MIB … |
| 1.3.6.1.4.1.9.9.191 | ciscoIpUplinkRedirectMIB | 3 | 11 | This MIB module is for the configuration of Cisco IP Uplink Redirect feature. |
| 1.3.6.1.4.1.9.9.192 | ciscoGprsChargingMIB | 3 | 315 | This MIB module manages the charging related function on the GGSN node of a GPRS system. The following diagram illustrates a simp… |
| 1.3.6.1.4.1.9.9.194 | ciscoPppoeMIB | 3 | 89 | Cisco PPPoE sessions management MIB Module. |
| 1.3.6.1.4.1.9.9.195 | ciscoEntityExtMIB | 3 | 64 | This MIB is an extension of the ENTITY-MIB specified in RFC2737. This MIB module contains Cisco-defined extensions to the entit… |
| 1.3.6.1.4.1.9.9.197 | ciscoDistDirMIB | 3 | 123 | Cisco Distributed Director MIB. The Cisco Distributed Director provides global Internet scalability and increased performance as … |
| 1.3.6.1.4.1.9.9.198 | ciscoRfSupMIB | 3 | 58 | This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redund… |
| 1.3.6.1.4.1.9.9.199 | ciscoSmFileDownloadMIB | 3 | 23 | The MIB module for downloading files to the Service Modules specifically designed for an architecture containing a controller car… |
| 1.3.6.1.4.1.9.9.201 | ciscoSwitchUsageMIB | 3 | 15 | This MIB defines objects related to statistics for the usage of switch fabric. The switch fabric is used by the incoming packets … |
| 1.3.6.1.4.1.9.9.202 | ciscoOscpMIB | 3 | 52 | The MIB module for managing the Cisco Optical Supervisory Channel Protocol (OSCP). The OSCP is used to determine and maintain wav… |
| 1.3.6.1.4.1.9.9.204 | ciscoXdslLineMIB | 2 | 32 | The tables defined by this MIB module contain a collection of managed objects that are general in nature and apply to different t… |
| 1.3.6.1.4.1.9.9.215 | ciscoMacNotificationMIB | 3 | 72 | This MIB module is for configuration of the MAC notification feature. MAC notification is a mechanism to inform monitoring device… |
| 1.3.6.1.4.1.9.9.216 | ciscoContentNetworkMIB | 3 | 34 | This MIB module defines objects for Content Network devices. A Content Network is a collection of devices that optimizes the deli… |
| ... | ||||