NTN-QOS-POLICY-AUX-MIB

All MIBs › NTN-QOS-POLICY-AUX-MIB

Organization: Nortel Networks, Inc.

Last Updated: 2004-07-20

Category: QoS and Policy

Description: Defines auxiliary QoS policy objects supplementing the core Nortel Networks PIB-based QoS policy framework.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is NTN-QOS-POLICY-AUX-MIB?

NTN-QOS-POLICY-AUX-MIB supplies auxiliary SNMP objects for Nortel Networks' policy-based QoS (Quality of Service) traffic-processing framework, complementing Nortel's primary COPS-PR/PIB-based QoS policy mechanism with objects better suited to SNMP access. It exposes configuration controls for dynamic policy management, QoS Policy Agent (QPA) state and retry timing, packet-reordering allowance, policing-statistics maintenance, and per-interface role/classification restrictions via an interface ID table. Its monitoring role centers on QoS software/configuration status: operators can check ntnQosConfigQpaState to confirm the policy agent is properly connected and synchronized, and watch ntnQosConfigMaintainPolicingStats to verify policing counters are being kept, both important for diagnosing why QoS policies aren't being applied as expected. It is explicitly an auxiliary/companion MIB to Nortel's core PIB-based QoS policy framework, so it has a direct dependency on that standard rather than standing alone. It is deployed on Nortel Networks routers/switches that support centralized, policy-server-driven QoS traffic management, and network engineers typically complete an NTN-QOS-POLICY-AUX-MIB download from Nortel/Avaya archives before compiling it alongside the core PIB-based QoS MIB.

IPNetwork Monitor allows you to monitor SNMP objects defined in NTN-QOS-POLICY-AUX-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Nortel Networks router/switch

Monitoring Examples

An operator polls ntnQosConfigQpaState to verify the device's QoS Policy Agent is actively synced with the policy server, and checks ntnQosInterfaceIdTable, via ntnQosInterfaceIdIfIndex and ntnQosInterfaceIdRoleCombination, to confirm an interface has the expected QoS role assigned; a QPA state stuck in retry combined with an incrementing ntnQosConfigQpaRetryTimer indicates the device has lost contact with its policy decision point.

What Can Be Monitored

QoS Policy Agent (QPA) connection state
policy retry timer
per-interface QoS role assignment
packet reordering/policing statistics settings
dynamic policy management status

Imported Objects

From IF-MIB

InterfaceIndex

From NTN-QOS-POLICY-EXT-PIB

ntnQosIfParametersExt

OBJECT-IDENTITY

From POLICY-FRAMEWORK-PIB

PolicyInstanceId
RoleCombination

From QOS-POLICY-IP-PIB

qosTargetEntry

OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
StorageType
TruthValue

From SYNOPTICS-ROOT-MIB

policy

OBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using ntnQosTargetStatsPktHits OID:

