TPLINK-SNMPRMON-MIB :: tpSnmpRmonHistoryDataDropEvents

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TPLINK-SNMPRMON-MIB › tpSnmpRmonHistoryDataDropEvents

tpSnmpRmonHistoryDataDropEvents

Module: TPLINK-SNMPRMON-MIB

OID (symbolic): TPLINK-SNMPRMON-MIB::tpSnmpRmonHistoryDataDropEvents

OID (numeric): 1.3.6.1.4.1.11863.6.32.1.2.2.2.1.4

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.

What is tpSnmpRmonHistoryDataDropEvents?

Number of times during this sampling interval that the switch dropped packets due to lack of resources; counts occurrences of the condition, not the packets themselves.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11863.6.32.1.2.2.2.1.4
snmpwalk -v2c -c public <target> TPLINK-SNMPRMON-MIB::tpSnmpRmonHistoryDataDropEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11863.6.32.1.2.2.2.1.4.1
snmpget -v2c -c public <target> TPLINK-SNMPRMON-MIB::tpSnmpRmonHistoryDataDropEvents.1

Start monitoring TP-Link managed switches (RMON stats/history/alarm-threshold status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TPLINK-SNMPRMON-MIB::tpSnmpRmonHistoryDataDropEvents OID value, configure state conditions and alerts, and monitor any TP-Link managed switches (RMON stats/history/alarm-threshold status) from a single console.

How to Use in IPNetwork Monitor

Select a TP-Link managed switch (RMON stats/history/alarm-threshold status) 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 tpSnmpRmonHistoryDataDropEvents 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 packets were dropped by the probe due to lack of resources during this sampling interval. 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 (10 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.11863tplinkTPLINK-MIB
1.3.6.1.4.1.11863.6tplinkMgmtTPLINK-MIB
1.3.6.1.4.1.11863.6.32tplinkSnmpMIBTPLINK-SNMP-MIB
1.3.6.1.4.1.11863.6.32.1tplinkSnmpMIBObjectsTPLINK-SNMP-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11863.6.32.1.2tpSnmpRmonControlTPLINK-SNMPRMON-MIB
1.3.6.1.4.1.11863.6.32.1.2.2tpSnmpRmonHistoryCtrlTPLINK-SNMPRMON-MIB
1.3.6.1.4.1.11863.6.32.1.2.2.2tpSnmpRmonHistoryDataTableTPLINK-SNMPRMON-MIB
1.3.6.1.4.1.11863.6.32.1.2.2.2.1tpSnmpRmonHistoryDataEntryTPLINK-SNMPRMON-MIB
1.3.6.1.4.1.11863.6.32.1.2.2.2.1.4tpSnmpRmonHistoryDataDropEventsTPLINK-SNMPRMON-MIB