A table of logging control entries.
The index of the table is nlmLogName.
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
---|---|---|---|---|---|
1.3.6.1.2.1.92.1.1.3.1.1 |
nlmLogName |
OCTET STRING{(0,32)} |
not-accessible |
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. |
The actually supported access is read-only. |
1.3.6.1.2.1.92.1.1.3.1.2 |
nlmConfigLogFilterName |
OCTET STRING{(0,32)} |
read-create |
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. |
The actually supported access is read-only. |
1.3.6.1.2.1.92.1.1.3.1.3 |
nlmConfigLogEntryLimit |
Unsigned32 |
read-create |
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. |
The actually supported access is read-only. |
1.3.6.1.2.1.92.1.1.3.1.4 |
nlmConfigLogAdminStatus |
INTEGER{enabled(1),disabled(2)} |
read-create |
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. |
The actually supported access is read-only. |
1.3.6.1.2.1.92.1.1.3.1.5 |
nlmConfigLogOperStatus |
INTEGER{disabled(1),operational(2),noFilter(3)} |
read-only |
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 |
This object is implemented as defined in the corresponding MIB files. |
1.3.6.1.2.1.92.1.1.3.1.6 |
nlmConfigLogStorageType |
INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)} |
read-create |
The storage type of this conceptual row. |
The actually supported access is read-only. |
1.3.6.1.2.1.92.1.1.3.1.7 |
nlmConfigLogEntryStatus |
INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)} |
read-create |
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. |
The actually supported access is read-only. |