2000-11-02
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).
Download CISCO-QOS-POLICY-CONFIG-MIB.txt Open CISCO-QOS-POLICY-CONFIG-MIB.txt in a new tab
| Name | OID |
|---|---|
| qosPrIfTable | 1.3.6.1.4.1.9.9.159.1.2.1 |
| qosIfCapabilityTable | 1.3.6.1.4.1.9.9.159.1.2.2 |
END OF TOC
1.3.6.1.4.1.9.9.159.1.1.1
TruthValue1 = true2 = falseRepresents a boolean value. · Integer32
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.
1.3.6.1.4.1.9.9.159.1.1.2
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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.
1.3.6.1.4.1.9.9.159.1.1.3
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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'.
1.3.6.1.4.1.9.9.159.1.1.4
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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.
1.3.6.1.4.1.9.9.159.1.1.5
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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'.
1.3.6.1.4.1.9.9.159.1.1.6
INTEGER1 = keep2 = discard · Integer32
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.
1.3.6.1.4.1.9.9.159.1.2.1
Index: ifIndex
A list of interface entries. An entry will exist for each interface which can support the provisioning of QoS policy feature.
from IF-MIB
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
1.3.6.1.4.1.9.9.159.1.2.1.1.1
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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).
1.3.6.1.4.1.9.9.159.1.2.1.1.2
QosPolicySource1 = none2 = local3 = copsThe source where a device obtains QoS policy. none (1) indicates that there is no QoS policy applied on this device. And this value only can be read and cannot be set by the users. local (2) indicates that the QoS policy is from local device configuration. For example, the QoS policy can be configured through command line interface (CLI). cops (3) indicates that the QoS policy is from a COPS server. · Integer32
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'.
1.3.6.1.4.1.9.9.159.1.2.2
Index: ifIndex · qosIfDirection · qosIfQType
A list of interface entries. An entry will exist for each interface which can support the QoS feature.
from IF-MIB
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
A unique value, greater than zero, for each interface. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re- initialization.
1.3.6.1.4.1.9.9.159.1.2.2.1.1
INTEGER1 = ingress2 = egress3 = both · Integer32
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.
1.3.6.1.4.1.9.9.159.1.2.2.1.2
QosInterfaceQueueType1 = oneQ1t2 = oneQ2t3 = oneQ4t4 = oneQ8t5 = twoQ1t6 = twoQ2t7 = twoQ4t8 = twoQ8t9 = threeQ1t10 = threeQ2t11 = threeQ4t12 = threeQ8t13 = fourQ1t14 = fourQ2t15 = fourQ4t16 = fourQ8t17 = eightQ1t18 = eightQ2t19 = eightQ4t20 = eightQ8t21 = sixteenQ1t22 = sixteenQ2t23 = sixteenQ4t24 = sixtyfourQ1t25 = sixtyfourQ2t26 = sixtyfourQ4t27 = oneP1Q0t28 = oneP1Q4t29 = oneP1Q8t30 = oneP2Q1t31 = oneP2Q2t32 = oneP3Q1t33 = oneP7Q8t34 = oneP3Q8t35 = sixteenQ8t36 = oneP15Q8t37 = oneP15Q1t38 = oneP7Q1t39 = oneP31Q1t40 = thirtytwoQ1t41 = thirtytwoQ8t42 = oneP31Q8t43 = oneP7Q4t44 = oneP3Q4t45 = oneP7Q2tAn enumerated type for all the known interface types. The interface types are currently limited to a predefined combination of queues and thresholds such that the product of queues and thresholds does not exceed 64 (i.e., the total number of DSCPs. · Integer32
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.
1.3.6.1.4.1.9.9.159.1.2.2.1.3
BITS
An enumeration of interface capabilities. Used by the management side to select policies and configuration to push to the device.