BN-LOG-MESSAGE-MIB :: bnLogMsgBufferCurSize

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › BN-LOG-MESSAGE-MIB › bnLogMsgBufferCurSize

bnLogMsgBufferCurSize

Module: BN-LOG-MESSAGE-MIB

OID (symbolic): BN-LOG-MESSAGE-MIB::bnLogMsgBufferCurSize

OID (numeric): 1.3.6.1.4.1.45.1.6.16.1.1.3

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The current number of log messages in the volatile portion of the system log message facility. Messages that are classified as volatile are lost upon system reinitialization.

What is bnLogMsgBufferCurSize?

Reports the current count of volatile log messages stored in the system log buffer. These messages are held in RAM and will be lost if the device is restarted or reinitialized.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.1.6.16.1.1.3
snmpwalk -v2c -c public <target> BN-LOG-MESSAGE-MIB::bnLogMsgBufferCurSize

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.1.6.16.1.1.3.1
snmpget -v2c -c public <target> BN-LOG-MESSAGE-MIB::bnLogMsgBufferCurSize.1

Start monitoring Bay Networks/Nortel routers and switches (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BN-LOG-MESSAGE-MIB::bnLogMsgBufferCurSize OID value, configure state conditions and alerts, and monitor any Bay Networks/Nortel routers and switches (legacy) from a single console.

How to Use in IPNetwork Monitor

Select a Bay Networks/Nortel routers and switch (legacy) 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 bnLogMsgBufferCurSize into the Find box to locate it in the OID tree, then select it and click OK. The current number of log messages in the volatile portion of the system log message facility. 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 count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. 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.45synopticsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.1productsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.1.6series5000SYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.1.6.16bnLogMsgS5-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.1.6.16.1bnLogMsgMIBBN-LOG-MESSAGE-MIB
1.3.6.1.4.1.45.1.6.16.1.1bnLogMsgMIBObjectsBN-LOG-MESSAGE-MIB
1.3.6.1.4.1.45.1.6.16.1.1.3bnLogMsgBufferCurSizeBN-LOG-MESSAGE-MIB