NTN-QOS-POLICY-AUX-MIB: View SNMP OID List / Download MIB

Contains interface index to interface role combination associations.

A conceptual row in the ntnQosInterfaceIdTable. Each row identifies an interface value that corresponds to an entry in the ifTable (MIB-II) and a role combination taglist with which the interface is associated.

The ifIndex value that is associated with this instance of the ntnQosInterfaceIdEntry. The ifIndex value of this attribute must correspond to the ifTable entry with the same ifIndex value.

The role combination that is associated with the interface with an ifIndex value that is equal to ntnQosInterfaceIdIfIndex.

The storage type for this conceptual row. Conceptual rows having the value permanent(4) need not allow write-access to any columnar objects in the row. This object may not be modified if the associated ntnQosInterfaceIdStatus object is equal to active(1).

The status of this row. An entry may not exist in the active state unless all objects in the entry have an appropriate value. Row creation using only default values is supported.

The queue set associated with this interface. A queue set must be defined in the qosInterfaceQueueTable prior to being referenced by this attribute.

This module defines an infrastructure used for support of policy-based traffic processing in a network device.

Specifies whether dynamic management (e.g., COPS-PR) is currently enabled. Devices may limit support for dynamic management by providing read-only access to this object. If enabled, dynamic management always takes precedence over static management such that static management may only be used for monitoring of objects that have a POLICY-ACCESS clause of 'install' or 'install-notify' in the respective PIB module. Disabling dynamic management causes Delete Request State (DRQ) and Client Close (CC) messages to be generated if a connection between the PEP and a PDP is currently established. Installed policies are not automatically deleted. Enabling dynamic management will initiate the COPS-PR connect sequence and, potentailly, the loading of policy information. Enumeration: 'disabled': 2, 'enabled': 1.

The state of the QoS Policy Agent (QPA). A state of 'running(1)' indicates that the QPA is in a stable state and can process messages. A state of 'initializing(2)' indicates that the agent is currently unable to process messages. Either 'running(1)' or 'initializing(2)' will be returned when querying this object. These values can not be set. All installed state can be deleted and reset to the device's default state by setting the value of this object to 'resetToDefault(3)'. This is the only value that will be accepted when setting this object. The 'resetToDefault(3)' value will never be returned in response to a query. Enumeration: 'running': 1, 'resetToDefault': 3, 'initializing': 2.

The number of seconds between the receipt of a connection termination/rejection indication and the initiation of a new connection request. A value of -1 indicates that a connection retry should not be attempted after a failed attempt.

Support for certain Per-Hop-Behaviors (PHBs) requires that packets within a flow not be reordered upon transmission. Packet reordering may not be an issue for other PHBs. Setting this object to 'true(1)' allows full flexibility in terms of the egress queue to which a packet is assigned. A value of 'false(2)' causes the agent to verify that in-profile and out-of-profile actions associated with a flow will not cause packets from the same flow to be assigned to different egress queues.

Policing statistics, such as in-profile and out-of-profile octets, are often an important mechanism for evaluating the effectiveness of installed policies. In order to track these statistics, additional system resources are consumed meaning that the amount of filters available for classification purposes is limited. Setting this object to 'true(1)' causes statistics to be tracked by default for all metered policies defined after this attribute is set. A value of 'false(2)' means that new metered policies will not track statistics. Note that this attribute specifies the default behavior. Statistics maintenance may be enabled and disabled on a per policy basis via an attribute in the ntnQosTargetStatsTable. If a value for that attribute is not provided, the value of this object determines the behavior.

Specifies which interface class types can be defined by the user. Default filters are installed to support the different interface classes. Limiting the classes that can be used reduces, or eliminates entirely, the default filter resources that must be consumed, making these resources available for administrator use. Modifications to this attribute require a system initialization before they take effect. Enumeration: 'unrestrictedAndTrusted': 2, 'allowAllIfcClasses': 3, 'unrestrictedOnly': 1.

This attribute identifies the action that is to be initiated for flows that are determined to be out-of-profile and are being metered using the 'committedRestricted' type of meter. Actions must be defined in the qosActionTable prior to being referenced by this attribute. The value of this attribute may not be changed while meters of this type are currently associated with a policy.

Specifies whether policies referencing IP filter criteria can be defined by the user. The value of this attribute determines if new IP filter-based policies can be installed. If the value of this attribute is 'noPolicyRestrictions(1)', both IP and Layer 2-based policies can be installed. If the value is 'l3PolicyRestrictions(2)', only Layer 2-based policies can be installed. This attribute is only consulted when traffic separation mode is enabled. Modification of this attribute may be restricted based on the interface used (e.g., CLI) for the modification. Enumeration: 'l3PolicyRestrictions': 2, 'noPolicyRestrictions': 1.

Contains items that supplement the target group data that is specified in the qosTargetTable.

A conceptual row in the ntnQosTargetStatsTable. Each row contains statistics related to the associated qosTargetTable entry. Entries will be automatically deleted from this table should the corresponding qosTargetTable entry be destroyed.

This object tracks the packet hits of this target group specification. Packet hits are defined as packets that are selected for additional processing based on target data specified in the associated qosTargetTable entry.

The number of times the associated ntnQosTargetStatsPktHits counter has overflowed.

This object tracks the packet hits of this target group specification. Packet hits are defined as packets that are selected for additional processing based on target data specified in the associated qosTargetTable entry.

This object tracks the total number of octets associated with packet hits of this target group specification.

The number of times the associated ntnQosTargetStatsTotalOctets counter has overflowed.

This object tracks the total number of octets associated with packet hits of this target group specification.

This object tracks the total number of octets associated with packets considered to be in-profile based on the metering specification associated with this target group entry.

The number of times the associated ntnQosTargetStatsInProfOctets counter has overflowed.

This object tracks the total number of octets associated with packets considered to be in-profile based on the metering specification associated with this target group entry.

This object tracks the total number of octets associated with packets considered to be out-of- profile based on the metering specification associated with this target group entry.

The number of times the associated ntnQosTargetStatsOutProfOctets counter has overflowed.

This object tracks the total number of octets associated with packets considered to be out-of- profile based on the metering specification associated with this target group entry.

Policing statistics, such as in-profile and out-of-profile octets, are often an important mechanism for evaluating the effectiveness of installed policies. In order to track these statistics, additional system resources are consumed meaning that the amount of filters available for classification purposes is limited. Setting this object to 'true(1)' causes statistics to be tracked for the metered policy being defined. A value of 'false(2)' means that the metered policy will not track statistics.

This object counts the number of packets dropped due to insufficient shaping resources. Traffic that is being shaped prior to transmission may need to be buffered temporarily to ensure conformance to the associated shaping specification. Shaping buffer resources are limited. If shaping buffer resources are exhausted, traffic that is to be shaped will be dropped, causing this counter to be incremented once per dropped packet, until resources become available.

The number of times the associated ntnQosTargetStatsShapingQDrops counter has overflowed.

This object counts the number of packets dropped due to insufficient shaping resources. Traffic that is being shaped prior to transmission may need to be buffered temporarily to ensure conformance to the associated shaping specification. Shaping buffer resources are limited. If shaping buffer resources are exhausted, traffic that is to be shaped will be dropped, causing this counter to be incremented once per dropped packet, until resources become available.

Describes the requirements for conformance to the Nortel Networks QoS Policy MIB.

Objects used to configure QoS Policy Agent operation.

Objects used to define interface (ifIndex) to interface role combination mappings.

Objects that supplement the qosTargetTable providing per target statistics.