BDCOM-MEMORY-POOL-MIB :: bdcomMemoryPoolUsed

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BDCOM-MEMORY-POOL-MIB › bdcomMemoryPoolUsed

bdcomMemoryPoolUsed

Module: BDCOM-MEMORY-POOL-MIB

OID (symbolic): BDCOM-MEMORY-POOL-MIB::bdcomMemoryPoolUsed

OID (numeric): 1.3.6.1.4.1.3320.9.48.1.1.1.5

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device.

What is bdcomMemoryPoolUsed?

Reports the number of bytes currently allocated and in use by applications from this memory pool. Monitoring this value alongside total pool size helps detect memory pressure or potential memory exhaustion on the device.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.3320.9.48.1.1.1.5
snmpwalk -v2c -c public <target> BDCOM-MEMORY-POOL-MIB::bdcomMemoryPoolUsed

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.3320.9.48.1.1.1.5.1
snmpget -v2c -c public <target> BDCOM-MEMORY-POOL-MIB::bdcomMemoryPoolUsed.1

Start monitoring BDCOM networking equipment (switches/routers) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BDCOM-MEMORY-POOL-MIB::bdcomMemoryPoolUsed OID value, configure state conditions and alerts, and monitor any BDCOM networking equipment (switches/routers) from a single console.

How to Use in IPNetwork Monitor

Select a BDCOM networking equipment (switches/routers) 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 bdcomMemoryPoolUsed 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. Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device. 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 Gauge32-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 bytes), 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 (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.3320bdcomBDCOM-SMI
1.3.6.1.4.1.3320.9bdMgmtBDCOM-SMI
Numeric OIDNameModule
1.3.6.1.4.1.3320.9.48bdcomMemoryPoolMIBBDCOM-MEMORY-POOL-MIB
1.3.6.1.4.1.3320.9.48.1bdcomMemoryPoolObjectsBDCOM-MEMORY-POOL-MIB
1.3.6.1.4.1.3320.9.48.1.1bdcomMemoryPoolTableBDCOM-MEMORY-POOL-MIB
1.3.6.1.4.1.3320.9.48.1.1.1bdcomMemoryPoolEntryBDCOM-MEMORY-POOL-MIB
1.3.6.1.4.1.3320.9.48.1.1.1.5bdcomMemoryPoolUsedBDCOM-MEMORY-POOL-MIB