NOTIFICATION-LOG-MIB

All MIBs › NOTIFICATION-LOG-MIB

Organization: IETF Distributed Management Working Group

Last Updated: 2000-11-27

Category: Alarm and Event Management

Description: Defines managed objects for logging SNMP notification PDUs, allowing applications to review past notifications and reconstruct event history.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring NOTIFICATION-LOG-MIB with a free 30-day trial of IPNetwork Monitor.

What Is NOTIFICATION-LOG-MIB?

NOTIFICATION-LOG-MIB is an IETF standards-track SNMP MIB module that defines a mechanism for an SNMP agent to log notifications (traps and informs) it generates or forwards, independent of any particular vendor's hardware. It exposes data organized around log configuration (global entry limits, age-out policy, filter names, per-log admin/operational status, storage type) and log statistics (counts of notifications logged globally and per log), plus the stored log entries referencing the original notification's varbinds and timestamp. Because it stores a historical record of events, it is used mainly to monitor software-level status and event history rather than physical hardware: administrators check nlmConfigLogOperStatus to confirm logging is active, watch entry limits and age-out to see whether logs are silently overflowing or discarding data prematurely, and reconstruct a timeline of fault/status events on the device. It has no dependency on hardware-specific MIBs but is typically layered on top of the SNMPv3 notification/target MIBs (SNMP-TARGET-MIB, SNMP-NOTIFICATION-MIB) that actually generate the events it logs. It is deployed on any SNMP-capable network device or management station that needs an audit trail of trap/inform activity retrievable after a live trap has already scrolled past. Engineers implementing or auditing this functionality typically reference the NOTIFICATION-LOG-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in NOTIFICATION-LOG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

vendor-neutral, standards-based MIB, not tied to a specific manufacturer
any SNMP-capable network device or management station

Monitoring Examples

An administrator polls nlmConfigLogTable/nlmConfigLogEntry to confirm a named log (nlmLogName) has nlmConfigLogAdminStatus enabled and nlmConfigLogOperStatus reporting active, then checks nlmConfigLogEntryLimit against nlmStatsGlobalNotificationsLogged to see if the log is nearing capacity and about to discard older entries per nlmConfigGlobalAgeOut. A rising nlmStatsGlobalNotificationsLogged count with no operator awareness can reveal a device generating an unusual flood of traps (e.g., a flapping interface) that would otherwise go unnoticed between polls.

What Can Be Monitored

notification log admin/operational status
log entry limit and age-out policy
total notifications logged
log filter configuration
log storage type
historical trap/inform event records

Imported Objects

From SNMP-FRAMEWORK-MIB

SnmpAdminString
SnmpEngineID

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Counter64
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE
Opaque
TimeTicks
Unsigned32
mib-2

From SNMPv2-TC

DateAndTime
RowStatus
StorageType
TAddress
TDomain
TimeStamp

How to Use in IPNetwork Monitor

Example using nlmStatsGlobalNotificationsLogged OID:

