JACOBS-RPL-MIB :: rplMemOverflows

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsJACOBS-RPL-MIBrplMemOverflows

rplMemOverflows

Module: JACOBS-RPL-MIB

OID (symbolic): JACOBS-RPL-MIB::rplMemOverflows

OID (numeric): 1.3.6.1.4.1.30982.1.2.1.8.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of memory allocation failures (e.g., routing table

overflows).

What is rplMemOverflows?

Counts memory allocation failures, such as routing table overflows, encountered by the RPL implementation. An admin watches this counter to catch a low-power node running out of memory to track its growing set of routes or neighbors.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.30982.1.2.1.8.1
snmpwalk -v2c -c public <target> JACOBS-RPL-MIB::rplMemOverflows

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.30982.1.2.1.8.1.1
snmpget -v2c -c public <target> JACOBS-RPL-MIB::rplMemOverflows.1

Start monitoring Low-power/lossy wireless mesh node (IoT/sensor device, RPL routing) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the JACOBS-RPL-MIB::rplMemOverflows OID value, configure state conditions and alerts, and monitor any Low-power/lossy wireless mesh node (IoT/sensor device, RPL routing) from a single console.

How to Use in IPNetwork Monitor

Select a Low-power/lossy wireless mesh node (IoT/sensor device, RPL routing) 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 rplMemOverflows into the Find box to locate it in the OID tree, then select it and click OK. The number of memory allocation failures (e.g., routing table overflows). 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.30982jacobsJACOBS-SMI
1.3.6.1.4.1.30982.1cndsJACOBS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.30982.1.2rplMibJACOBS-RPL-MIB
1.3.6.1.4.1.30982.1.2.1rplObjectsJACOBS-RPL-MIB
1.3.6.1.4.1.30982.1.2.1.8rplStatsJACOBS-RPL-MIB
1.3.6.1.4.1.30982.1.2.1.8.1rplMemOverflowsJACOBS-RPL-MIB