SNMP-NOTIFICATION-MIB

All MIBs › SNMP-NOTIFICATION-MIB

Organization: IETF SNMPv3 Working Group

Last Updated: 2002-10-14

Category: SNMP Framework

Description: Defines objects for configuring notification originator applications, including selecting management targets and filtering which notifications are sent.

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

What Is SNMP-NOTIFICATION-MIB?

SNMP-NOTIFICATION-MIB is a vendor-neutral IETF standards MIB defined in RFC 3413, part of the SNMPv3 framework, that configures how an SNMP entity generates and sends notifications (traps/informs). It exposes configuration objects for selecting which management targets receive notifications and for filtering which notifications are actually sent, via the snmpNotifyTable and snmpNotifyFilterProfileTable. Reviewing the SNMP-NOTIFICATION-MIB OID list shows how snmpNotifyTable entries tie together with the filter profile table to form the full notification pipeline. Rather than reporting hardware or software status itself, it governs the notification pipeline that carries fault and status alerts—such as power supply failures, link down events, or software errors—from the agent to management stations, so its correct configuration is essential for any device's alerting to function at all. It is tightly coupled to the SNMP-TARGET-MIB (which defines the actual target addresses referenced by snmpNotifyTag) and to SNMP-FRAMEWORK-MIB for VACM/security context. It is deployed on essentially every SNMPv3-capable device—routers, switches, servers, and appliances—wherever trap/inform delivery needs to be configured or audited.

IPNetwork Monitor allows you to monitor SNMP objects defined in SNMP-NOTIFICATION-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 SNMPv3-capable network device, server, or appliance

Monitoring Examples

An admin would inspect snmpNotifyTable/snmpNotifyEntry rows to confirm that snmpNotifyName entries have the correct snmpNotifyTag (linking to SNMP-TARGET-MIB target addresses) and snmpNotifyType set to trap or inform. Checking snmpNotifyFilterProfileTable and snmpNotifyFilterProfileName reveals whether a filter profile is unexpectedly suppressing notifications, a common cause of "traps configured but never received" incidents. snmpNotifyRowStatus can be polled to verify a notification entry is active (value 1, active) rather than left notInService after a misconfigured change.

What Can Be Monitored

configured notification targets
notification type (trap vs. inform)
notification filter profiles
notification entry row status
storage type of notify entries

Imported Objects

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMP-TARGET-MIB

SnmpTagValue
snmpTargetParamsName	OBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE
snmpModules

From SNMPv2-TC

RowStatus
StorageType

OIDs

