| nlmConfigGlobalEntryLimit |
.1.3.6.1.2.1.92.1.1.1 |
|
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.
|
| nlmConfigGlobalAgeOut |
.1.3.6.1.2.1.92.1.1.2 |
|
The number of minutes a Notification SHOULD be kept in a log
before it is automatically removed.
If an application changes the value of nlmConfigGlobalAgeOut,
Notifications older than the new time MAY be discarded to meet the
new time.
A value of 0 means no age out.
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.
|
| nlmConfigLogEntry |
.1.3.6.1.2.1.92.1.1.3.1 |
|
A logging control entry. Depending on the entry's storage type
entries may be supplied by the system or created and deleted by
applications using nlmConfigLogEntryStatus.
|
| nlmStatsGlobalNotificationsLogged |
.1.3.6.1.2.1.92.1.2.1 |
|
The number of Notifications put into the nlmLogTable. This
counts a Notification once for each log entry, so a Notification
put into multiple logs is counted multiple times.
|
| nlmStatsGlobalNotificationsBumped |
.1.3.6.1.2.1.92.1.2.2 |
|
The number of log entries discarded to make room for a new entry
due to lack of resources or the value of nlmConfigGlobalEntryLimit
or nlmConfigLogEntryLimit. This does not include entries discarded
due to the value of nlmConfigGlobalAgeOut.
|
| nlmStatsLogEntry |
.1.3.6.1.2.1.92.1.2.3.1 |
|
A Notification log statistics entry.
|
| nlmLogEntry |
.1.3.6.1.2.1.92.1.3.1.1 |
|
A Notification log entry.
Entries appear in this table when Notifications occur and pass
filtering by nlmConfigLogFilterName and access control. They are
removed to make way for new entries due to lack of resources or
the values of nlmConfigGlobalEntryLimit, nlmConfigGlobalAgeOut, or
nlmConfigLogEntryLimit.
If adding an entry would exceed nlmConfigGlobalEntryLimit or system
resources in general, the oldest entry in any log SHOULD be removed
to make room for the new one.
If adding an entry would exceed nlmConfigLogEntryLimit the oldest
entry in that log SHOULD be removed to make room for the new one.
Before the managed system puts a locally-generated Notification
into a non-null-named log it assures that the creator of the log
has access to the information in the Notification. If not it
does not log that Notification in that log.
|
| nlmLogVariableEntry |
.1.3.6.1.2.1.92.1.3.2.1 |
|
A Notification log entry variable.
Entries appear in this table when there are variables in
the varbind list of a Notification in nlmLogTable.
|
| nlmLogName |
.1.3.6.1.2.1.92.1.1.3.1.1 |
|
The name of the log.
An implementation may allow multiple named logs, up to some
implementation-specific limit (which may be none). A
zero-length log name is reserved for creation and deletion by
the managed system, and MUST be used as the default log name by
systems that do not support named logs.
|
| nlmConfigLogFilterName |
.1.3.6.1.2.1.92.1.1.3.1.2 |
|
A value of snmpNotifyFilterProfileName as used as an index
into the snmpNotifyFilterTable in the SNMP Notification MIB,
specifying the locally or remotely originated Notifications
to be filtered out and not logged in this log.
A zero-length value or a name that does not identify an
existing entry in snmpNotifyFilterTable indicate no
Notifications are to be logged in this log.
|
| nlmConfigLogEntryLimit |
.1.3.6.1.2.1.92.1.1.3.1.3 |
|
The maximum number of notification entries that can be held in
nlmLogTable for this named log. A particular setting does not
guarantee that that much data can be held.
If an application changes the limit while there are
Notifications in the log, the oldest Notifications are discarded
to bring the log down to the new limit.
A value of 0 indicates 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.
|
| nlmConfigLogAdminStatus |
.1.3.6.1.2.1.92.1.1.3.1.4 |
|
Control to enable or disable the log without otherwise
disturbing the log's entry.
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.
|
| nlmConfigLogOperStatus |
.1.3.6.1.2.1.92.1.1.3.1.5 |
|
The operational status of this log:
disabled administratively disabled
operational administratively enabled and working
noFilter administratively enabled but either
nlmConfigLogFilterName is zero length
or does not name an existing entry in
snmpNotifyFilterTable
|
| nlmConfigLogStorageType |
.1.3.6.1.2.1.92.1.1.3.1.6 |
|
The storage type of this conceptual row.
|
| nlmConfigLogEntryStatus |
.1.3.6.1.2.1.92.1.1.3.1.7 |
|
Control for creating and deleting entries. Entries may be
modified while active.
For non-null-named logs, the managed system records the security
credentials from the request that sets nlmConfigLogStatus
to 'active' and uses that identity to apply access control to
the objects in the Notification to decide if that Notification
may be logged.
|
| nlmStatsLogNotificationsLogged |
.1.3.6.1.2.1.92.1.2.3.1.1 |
|
The number of Notifications put in this named log.
|
| nlmStatsLogNotificationsBumped |
.1.3.6.1.2.1.92.1.2.3.1.2 |
|
The number of log entries discarded from this named log to make
room for a new entry due to lack of resources or the value of
nlmConfigGlobalEntryLimit or nlmConfigLogEntryLimit. This does not
include entries discarded due to the value of
nlmConfigGlobalAgeOut.
|
| nlmLogIndex |
.1.3.6.1.2.1.92.1.3.1.1.1 |
|
A monotonically increasing integer for the sole purpose of
indexing entries within the named log. When it reaches the
maximum value, an extremely unlikely event, the agent wraps the
value back to 1.
|
| nlmLogTime |
.1.3.6.1.2.1.92.1.3.1.1.2 |
|
The value of sysUpTime when the entry was placed in the log. If
the entry occurred before the most recent management system
initialization this object value MUST be set to zero.
|
| nlmLogDateAndTime |
.1.3.6.1.2.1.92.1.3.1.1.3 |
|
The local date and time when the entry was logged, instantiated
only by systems that have date and time capability.
|
| nlmLogEngineID |
.1.3.6.1.2.1.92.1.3.1.1.4 |
|
The identification of the SNMP engine at which the Notification
originated.
If the log can contain Notifications from only one engine
or the Trap is in SNMPv1 format, this object is a zero-length
string.
|
| nlmLogEngineTAddress |
.1.3.6.1.2.1.92.1.3.1.1.5 |
|
The transport service address of the SNMP engine from which the
Notification was received, formatted according to the corresponding
value of nlmLogEngineTDomain. This is used to identify the source
of an SNMPv1 trap, since an nlmLogEngineId cannot be extracted
from the SNMPv1 trap pdu.
This object MUST always be instantiated, even if the log
can contain Notifications from only one engine.
Please be aware that the nlmLogEngineTAddress may not uniquely
identify the SNMP engine from which the Notification was received.
For example, if an SNMP engine uses DHCP or NAT to obtain
ip addresses, the address it uses may be shared with other
network devices, and hence will not uniquely identify the
SNMP engine.
|
| nlmLogEngineTDomain |
.1.3.6.1.2.1.92.1.3.1.1.6 |
|
Indicates the kind of transport service by which a Notification
was received from an SNMP engine. nlmLogEngineTAddress contains
the transport service address of the SNMP engine from which
this Notification was received.
Possible values for this object are presently found in the
Transport Mappings for SNMPv2 document (RFC 1906 [8]).
|
| nlmLogContextEngineID |
.1.3.6.1.2.1.92.1.3.1.1.7 |
|
If the Notification was received in a protocol which has a
contextEngineID element like SNMPv3, this object has that value.
Otherwise its value is a zero-length string.
|
| nlmLogContextName |
.1.3.6.1.2.1.92.1.3.1.1.8 |
|
The name of the SNMP MIB context from which the Notification came.
For SNMPv1 Traps this is the community string from the Trap.
|
| nlmLogNotificationID |
.1.3.6.1.2.1.92.1.3.1.1.9 |
|
The NOTIFICATION-TYPE object identifier of the Notification that
occurred.
|
| nlmLogVariableIndex |
.1.3.6.1.2.1.92.1.3.2.1.1 |
|
A monotonically increasing integer, starting at 1 for a given
nlmLogIndex, for indexing variables within the logged
Notification.
|
| nlmLogVariableID |
.1.3.6.1.2.1.92.1.3.2.1.2 |
|
The variable's object identifier.
|
| nlmLogVariableValueType |
.1.3.6.1.2.1.92.1.3.2.1.3 |
|
The type of the value. One and only one of the value
objects that follow must be instantiated, based on this type.
|
| nlmLogVariableCounter32Val |
.1.3.6.1.2.1.92.1.3.2.1.4 |
|
The value when nlmLogVariableType is 'counter32'.
|
| nlmLogVariableUnsigned32Val |
.1.3.6.1.2.1.92.1.3.2.1.5 |
|
The value when nlmLogVariableType is 'unsigned32'.
|
| nlmLogVariableTimeTicksVal |
.1.3.6.1.2.1.92.1.3.2.1.6 |
|
The value when nlmLogVariableType is 'timeTicks'.
|
| nlmLogVariableInteger32Val |
.1.3.6.1.2.1.92.1.3.2.1.7 |
|
The value when nlmLogVariableType is 'integer32'.
|
| nlmLogVariableOctetStringVal |
.1.3.6.1.2.1.92.1.3.2.1.8 |
|
The value when nlmLogVariableType is 'octetString'.
|
| nlmLogVariableIpAddressVal |
.1.3.6.1.2.1.92.1.3.2.1.9 |
|
The value when nlmLogVariableType is 'ipAddress'.
Although this seems to be unfriendly for IPv6, we
have to recognize that there are a number of older
MIBs that do contain an IPv4 format address, known
as IpAddress.
IPv6 addresses are represented using TAddress or
InetAddress, and so the underlying datatype is
OCTET STRING, and their value would be stored in
the nlmLogVariableOctetStringVal column.
|
| nlmLogVariableOidVal |
.1.3.6.1.2.1.92.1.3.2.1.10 |
|
The value when nlmLogVariableType is 'objectId'.
|
| nlmLogVariableCounter64Val |
.1.3.6.1.2.1.92.1.3.2.1.11 |
|
The value when nlmLogVariableType is 'counter64'.
|
| nlmLogVariableOpaqueVal |
.1.3.6.1.2.1.92.1.3.2.1.12 |
|
The value when nlmLogVariableType is 'opaque'.
|
