1. Network Management Specification
8000-A2-GB30-30
June 2004
91
8.4.3.2
SNMP-NOTIFICATION-MIB (RFC 3413)
This MIB allows the SNMP managers to configure notification recipients. The MIB is
composed of the following tables:
8.4.3.2.1
snmpNotifyTable
The SNMP agent will be able to generate unconfirmed (TRAPS) using the SNMPv1 or
SNMPv2 message format. Additionally it will be able to generate confirmed (INFORM)
notifications using the SNMPv2 message format.ation. Notifications will be sent out with-
out data encryption.
The following are the default entries in the snmpNotifyTable
:
8.4.3.2.2
Configuring a trap manager:
A remote SNMP entity (manager) can configure trap recipients by creating new entries in
the snmpTargetAddrTable with the IP address, Port and the respective notifyTag and tar-
getAddrParams depending on how users want notifications to be generated. The following
is an example of a configured trap manager in snmpTargetParams:
Table 1-109. SNMP-NOTIFICATION-MIB mib objects
Object
Supported
Comments
snmpNotifyTable
read-only
This table contains default entries
(templates) for the types of notifications
that can be sent. These templates are to be
used for:
a) sending SNMPv1 traps.
b) sending SNMPv2 traps.
c) sending SNMPv2 inform.
snmpNotifyFilterTable
not supported filtering of traps are not required
snmpNotifyFilterProfileTable
not supported filtering of traps are not required
Table 1-110. Default entries in snmpNotifyTable
snmpNotifyName snmpNotifyTag
snmpNotifyType Comments
“template-trap”
“template-trap”
trap
used for v1/v2
unconfirmed traps.
“template-confirm”
“template-confirm”
inform
used for v2 confirmed
traps.
Table 1-111. Example of a trap manager configured in snmpTargetAddrTable
Name
TDomain
TAddress
retryCount
timeout
TagList
TargetAddrParams
“v1-graysnapper”
UDP
1.1.1.1, 162
3
100
“template-trap”
“template-target-params-v1”