OID symbolic	OID numeric	Type	Access	Description
snmpNotificationMIB	1.3.6.1.6.3.13			This MIB module defines MIB objects which provide mechanisms to remotely configure the parameters used by an SNMP entity for the generation of notifications. Copyright (C) The Internet Society (2002). This version of this MIB module is part of RFC 3413; see the RFC itself for full legal notices.
snmpNotifyBasicCompliance	1.3.6.1.6.3.13.3.1.1			The compliance statement for minimal SNMP entities which implement only SNMP Unconfirmed-Class notifications and read-create operations on only the snmpTargetAddrTable.
snmpNotifyBasicFiltersCompliance	1.3.6.1.6.3.13.3.1.2			The compliance statement for SNMP entities which implement SNMP Unconfirmed-Class notifications with filtering, and read-create operations on all related tables.
snmpNotifyCompliances	1.3.6.1.6.3.13.3.1
snmpNotifyConformance	1.3.6.1.6.3.13.3
snmpNotifyEntry	1.3.6.1.6.3.13.1.1.1		not-accessible	An entry in this table selects a set of management targets which should receive notifications, as well as the type of notification which should be sent to each selected management target. Entries in the snmpNotifyTable are created and deleted using the snmpNotifyRowStatus object.
snmpNotifyFilterEntry	1.3.6.1.6.3.13.1.3.1		not-accessible	An element of a filter profile. Entries in the snmpNotifyFilterTable are created and deleted using the snmpNotifyFilterRowStatus object.
snmpNotifyFilterGroup	1.3.6.1.6.3.13.3.2.2			A collection of objects providing remote configuration of notification filters.
OCT snmpNotifyFilterMask	1.3.6.1.6.3.13.1.3.1.2	OCTET STRING	read-create	The bit mask which, in combination with the corresponding instance of snmpNotifyFilterSubtree, defines a family of subtrees which are included in or excluded from the filter profile. Each bit of this bit mask corresponds to a sub-identifier of snmpNotifyFilterSubtree, with the most significant bit of the i-th octet of this octet string value (extended if necessary, see below) corresponding to the (8i - 7)-th sub-identifier, and the least significant bit of the i-th octet of this octet string corresponding to the (8i)-th sub-identifier, where i is in the range 1 through 16. Each bit of this bit mask specifies whether or not the corresponding sub-identifiers must match when determining if an OBJECT IDENTIFIER matches this family of filter subtrees; a '1' indicates that an exact match must occur; a '0' indicates 'wild card', i.e., any sub-identifier value matches. Thus, the OBJECT IDENTIFIER X of an object instance is contained in a family of filter subtrees if, for each sub-identifier of the value of snmpNotifyFilterSubtree, either: the i-th bit of snmpNotifyFilterMask is 0, or the i-th sub-identifier of X is equal to the i-th sub-identifier of the value of snmpNotifyFilterSubtree. If the value of this bit mask is M bits long and there are more than M sub-identifiers in the corresponding instance of snmpNotifyFilterSubtree, then the bit mask is extended with 1's to be the required length. Note that when the value of this object is the zero-length string, this extension rule results in a mask of all-1's being used (i.e., no 'wild card'), and the family of filter subtrees is the one subtree uniquely identified by the corresponding instance of snmpNotifyFilterSubtree.
snmpNotifyFilterProfileEntry	1.3.6.1.6.3.13.1.2.1		not-accessible	An entry in this table indicates the name of the filter profile to be used when generating notifications using the corresponding entry in the snmpTargetParamsTable. Entries in the snmpNotifyFilterProfileTable are created and deleted using the snmpNotifyFilterProfileRowStatus object.
STR snmpNotifyFilterProfileName	1.3.6.1.6.3.13.1.2.1.1	SnmpAdminString	read-create	The name of the filter profile to be used when generating notifications using the corresponding entry in the snmpTargetAddrTable.
ROW snmpNotifyFilterProfileRowStatus	1.3.6.1.6.3.13.1.2.1.3	RowStatus	read-create	The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the snmpNotifyFilterProfileRowStatus column is 'notReady'. In particular, a newly created row cannot be made active until the corresponding instance of snmpNotifyFilterProfileName has been set.
STO snmpNotifyFilterProfileStorType	1.3.6.1.6.3.13.1.2.1.2	StorageType	read-create	The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
snmpNotifyFilterProfileTable	1.3.6.1.6.3.13.1.2		not-accessible	This table is used to associate a notification filter profile with a particular set of target parameters.
ROW snmpNotifyFilterRowStatus	1.3.6.1.6.3.13.1.3.1.5	RowStatus	read-create	The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5).
STO snmpNotifyFilterStorageType	1.3.6.1.6.3.13.1.3.1.4	StorageType	read-create	The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
OID snmpNotifyFilterSubtree	1.3.6.1.6.3.13.1.3.1.1	OBJECT IDENTIFIER	not-accessible	The MIB subtree which, when combined with the corresponding instance of snmpNotifyFilterMask, defines a family of subtrees which are included in or excluded from the filter profile.
snmpNotifyFilterTable	1.3.6.1.6.3.13.1.3		not-accessible	The table of filter profiles. Filter profiles are used to determine whether particular management targets should receive particular notifications. When a notification is generated, it must be compared with the filters associated with each management target which is configured to receive notifications, in order to determine whether it may be sent to each such management target. A more complete discussion of notification filtering can be found in section 6. of [SNMP-APPL].
INT snmpNotifyFilterType	1.3.6.1.6.3.13.1.3.1.3	INTEGER	read-create	This object indicates whether the family of filter subtrees defined by this entry are included in or excluded from a filter. A more detailed discussion of the use of this object can be found in section 6. of [SNMP-APPL].
snmpNotifyFullCompliance	1.3.6.1.6.3.13.3.1.3			The compliance statement for SNMP entities which either implement only SNMP Confirmed-Class notifications, or both SNMP Unconfirmed-Class and Confirmed-Class notifications, plus filtering and read-create operations on all related tables.
snmpNotifyGroup	1.3.6.1.6.3.13.3.2.1			A collection of objects for selecting which management targets are used for generating notifications, and the type of notification to be generated for each selected management target.
snmpNotifyGroups	1.3.6.1.6.3.13.3.2
STR snmpNotifyName	1.3.6.1.6.3.13.1.1.1.1	SnmpAdminString	not-accessible	The locally arbitrary, but unique identifier associated with this snmpNotifyEntry.
snmpNotifyObjects	1.3.6.1.6.3.13.1
ROW snmpNotifyRowStatus	1.3.6.1.6.3.13.1.1.1.5	RowStatus	read-create	The status of this conceptual row. To create a row in this table, a manager must set this object to either createAndGo(4) or createAndWait(5).
STO snmpNotifyStorageType	1.3.6.1.6.3.13.1.1.1.4	StorageType	read-create	The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
snmpNotifyTable	1.3.6.1.6.3.13.1.1		not-accessible	This table is used to select management targets which should receive notifications, as well as the type of notification which should be sent to each selected management target.
SNM snmpNotifyTag	1.3.6.1.6.3.13.1.1.1.2	SnmpTagValue	read-create	This object contains a single tag value which is used to select entries in the snmpTargetAddrTable. Any entry in the snmpTargetAddrTable which contains a tag value which is equal to the value of an instance of this object is selected. If this object contains a value of zero length, no entries are selected.
INT snmpNotifyType	1.3.6.1.6.3.13.1.1.1.3	INTEGER	read-create	This object determines the type of notification to be generated for entries in the snmpTargetAddrTable selected by the corresponding instance of snmpNotifyTag. This value is only used when generating notifications, and is ignored when using the snmpTargetAddrTable for other purposes. If the value of this object is trap(1), then any messages generated for selected rows will contain Unconfirmed-Class PDUs. If the value of this object is inform(2), then any messages generated for selected rows will contain Confirmed-Class PDUs. Note that if an SNMP entity only supports generation of Unconfirmed-Class PDUs (and not Confirmed-Class PDUs), then this object may be read-only.

FAQ

What does SNMP-NOTIFICATION-MIB actually configure on an SNMPv3-capable device?
It defines the snmpNotifyTable for selecting which management targets receive notifications and the snmpNotifyFilterProfileTable for filtering which notifications are actually sent, forming the configuration for the device's trap/inform generation pipeline.

Why is correctly configuring SNMP-NOTIFICATION-MIB important even though it doesn't report hardware status itself?
Because it governs the notification pipeline that carries fault and status alerts — like power supply failures or link-down events — from the agent to the management station, so if it's misconfigured, those alerts simply never arrive regardless of what the device is actually experiencing.

RFC description

RFC 3413 MIB defining SNMP notification management, specifying targets and filtering for trap generation.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device/server/appliance (notification-originator configuration) 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 SNMP-NOTIFICATION-MIB

What Is SNMP-NOTIFICATION-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

FAQ

RFC description