CISCO-QOS-POLICY-CONFIG-MIB.mib object
Introduction
Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2025 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers).
This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.
ActiveXperts Network Monitor 2025 can import MIB file CISCO-QOS-POLICY-CONFIG-MIB and use it to monitor vendor specific OID's.
CISCO-QOS-POLICY-CONFIG-MIB file content
Object view of CISCO-QOS-POLICY-CONFIG-MIB:
| Scalar Object |
| qosEnabled |
.1.3.6.1.4.1.9.9.159.1.1.1 |
|
Indicates whether the QoS feature is enabled on the device.
true(1) means that the QoS feature is enabled on this device.
false(2) means that the QoS feature is disabled. All the QoS
policy on the device will be ignored.
|
| qosPrAdminPolicySource |
.1.3.6.1.4.1.9.9.159.1.1.2 |
|
Indicates the desired source of a device's provisioning of
QoS policy for the whole device.
Actually, the source of an interface's provisioning of QoS
policy is controlled by two level configurations. The first
level is the system level to be the global control for the
whole device. This object is for the system level. The second
level is for each individual interface. The
qosPrIfAdminPolicySource is for the interface level. So, the
value of this object will decide that the value of
qosPrIfAdminPolicySource can take precedence or not. If this
object is configured to cops(3), the value of
qosPrIfAdminPolicySource has the precedence configuration of
the interface's provisioning of QoS policy source.
That is to say if this object is configured to local(2), then
the value of qosPrIfAdminPolicySource will be ignored. It
means the provisioning of QoS policy source of all the
interfaces in this device will be from local information if
this MIB is configured to local(2).
If this object is configured to cops(3), then the final
provisioning of QoS policy of an interface is determined by the
configuration of the qosPrIfAdminPolicySource object of that
interface.
Changing qosPrIfAdminPolicySource of an interface from cops(3)
to local(2) while the value of this object is cops(3) makes the
interface discard the QoS provisioning policy from the COPS
server and uses the local QoS provisioning policy configuration
instead.
|
| qosPrOperPolicySource |
.1.3.6.1.4.1.9.9.159.1.1.3 |
|
Indicates the operational source of a device's provisioning of
QoS policy.
Note that when qosPrAdminPolicySource transitions to cops(3),
qosPrOperPolicySource will normally also transition to
cops(3). In this situation, it is possible that
qosPrOperPolicySource's transition will not occur immediately
because the system is initializing the COPS function at the
system booting up time, but rather after a small time lag to
complete certain operations before going 'cops'.
|
| qosRsvpAdminPolicySource |
.1.3.6.1.4.1.9.9.159.1.1.4 |
|
Indicates the desired source of a device's outsourcing of QoS
policy. Outsourcing means the policy information is from
outside source not from local information.
|
| qosRsvpOperPolicySource |
.1.3.6.1.4.1.9.9.159.1.1.5 |
|
Indicates the current operational source of a device's
outsourcing of QoS policy.
Note that when qosRsvpAdminPolicySource transitions to
cops(3), qosRsvpOperPolicySource will normally also transition
to cops(3). In this situation, it is possible that
qosRsvpOperPolicySource's transition will not occur
immediately because the system is initializing the COPS
function at the system boot up time, but rather after a small
time lag to complete certain operations before going 'cops'.
|
| qosCopsPolicyStatus |
.1.3.6.1.4.1.9.9.159.1.1.6 |
|
This object indicates whether the QoS policy downloaded from
COPS server should be kept or discarded by the system while
the COPS function is not running in the system or the
connection between PDP and PEP is lost or any other reason
that system cannot get the QoS policy from COPS server.
|
| qosPrIfEntry |
.1.3.6.1.4.1.9.9.159.1.2.1.1 |
|
An entry containing the configuration of provisioning of QoS
policy of a particular interface.
|
| qosIfCapabilityEntry |
.1.3.6.1.4.1.9.9.159.1.2.2.1 |
|
A description of an interface's QoS capabilities.
|
| Tabular Object |
| qosPrIfAdminPolicySource |
.1.3.6.1.4.1.9.9.159.1.2.1.1.1 |
|
Indicates the desired source of QoS provision policy for
this interface.
This object is only effective when the value of
qosPrOperPolicySource is cops(3) and the value of qosEnabled
is true(1).
|
| qosPrIfOperPolicySource |
.1.3.6.1.4.1.9.9.159.1.2.1.1.2 |
|
Indicates the operational source of QoS provisioning policy
for this interface.
When the value of the object qosPrOperPolicySource is
local(2), the QoS provisioning policy for this interface is
taken from device's local configuration. If
qosPrOperPolicySource is configured to cops(3), the current
operational source of QoS provisioning policy will depend on
the configuration of qosPrIfAdminPolicySource object.
Here is the logic.
IF qosPrOperPolicySource == local(2)
THEN qosPrIfOperPolicySource is local(2)
ELSE
IF qosPrOperPolicySource == cops(3)
THEN
IF qosPrIfAdminPolicySource == cops(3)
THEN qosPrIfOperPolicySource is cops(3)
ELSE qosPrIfOperPolicySource is local(2)
ELSE
qosPrIfOperPolicySource is none(1)
END
END
For example, if qosPrOperPolicySource shows local(2), although
the qosPrIfAdminPolicySource is configured cops(3), the QoS
provisioning policy running on this interface is from local
device configuration. It means this object will be local(2).
Note that when qosPrIfAdminPolicySource transitions to
cops(3) if qosPrOperPolicySource is cops(3),
qosPrIfOperPolicySource will normally also transition to
cops(3). In this situation, it is possible that
qosPrIfOperPolicySource's transition will not occur immediately
because the system is initializing the COPS function at the
system boot up time, but rather after a small time lag to
complete certain operations before going 'cops'.
|
| qosIfDirection |
.1.3.6.1.4.1.9.9.159.1.2.2.1.1 |
|
The traffic direction of the interface.
'ingress' means the traffic coming in the interface.
'egress' means the traffic going out the interface.
'both' means the traffic coming in and going out.
|
| qosIfQType |
.1.3.6.1.4.1.9.9.159.1.2.2.1.2 |
|
The interface type in terms of number of queues and
thresholds. A queue is a buffer for storing network packets.
A threshold is a water mark used to control traffic amount of
a queue.
|
| qosIfCapabilities |
.1.3.6.1.4.1.9.9.159.1.2.2.1.3 |
|
An enumeration of interface capabilities. Used by the
management side to select policies and configuration to
push to the device.
|
| Table |
| qosPrIfTable |
.1.3.6.1.4.1.9.9.159.1.2.1 |
|
A list of interface entries. An entry will exist for each
interface which can support the provisioning of QoS policy
feature.
|
| qosIfCapabilityTable |
.1.3.6.1.4.1.9.9.159.1.2.2 |
|
A list of interface entries. An entry will exist for each
interface which can support the QoS feature.
|
| Object Identifier |
| ciscoQosPolicyConfigMIB |
.1.3.6.1.4.1.9.9.159 |
|
This MIB module defines managed objects that support the
policy source configuration of Quality of Service (QoS) on
the device.
Terminology :
Common Open Policy Service (COPS) : A client/server model for
supporting policy control over QoS Signaling Protocols and
provisioned QoS resource management, etc. COPS is a query and
response protocol that can be used to exchange policy
information between a policy server (Policy Decision Point or
PDP) and its clients (Policy Enforcement Points or PEPs).
Policy Information Base (PIB) : The database of policy
information stored in the COPS client device.
QoS : The method which attempts to ensure that the network
requirements of different applications can be met by giving
preferential forwarding treatment to some traffic, perhaps at
the expense of other traffic.
QoS policy : a set of parameters used to achieve QoS purpose.
The device uses these parameters in flow classification, flow
scheduling, flow policing and codepoint mutation.
RSVP : Resource Reservation Protocol. RSVP is a signaling
mechanism that the application will use to signal parameters
to the network, so that network can assign QoS for the
application data stream.
COPS-PR : a COPS client type which supports device's
provisioning of QoS policy.
COPS-RSVP : a COPS client type which supports device's
outsourcing of QoS policy (RSVP).
|
| ciscoQosPolicyConfigMIBObjects |
.1.3.6.1.4.1.9.9.159.1 |
| qosPolicyGlobalObjects |
.1.3.6.1.4.1.9.9.159.1.1 |
| qosPolicyInterfaceObjects |
.1.3.6.1.4.1.9.9.159.1.2 |
| ciscoQosPolicyMIBNotifications |
.1.3.6.1.4.1.9.9.159.2 |
| ciscoQosPolicyConfigMIBConformance |
.1.3.6.1.4.1.9.9.159.3 |
| ciscoQosPolicyConfigMIBCompliances |
.1.3.6.1.4.1.9.9.159.3.1 |
| ciscoQosPolicyConfigMIBGroups |
.1.3.6.1.4.1.9.9.159.3.2 |
| Group |
| qosGlobalGroup |
.1.3.6.1.4.1.9.9.159.3.2.1 |
|
A collection of objects providing the ability to
enable/disable QoS feature on the device.
|
| qosPrGlobalGroup |
.1.3.6.1.4.1.9.9.159.3.2.2 |
|
A collection of objects providing the global configuration of
the provisioning of QoS policy source on the device.
|
| qosRsvpGlobalGroup |
.1.3.6.1.4.1.9.9.159.3.2.3 |
|
A collection of objects providing the global configuration of
the outsourcing of QoS policy source on the device.
|
| qosPrInterfaceGroup |
.1.3.6.1.4.1.9.9.159.3.2.4 |
|
A collection of objects providing the interface level
configuration of the provisioning of QoS policy source on the
device.
|
| qosInterfaceCapabilityGroup |
.1.3.6.1.4.1.9.9.159.3.2.5 |
|
A collection of object providing the QoS capabilities of the
interface on the device to help QoS policy configuration.
|
| qosCopsPolicyStatusGroup |
.1.3.6.1.4.1.9.9.159.3.2.6 |
|
A collection of object providing the status of QoS policy
downloaded from COPS server.
|
