NOTIFICATION-LOG-MIB

1.3.6.1.2.1.92.1.1.1

nlmConfigGlobalEntryLimit

Unsigned32

Read-write

This object indicates the maximum number of notification entries that can be held in nlmLogTable in nlmLogNames. This value is not applicable for some particular settings.

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. Note 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.

Currently, the value ranges from 1 to 15000.

1.3.6.1.2.1.92.1.1.2

nlmConfigGlobalAgeOut

Unsigned32; The value can be 0 or any value ranging from 720 to 2160, in minutes. The default value is 1440 minutes.

Read-write

This object indicates 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.

Note 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.

When the object is set, the value varies so that the number of minutes is a multiple of 60. For example, if the time is set to 800, the value will change to 840 (14 hours).

Currently, the value can be 0 or any value ranging from 12 to 36, in hours.

1.3.6.1.2.1.92.1.2.1

nlmStatsGlobalNotificationsLogged

INTEGER (0..4294967295)

Read-only

This object indicates the number of notifications put into nlmLogTable. This counts a notification once for each log entry, so a notification put into multiple logs is counted multiple times.

Currently, this object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.2.2

nlmStatsGlobalNotificationsBumped

INTEGER (0..4294967295)

Read-only

This object indicates 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 the entries discarded due to the value of nlmConfigGlobalAgeOut.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.1.3.1.1

nlmLogName

SnmpAdminString (SIZE(0..32))

Not-accessible

This object indicates 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 the managed system to create and delete logs. The system can contain multiple named logs, whose number can be set.

The value ranges from 0 to 32.

This object is implemented as defined in the corresponding MIB files.

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

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.1.3.1.3

nlmConfigLogEntryLimit

unsigned32

Read-create

This object indicates the maximum number of notification entries that can be held in nlmLogTable for this named log. 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 are discarded to bring the log down to the new limit.

A value of 0 indicates no limit.

Note 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.

Currently, a maximum of 15,000 notification entries can be held in nlmLogTable, and the maximum access is read-only.

1.3.6.1.2.1.92.1.1.3.1.4

nlmConfigLogAdminStatus

INTEGER

{

enabled(1),

disabled(2)

}

Read-create

This object indicates that the status of the log (enable or disable) can be controlled. If the status of the log cannot be controlled, the log entity is affected.

Note that when there are multiple administrators, these administrators will try to set an object to different values, which may affect the reliability and completeness of data set by each manager.

Currently, the maximum 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 value of this object identifies the operating status of logs.

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

This object indicates the storage types of logs.

Currently, the value can only be other(1), volatile(2), nonVolatile(3), permanent(4), or readonly(5). and the maximum 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

This object controls the creation and deletion of 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.

Currently, the value can only be active(1), notInService(2), notReady(3), createAndGo(4), createAndWait(5), or destroy(6). and the maximum access is read-only.

1.3.6.1.2.1.92.1.2.3.1.1

nlmStatsLogNotificationsLogged

INTEGER (0..4294967295)

Read-only

This object indicates the total number of a kind of logs.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.2.3.1.2

nlmStatsLogNotificationsBumped

INTEGER (0..4294967295)

Read-only

This object indicates the number of discarded logs. Only the logs that are deleted for the creation of new logs in the situation that resources are insufficient or the number of logs reaches the threshold of nlmConfigGlobalEntryLImit or nlmConfigEntryLimit are recorded.

The logs that are aged according to nlmConfigGlobalAgeOut are excluded.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.1

nlmLogIndex

Unsigned32 (1..4294967295)

Not-accessible

This object indicates an incremental integer, which is used to index the named log. When the integer reaches the maximum value (an extremely unlikely event), the agent restore the value to 1.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.2

nlmLogTime

TimeTicks

Read-only

This object indicates the value of sysUpTime when an alarm is recorded in the log. If the log is created before the system initialization, this object value must be set to 0.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.3

nlmLogDateAndTime

OCTET STRING (SIZE (8 | 11))

Read-only

This object indicates the local date and time recorded by the system when the entry was logged in. This function is available only on the system that has the date and time capability.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.4

nlmLogEngineID

OCTET STRING (SIZE(5..32))

Read-only

This object indicates the ID of the SNMP engine where an alarm is generated. If the log can contain the alarm message from only one engine or the Trap is in SNMPv1 format, this object is a zero-length string.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.5

nlmLogEngineTAddress

OCTET STRING (SIZE (1..255))

Read-only

This object indicates 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.

Note 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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.6

nlmLogEngineTDomain

OBJECT IDENTIFIER

Read-only

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]).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.7

nlmLogContextEngineID

OCTET STRING (SIZE(5..32))

Read-only

This object indicates that if the received alarm packet, such as an SNMPv3 packet, carries a contextEngineID element, the value of this object is equal to the value of contextEngineID. Otherwise, the value of this object is a zero-length string.

This object is not supported in the current version, and the system will display a zero-length string.

1.3.6.1.2.1.92.1.3.1.1.8

nlmLogContextName

OCTET STRING (SIZE (0..255))

Read-only

The name of the SNMP MIB context from which the Notification came. For SNMPv1 Traps this is the community string from the Trap.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.1.1.9

nlmLogNotificationID

OBJECT IDENTIFIER

Read-only

This object indicates NOTIFICATION-TYPE object that generates alarms.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.1

nlmLogVariableIndex

Unsigned32 (1..4294967295)

Not-accessible

This object indicates an incremental integer.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.2

nlmLogVariableID

OBJECT IDENTIFIER

Read-only

This object indicates the OID of the log variable.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.3

nlmLogVariableValueType

INTEGER

{

counter32(1),

unsigned32(2),

timeTicks(3),

integer32(4),

ipAddress(5),

octetString(6),

objectId(7),

counter64(8),

opaque(9)

}

Read-only

The value of this object identifies the type of the log variable value.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.4

nlmLogVariableCounter32Val

INTEGER (0..4294967295)

Read-only

This object indicates the value of the log variable with the data structure as Counter 32.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.5

nlmLogVariableUnsigned32Val

INTEGER (0..4294967295)

Read-only

This object indicates the value of the log variable with the data structure as Unsigned 32.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.6

nlmLogVariableTimeTicksVal

INTEGER (0..4294967295)

Read-only

This object indicates the value of the log variable with the data structure as TimeTicks.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.7

nlmLogVariableInteger32Val

Integer32

Read-only

The value of this object identifies the value of the log variable with the data structure as Integer 32.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.8

nlmLogVariableOctetStringVal

OctetString

Read-only

This object indicates the value of the log variable with the data structure as OctetString.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.9

nlmLogVariableIpAddressVal

OCTET STRING (SIZE (4))

Read-only

This object indicates the value of the log variable with the data structure as IpAddress.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.10

nlmLogVariableOidVal

OBJECT IDENTIFIER

Read-only

This object indicates the value of the log variable with the data structure as OID.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.11

nlmLogVariableCounter64Val

INTEGER (0..18446744073709551615)

Read-only

This object indicates the value of the log variable with the data structure as Counter 64.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.92.1.3.2.1.12

nlmLogVariableOpaqueVal

OCTET STRING

Read-only

This object indicates the value of the log variable with the data structure as Opaque.

This object is implemented as defined in the corresponding MIB files.