Select a device implementing NOTIFICATION-LOG-MIB as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type nlmStatsGlobalNotificationsLogged into the Find box to locate it in the OID tree, then select it and click OK. The number of Notifications put into the nlmLogTable. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in notifications), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
notificationLogMIB	1.3.6.1.2.1.92			The MIB module for logging SNMP Notifications, that is, Traps and Informs.
notificationLogMIBObjects	1.3.6.1.2.1.92.1
nlmConfig	1.3.6.1.2.1.92.1.1
U32 nlmConfigGlobalEntryLimit	1.3.6.1.2.1.92.1.1.1	Unsigned32	read-write	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.
U32 nlmConfigGlobalAgeOut	1.3.6.1.2.1.92.1.1.2	Unsigned32	read-write	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.
nlmConfigLogTable	1.3.6.1.2.1.92.1.1.3		not-accessible	A table of logging control entries.
nlmConfigLogEntry	1.3.6.1.2.1.92.1.1.3.1		not-accessible	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.
STR nlmLogName	1.3.6.1.2.1.92.1.1.3.1.1	SnmpAdminString	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.
STR nlmConfigLogFilterName	1.3.6.1.2.1.92.1.1.3.1.2	SnmpAdminString	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.
U32 nlmConfigLogEntryLimit	1.3.6.1.2.1.92.1.1.3.1.3	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.
INT nlmConfigLogAdminStatus	1.3.6.1.2.1.92.1.1.3.1.4	INTEGER	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.
INT nlmConfigLogOperStatus	1.3.6.1.2.1.92.1.1.3.1.5	INTEGER	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
STO nlmConfigLogStorageType	1.3.6.1.2.1.92.1.1.3.1.6	StorageType	read-create	The storage type of this conceptual row.
ROW nlmConfigLogEntryStatus	1.3.6.1.2.1.92.1.1.3.1.7	RowStatus	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.
nlmStats	1.3.6.1.2.1.92.1.2
C32 nlmStatsGlobalNotificationsLoggedEx	1.3.6.1.2.1.92.1.2.1	Counter32	read-only	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.
C32 nlmStatsGlobalNotificationsBumped	1.3.6.1.2.1.92.1.2.2	Counter32	read-only	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.
nlmStatsLogTable	1.3.6.1.2.1.92.1.2.3		not-accessible	A table of Notification log statistics entries.
nlmStatsLogEntry	1.3.6.1.2.1.92.1.2.3.1		not-accessible	A Notification log statistics entry.
C32 nlmStatsLogNotificationsLogged	1.3.6.1.2.1.92.1.2.3.1.1	Counter32	read-only	The number of Notifications put in this named log.
C32 nlmStatsLogNotificationsBumped	1.3.6.1.2.1.92.1.2.3.1.2	Counter32	read-only	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.
nlmLog	1.3.6.1.2.1.92.1.3
nlmLogTable	1.3.6.1.2.1.92.1.3.1		not-accessible	A table of Notification log entries. It is an implementation-specific matter whether entries in this table are preserved across initializations of the management system. In general one would expect that they are not. Note that keeping entries across initializations of the management system leads to some confusion with counters and TimeStamps, since both of those are based on sysUpTime, which resets on management initialization. In this situation, counters apply only after the reset and nlmLogTime for entries made before the reset MUST be set to 0.
nlmLogEntry	1.3.6.1.2.1.92.1.3.1.1		not-accessible	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.
U32 nlmLogIndex	1.3.6.1.2.1.92.1.3.1.1.1	Unsigned32	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.
TIM nlmLogTime	1.3.6.1.2.1.92.1.3.1.1.2	TimeStamp	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.
DAT nlmLogDateAndTime	1.3.6.1.2.1.92.1.3.1.1.3	DateAndTime	read-only	The local date and time when the entry was logged, instantiated only by systems that have date and time capability.
SNM nlmLogEngineID	1.3.6.1.2.1.92.1.3.1.1.4	SnmpEngineID	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.
ADR nlmLogEngineTAddress	1.3.6.1.2.1.92.1.3.1.1.5	TAddress	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.
TDO nlmLogEngineTDomain	1.3.6.1.2.1.92.1.3.1.1.6	TDomain	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]).
SNM nlmLogContextEngineID	1.3.6.1.2.1.92.1.3.1.1.7	SnmpEngineID	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.
STR nlmLogContextName	1.3.6.1.2.1.92.1.3.1.1.8	SnmpAdminString	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.
OID nlmLogNotificationID	1.3.6.1.2.1.92.1.3.1.1.9	OBJECT IDENTIFIER	read-only	The NOTIFICATION-TYPE object identifier of the Notification that occurred.
nlmLogVariableTable	1.3.6.1.2.1.92.1.3.2		not-accessible	A table of variables to go with Notification log entries.
nlmLogVariableEntry	1.3.6.1.2.1.92.1.3.2.1		not-accessible	A Notification log entry variable. Entries appear in this table when there are variables in the varbind list of a Notification in nlmLogTable.
U32 nlmLogVariableIndex	1.3.6.1.2.1.92.1.3.2.1.1	Unsigned32	not-accessible	A monotonically increasing integer, starting at 1 for a given nlmLogIndex, for indexing variables within the logged Notification.
OID nlmLogVariableID	1.3.6.1.2.1.92.1.3.2.1.2	OBJECT IDENTIFIER	read-only	The variable's object identifier.
INT nlmLogVariableValueType	1.3.6.1.2.1.92.1.3.2.1.3	INTEGER	read-only	The type of the value. One and only one of the value objects that follow must be instantiated, based on this type.
C32 nlmLogVariableCounter32Val	1.3.6.1.2.1.92.1.3.2.1.4	Counter32	read-only	The value when nlmLogVariableType is 'counter32'.
U32 nlmLogVariableUnsigned32Val	1.3.6.1.2.1.92.1.3.2.1.5	Unsigned32	read-only	The value when nlmLogVariableType is 'unsigned32'.
TIK nlmLogVariableTimeTicksVal	1.3.6.1.2.1.92.1.3.2.1.6	TimeTicks	read-only	The value when nlmLogVariableType is 'timeTicks'.
I32 nlmLogVariableInteger32Val	1.3.6.1.2.1.92.1.3.2.1.7	Integer32	read-only	The value when nlmLogVariableType is 'integer32'.
OCT nlmLogVariableOctetStringVal	1.3.6.1.2.1.92.1.3.2.1.8	OCTET STRING	read-only	The value when nlmLogVariableType is 'octetString'.
IP nlmLogVariableIpAddressVal	1.3.6.1.2.1.92.1.3.2.1.9	IpAddress	read-only	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.
OID nlmLogVariableOidVal	1.3.6.1.2.1.92.1.3.2.1.10	OBJECT IDENTIFIER	read-only	The value when nlmLogVariableType is 'objectId'.
C64 nlmLogVariableCounter64Val	1.3.6.1.2.1.92.1.3.2.1.11	Counter64	read-only	The value when nlmLogVariableType is 'counter64'.
OPA nlmLogVariableOpaqueVal	1.3.6.1.2.1.92.1.3.2.1.12	Opaque	read-only	The value when nlmLogVariableType is 'opaque'.
notificationLogMIBConformance	1.3.6.1.2.1.92.3
notificationLogMIBCompliances	1.3.6.1.2.1.92.3.1
notificationLogMIBCompliance	1.3.6.1.2.1.92.3.1.1			The compliance statement for entities which implement the Notification Log MIB.
notificationLogMIBGroups	1.3.6.1.2.1.92.3.2
notificationLogConfigGroup	1.3.6.1.2.1.92.3.2.1			Notification log configuration management.
notificationLogStatsGroup	1.3.6.1.2.1.92.3.2.2			Notification log statistics.
notificationLogLogGroup	1.3.6.1.2.1.92.3.2.3			Notification log data.
notificationLogDateGroup	1.3.6.1.2.1.92.3.2.4			Conditionally mandatory notification log data. This group is mandatory on systems that keep wall clock date and time and should not be implemented on systems that do not have a wall clock date.

RFC description

SNMP notification logging service for recording and retrieving trap and inform messages.

Start monitoring Vendor-neutral IETF standard (any SNMP-capable device, trap/inform logging) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download NOTIFICATION-LOG-MIB