BIANCA-BRICK-MIB :: biboAdmSyslogMaxEntries

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsBIANCA-BRICK-MIBbiboAdmSyslogMaxEntries

biboAdmSyslogMaxEntries

Module: BIANCA-BRICK-MIB

OID (symbolic): BIANCA-BRICK-MIB::biboAdmSyslogMaxEntries

OID (numeric): 1.3.6.1.4.1.272.4.1.11

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: Maximum Number of syslog messages stored in memory.

What is biboAdmSyslogMaxEntries?

Maximum Number of syslog messages stored in memory. The biboAdmSyslogMaxEntries directs where system log messages should be sent for centralized monitoring. For example, all authentication events go to your central syslog server at 10.0.0.50.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.272.4.1.11
snmpwalk -v2c -c public <target> BIANCA-BRICK-MIB::biboAdmSyslogMaxEntries

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.272.4.1.11.1
snmpget -v2c -c public <target> BIANCA-BRICK-MIB::biboAdmSyslogMaxEntries.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.4.1.272.4.1.11.1 i <value>

Start monitoring bintec BIANCA/BRICK ISDN/VPN routers (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BIANCA-BRICK-MIB::biboAdmSyslogMaxEntries OID value, configure state conditions and alerts, and monitor any bintec BIANCA/BRICK ISDN/VPN routers (legacy) 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.272bintecBIANCA-BOX-ISDN-MIB
1.3.6.1.4.1.272.4biboBIANCA-BOX-ISDN-MIB
Numeric OIDNameModule
1.3.6.1.4.1.272.4.1adminBIANCA-BRICK-MIB
1.3.6.1.4.1.272.4.1.11biboAdmSyslogMaxEntriesBIANCA-BRICK-MIB