UCD-SNMP-MIB :: memBuffer

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsUCD-SNMP-MIBmemBuffer

memBuffer

Module: UCD-SNMP-MIB

OID (symbolic): UCD-SNMP-MIB::memBuffer

OID (numeric): 1.3.6.1.4.1.2021.4.14

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The total amount of real or virtual memory currently allocated for use as memory buffers.

This object will not be implemented on hosts where the underlying operating system does not explicitly identify memory as specifically reserved for this purpose.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2021.4.14
snmpwalk -v2c -c public <target> UCD-SNMP-MIB::memBuffer

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2021.4.14.1
snmpget -v2c -c public <target> UCD-SNMP-MIB::memBuffer.1

Start monitoring Unix/Linux servers running the Net-SNMP (net-snmp/snmpd) agent (CPU/memory/disk/process-table status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the UCD-SNMP-MIB::memBuffer OID value, configure state conditions and alerts, and monitor any Unix/Linux servers running the Net-SNMP (net-snmp/snmpd) agent (CPU/memory/disk/process-table status) from a single console.

How to Use in IPNetwork Monitor

Select a Unix/Linux server running the Net-SNMP (net-snmp/snmpd) agent 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 memBuffer into the Find box to locate it in the OID tree, then select it and click OK. It reports the total amount of real or virtual memory currently allocated for use as memory buffers, in KB. 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 an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the value grows well beyond its normal baseline without leveling off, since continuously rising buffer allocation can indicate memory pressure. 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2021ucdavisUCD-SNMP-MIB
1.3.6.1.4.1.2021.4memoryUCD-SNMP-MIB
1.3.6.1.4.1.2021.4.14memBufferUCD-SNMP-MIB