ATM-RMON-MIB :: atmStatsControlDropEvents

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsATM-RMON-MIBatmStatsControlDropEvents

atmStatsControlDropEvents

Module: ATM-RMON-MIB

OID (symbolic): ATM-RMON-MIB::atmStatsControlDropEvents

OID (numeric): 1.3.6.1.4.1.9.10.16.1.2.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of events in which cells which should have been counted in the associated atmStatsEntry, but were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of cells or calls dropped; it is just the number of times this condition has been detected.

What is atmStatsControlDropEvents?

Counts the number of times the monitoring probe was forced to drop ATM cell data that should have been counted in the associated statistics entry, due to insufficient probe resources. A rising value signals that the probe is under resource pressure and may be producing incomplete statistics.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.10.16.1.2.1.1.1
snmpwalk -v2c -c public <target> ATM-RMON-MIB::atmStatsControlDropEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.10.16.1.2.1.1.1.1
snmpget -v2c -c public <target> ATM-RMON-MIB::atmStatsControlDropEvents.1

Start monitoring ATM network probes/monitoring devices with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ATM-RMON-MIB::atmStatsControlDropEvents OID value, configure state conditions and alerts, and monitor any ATM network probes/monitoring devices from a single console.

How to Use in IPNetwork Monitor

Select an ATM network probes/monitoring device 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 atmStatsControlDropEvents 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. The total number of events in which cells which should have been counted in the associated atmStatsEntry, but were dropped by the probe due to lack of resources. 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 between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.10ciscoExperimentCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.10.16atmRmonATM-RMON-MIB
1.3.6.1.4.1.9.10.16.1atmRmonMIBObjectsATM-RMON-MIB
1.3.6.1.4.1.9.10.16.1.2atmStatsATM-RMON-MIB
1.3.6.1.4.1.9.10.16.1.2.1atmStatsControlTableATM-RMON-MIB
1.3.6.1.4.1.9.10.16.1.2.1.1atmStatsControlEntryATM-RMON-MIB
1.3.6.1.4.1.9.10.16.1.2.1.1.1atmStatsControlDropEventsATM-RMON-MIB