RFC1271-MIB :: bufferControlMaxOctetsGranted

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsRFC1271-MIBbufferControlMaxOctetsGranted

bufferControlMaxOctetsGranted

Module: RFC1271-MIB

OID (symbolic): RFC1271-MIB::bufferControlMaxOctetsGranted

OID (numeric): 1.3.6.1.2.1.16.8.1.1.9

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The maximum number of octets that can be saved in this captureBuffer, including overhead. If this variable is -1, the capture buffer will save as many octets as possible.

When the bufferControlMaxOctetsRequested object is created or modified, the probe should set this object as closely to the requested value as is possible for the particular probe implementation and available resources. However, if the request object has the special value of -1, the probe must set this object to -1. The probe must not lower this value except as a result of a modification to the associated bufferControlMaxOctetsRequested object.

When this maximum number of octets is reached and a new packet is to be added to this capture buffer and the corresponding bufferControlFullAction is set to wrapWhenFull(2), enough of the oldest packets associated with this capture buffer shall be deleted by the agent so that the new packet can be added. If the corresponding bufferControlFullAction is set to lockWhenFull(1), the new packet shall be discarded. In either case, the probe must set bufferControlFullStatus to full(2).

When the value of this object changes to a value less than the current value, entries are deleted from the captureBufferTable associated with this bufferControlEntry. Enough of the oldest of these captureBufferEntries shall be deleted by the agent so that the number of octets used remains less than or equal to the new value of this object.

When the value of this object changes to a value greater than the current value, the number of associated captureBufferEntries may be allowed to grow.

What is bufferControlMaxOctetsGranted?

Actual maximum total octets, including overhead, that this capture buffer will hold, set as close as possible to bufferControlMaxOctetsRequested (or -1 if that was requested); when this limit is hit, either the oldest packets are wrapped out or new packets are dropped depending on bufferControlFullAction.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.8.1.1.9
snmpwalk -v2c -c public <target> RFC1271-MIB::bufferControlMaxOctetsGranted

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.16.8.1.1.9.1
snmpget -v2c -c public <target> RFC1271-MIB::bufferControlMaxOctetsGranted.1

Start monitoring vendor-neutral, standards-based RMON MIB, RMON-capable network probes and switches monitoring Ethernet with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1271-MIB::bufferControlMaxOctetsGranted OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based RMON MIB, RMON-capable network probes and switches monitoring Ethernet from a single console.

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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.16rmonLBHUB-BOOM-MIB
1.3.6.1.2.1.16.8captureLBHUB-BOOM-MIB
Numeric OIDNameModule
1.3.6.1.2.1.16.8.1bufferControlTableRFC1271-MIB
1.3.6.1.2.1.16.8.1.1bufferControlEntryRFC1271-MIB
1.3.6.1.2.1.16.8.1.1.9bufferControlMaxOctetsGrantedRFC1271-MIB