nlmLogTable

1.3.6.1.2.1.92.1.3.1.1.1

nlmLogIndex

Unsigned32{(1,4294967295)}

not-accessible

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.

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

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.

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{(8,8),(11,11)}

read-only

The local date and time when the entry was logged, instantiated

only by systems that have 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{(5,32)}

read-only

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.

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{(1,255)}

read-only

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.

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{(5,32)}

read-only

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.

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

1.3.6.1.2.1.92.1.3.1.1.8

nlmLogContextName

OCTET STRING{(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

The NOTIFICATION-TYPE object identifier of the Notification that

occurred.

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