Select a Nortel Networks router/switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type ntnQosTargetStatsPktHits into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object tracks the packet hits of this target group specification. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in packets), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ntnQosCompliance	1.3.6.1.4.1.45.4.5.2.1.1			Describes the requirements for conformance to the Nortel Networks QoS Policy MIB.
ntnQosCompliances	1.3.6.1.4.1.45.4.5.2.1
ntnQosConfig	1.3.6.1.4.1.45.4.5.1.1
T/F ntnQosConfigAllowPacketReordering	1.3.6.1.4.1.45.4.5.1.1.4	TruthValue	read-write	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.
POL ntnQosConfigDefaultOutOfProfileAction	1.3.6.1.4.1.45.4.5.1.1.7	PolicyInstanceId	read-write	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.
INT ntnQosConfigDynamicMgmt	1.3.6.1.4.1.45.4.5.1.1.1	INTEGER	read-write	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.
ntnQosConfigGroup	1.3.6.1.4.1.45.4.5.2.2.1			Objects used to configure QoS Policy Agent operation.
INT ntnQosConfigIfcClassRestrictions	1.3.6.1.4.1.45.4.5.1.1.6	INTEGER	read-write	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.
T/F ntnQosConfigMaintainPolicingStats	1.3.6.1.4.1.45.4.5.1.1.5	TruthValue	read-write	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.
INT ntnQosConfigPolicyCfgRestrictionMode	1.3.6.1.4.1.45.4.5.1.1.8	INTEGER	read-write	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.
I32 ntnQosConfigQpaRetryTimer	1.3.6.1.4.1.45.4.5.1.1.3	Integer32	read-write	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.
INT ntnQosConfigQpaState	1.3.6.1.4.1.45.4.5.1.1.2	INTEGER	read-write	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.
ntnQosGroups	1.3.6.1.4.1.45.4.5.2.2
ntnQosInterfaceIdEntry	1.3.6.1.4.1.45.4.4.1.1.4.1		not-accessible	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.
ntnQosInterfaceIdGroup	1.3.6.1.4.1.45.4.5.2.2.2			Objects used to define interface (ifIndex) to interface role combination mappings.
NUM ntnQosInterfaceIdIfIndex	1.3.6.1.4.1.45.4.4.1.1.4.1.1	InterfaceIndex	not-accessible	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.
POL ntnQosInterfaceIdQueueSet	1.3.6.1.4.1.45.4.4.1.1.4.1.5	PolicyInstanceId	read-create	The queue set associated with this interface. A queue set must be defined in the qosInterfaceQueueTable prior to being referenced by this attribute.
ROL ntnQosInterfaceIdRoleCombination	1.3.6.1.4.1.45.4.4.1.1.4.1.2	RoleCombination	read-create	The role combination that is associated with the interface with an ifIndex value that is equal to ntnQosInterfaceIdIfIndex.
ROW ntnQosInterfaceIdStatus	1.3.6.1.4.1.45.4.4.1.1.4.1.4	RowStatus	read-create	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.
STO ntnQosInterfaceIdStorageType	1.3.6.1.4.1.45.4.4.1.1.4.1.3	StorageType	read-create	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).
ntnQosInterfaceIdTable	1.3.6.1.4.1.45.4.4.1.1.4		not-accessible	Contains interface index to interface role combination associations.
ntnQosPolicyAuxConformance	1.3.6.1.4.1.45.4.5.2
ntnQosPolicyAuxMib	1.3.6.1.4.1.45.4.5			This module defines an infrastructure used for support of policy-based traffic processing in a network device.
ntnQosPolicyAuxObjects	1.3.6.1.4.1.45.4.5.1
ntnQosStatistics	1.3.6.1.4.1.45.4.5.1.2
ntnQosTargetStatsEntry	1.3.6.1.4.1.45.4.5.1.2.1.1		not-accessible	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.
ntnQosTargetStatsGroup	1.3.6.1.4.1.45.4.5.2.2.3			Objects that supplement the qosTargetTable providing per target statistics.
C64 ntnQosTargetStatsHCPktHits	1.3.6.1.4.1.45.4.5.1.2.1.1.3	Counter64	read-only	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.
C64 ntnQosTargetStatsHCShapingQDrops	1.3.6.1.4.1.45.4.5.1.2.1.1.16	Counter64	read-only	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.
C64 ntnQosTargetStatsInProfHCOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.9	Counter64	read-only	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.
C32 ntnQosTargetStatsInProfOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.7	Counter32	read-only	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.
C32 ntnQosTargetStatsInProfOverflowOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.8	Counter32	read-only	The number of times the associated ntnQosTargetStatsInProfOctets counter has overflowed.
C64 ntnQosTargetStatsOutProfHCOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.12	Counter64	read-only	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.
C32 ntnQosTargetStatsOutProfOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.10	Counter32	read-only	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.
C32 ntnQosTargetStatsOutProfOverflowOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.11	Counter32	read-only	The number of times the associated ntnQosTargetStatsOutProfOctets counter has overflowed.
C32 ntnQosTargetStatsOverflowPktHits	1.3.6.1.4.1.45.4.5.1.2.1.1.2	Counter32	read-only	The number of times the associated ntnQosTargetStatsPktHits counter has overflowed.
C32 ntnQosTargetStatsOverflowShapingQDrops	1.3.6.1.4.1.45.4.5.1.2.1.1.15	Counter32	read-only	The number of times the associated ntnQosTargetStatsShapingQDrops counter has overflowed.
C32 ntnQosTargetStatsPktHitsEx	1.3.6.1.4.1.45.4.5.1.2.1.1.1	Counter32	read-only	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.
C32 ntnQosTargetStatsShapingQDrops	1.3.6.1.4.1.45.4.5.1.2.1.1.14	Counter32	read-only	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.
ntnQosTargetStatsTable	1.3.6.1.4.1.45.4.5.1.2.1		not-accessible	Contains items that supplement the target group data that is specified in the qosTargetTable.
C64 ntnQosTargetStatsTotalHCOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.6	Counter64	read-only	This object tracks the total number of octets associated with packet hits of this target group specification.
C32 ntnQosTargetStatsTotalOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.4	Counter32	read-only	This object tracks the total number of octets associated with packet hits of this target group specification.
C32 ntnQosTargetStatsTotalOverflowOctets	1.3.6.1.4.1.45.4.5.1.2.1.1.5	Counter32	read-only	The number of times the associated ntnQosTargetStatsTotalOctets counter has overflowed.
T/F ntnQosTargetStatsTrackStatistics	1.3.6.1.4.1.45.4.5.1.2.1.1.13	TruthValue	read-write	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.

RFC description

A MIB for managing QoS (Quality of Service) policies in NTN (Non-Terrestrial Networks) environments. This auxiliary MIB provides additional management objects for quality of service policy configuration and monitoring in satellite and aerial network systems.

Start monitoring Nortel Networks routers/switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download NTN-QOS-POLICY-AUX-MIB