syslogMsgTableMaxSize
SYSLOG-MSG-MIB ·
.1.3.6.1.2.1.192.1.1.1
Object
The maximum number of SYSLOG messages that may be held in
syslogMsgTable. A particular setting does not guarantee that
there is sufficient memory available for the maximum number
of table entries indicated by this object. A value of 0 means
no fixed limit.
If an application reduces the limit while there are SYSLOG
messages in the syslogMsgTable, the SYSLOG messages that are
in the syslogMsgTable for the longest time MUST be discarded
to bring the table down to the new limit.
The value of this object should be kept in nonvolatile
memory.
Context
- MIB
- SYSLOG-MSG-MIB
- OID
.1.3.6.1.2.1.192.1.1.1- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- syslogMsgControl
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'SYSLOG-MSG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SYSLOG-MSG-MIB::syslogMsgTableMaxSize.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'SYSLOG-MSG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SYSLOG-MSG-MIB::syslogMsgTableMaxSize'
Syntax
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Conformance
Member of
Compliance refinements
syslogMsgReadOnlyCompliance
readonly
Write access is not required.