| NlmStatsLogEntry |
|
| SEQUENCE |
|
|
|
| |
nlmStatsLogNotificationsLogged |
Counter32 |
|
| |
nlmStatsLogNotificationsBumped |
Counter32 |
|
| NlmLogVariableEntry |
|
| SEQUENCE |
|
|
|
| |
nlmLogVariableIndex |
Unsigned32 |
|
| |
nlmLogVariableID |
OBJECT IDENTIFIER |
|
| |
nlmLogVariableValueType |
INTEGER |
|
| |
nlmLogVariableCounter32Val |
Counter32 |
|
| |
nlmLogVariableUnsigned32Val |
Unsigned32 |
|
| |
nlmLogVariableTimeTicksVal |
TimeTicks |
|
| |
nlmLogVariableInteger32Val |
Integer32 |
|
| |
nlmLogVariableOctetStringVal |
OCTET STRING |
|
| |
nlmLogVariableIpAddressVal |
IpAddress |
|
| |
nlmLogVariableOidVal |
OBJECT IDENTIFIER |
|
| |
nlmLogVariableCounter64Val |
Counter64 |
|
| |
nlmLogVariableOpaqueVal |
OCTET STRING |
|
| 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. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
NlmConfigLogEntry |
|
|
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
|
|
| 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. |
| Status: current |
Access: read-create |
| OBJECT-TYPE |
|
|
|
| |
RowStatus |
|
|
| nlmStatsLogEntry |
1.3.6.1.2.1.92.1.2.3.1 |
| A Notification log statistics entry. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
NlmStatsLogEntry |
|
|
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
NlmLogEntry |
|
|
| 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]). |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TDomain |
|
|
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpEngineID |
|
|
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
SnmpAdminString |
|
|
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
NlmLogVariableEntry |
|
|
