DISMAN-EVENT-MIB :: mteResourceSampleInstanceLacks

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDISMAN-EVENT-MIBmteResourceSampleInstanceLacks

mteResourceSampleInstanceLacks

Module: DISMAN-EVENT-MIB

OID (symbolic): DISMAN-EVENT-MIB::mteResourceSampleInstanceLacks

OID (numeric): 1.3.6.1.2.1.88.1.1.5

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum.

What is mteResourceSampleInstanceLacks?

This counter tracks how many times the system failed to allocate a new trigger-sampling instance because doing so would have exceeded mteResourceSampleInstanceMaximum. A nonzero and rising count here means triggers are silently failing to sample some object instances due to the configured resource cap.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.88.1.1.5
snmpwalk -v2c -c public <target> DISMAN-EVENT-MIB::mteResourceSampleInstanceLacks

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.88.1.1.5.1
snmpget -v2c -c public <target> DISMAN-EVENT-MIB::mteResourceSampleInstanceLacks.1

Start monitoring SNMP-capable network device or management station (vendor-neutral, DISMAN event triggers) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DISMAN-EVENT-MIB::mteResourceSampleInstanceLacks OID value, configure state conditions and alerts, and monitor any SNMP-capable network device or management station (vendor-neutral, DISMAN event triggers) from a single console.

How to Use in IPNetwork Monitor

Select a SNMP-capable network device or management station (vendor-neutral, DISMAN event triggers) 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 mteResourceSampleInstanceLacks into the Find box to locate it in the OID tree, then select it and click OK. The number of times this system could not take a new sample because that allocation would have exceeded the limit set by mteResourceSampleInstanceMaximum. 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 instances), 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.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.88dismanEventMIBDISMAN-EVENT-MIB
1.3.6.1.2.1.88.1dismanEventMIBObjectsDISMAN-EVENT-MIB
1.3.6.1.2.1.88.1.1mteResourceDISMAN-EVENT-MIB
1.3.6.1.2.1.88.1.1.5mteResourceSampleInstanceLacksDISMAN-EVENT-MIB