nlmConfigGlobalEntryLimit
NOTIFICATION-LOG-MIB ·
.1.3.6.1.2.1.92.1.1.1
Object
The maximum number of notification entries that may be held
in nlmLogTable for all nlmLogNames added together. A particular
setting does not guarantee that much data can be held.
If an application changes the limit while there are
Notifications in the log, the oldest Notifications MUST be
discarded to bring the log down to the new limit - thus the
value of nlmConfigGlobalEntryLimit MUST take precedence over
the values of nlmConfigGlobalAgeOut and nlmConfigLogEntryLimit,
even if the Notification being discarded has been present for
fewer minutes than the value of nlmConfigGlobalAgeOut, or if
the named log has fewer entries than that specified in
nlmConfigLogEntryLimit.
A value of 0 means no limit.
Please be aware that contention between multiple managers
trying to set this object to different values MAY affect the
reliability and completeness of data seen by each manager.
Context
- MIB
- NOTIFICATION-LOG-MIB
- OID
.1.3.6.1.2.1.92.1.1.1- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- nlmConfig
- 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 'NOTIFICATION-LOG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'NOTIFICATION-LOG-MIB::nlmConfigGlobalEntryLimit.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'NOTIFICATION-LOG-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'NOTIFICATION-LOG-MIB::nlmConfigGlobalEntryLimit'
Syntax
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Conformance
Member of
Compliance refinements
range: 0..4294967295
Implementations may choose a limit and not allow it to be
changed or may enforce an upper or lower bound on the
limit.
changed or may enforce an upper or lower bound on the
limit.