Alcatel-Lucent 7450 System Management Manual page 490

SNMP Trap Groups
notify-community community | security-name — Specifies the community string for snmpv1 or
community — The community string as required by the snmpv1 or snmpv2c trap receiver. The
security-name — The security-name as defined in the config>system>security>user context for
security-level {no-auth-no-privacy | auth-no-privacy | privacy} — Specifies the required
replay — Enable replay of missed events to target. If replay is applied to an SNMP trap target
Page 490
Pre-existing conditions are checked before the snmpv3SecurityName is accepted. These are:
• The user name must be configured.
• The v3 access group must be configured.
• The v3 notification view must be configured.
Default snmpv3
Values snmpv1, snmpv2c, snmpv3
snmpv2c or the snmpv3 security-name. If no notify-community is configured, then no alarms
nor traps will be issued for the trap destination. If the SNMP version is modified, the notify-
community must be changed to the proper form for the SNMP version.
community string can be an ASCII string up to 31 characters in length.
SNMP v3. The security-name can be an ASCII string up to 31 characters in length.
authentication and privacy levels required to access the views configured on this node when
configuring an snmpv3 trap receiver.
The keyword no-auth-no-privacy specifies no authentication and no privacy (encryption) are
required.
The keyword auth-no-privacy specifies authentication is required but no privacy (encryption) is
required. When this option is configured the security-name must be configured for authentica-
tion.
The keyword privacy specifies both authentication and privacy (encryption) is required. When
this option is configured the security-name must be configured for authentication and privacy.
Default no-auth-no-privacy. This parameter can only be configured if SNMPv3 is also con-
figured.
Values no-auth-no-privacy, auth-no-privacy, privacy
address, the address is monitored for reachability. Reachability is determined by whether or not
there is a route in the routing table by which the target address can be reached. Before sending a
trap to a target address, the SNMP module asks the PIP module if there is either an in-band or
out-of-band route to the target address. If there is no route to the SNMP target address, the
SNMP module saves the sequence-id of the first event that will be missed by the trap target.
When the routing table changes again so that there is now a route by which the SNMP target
address can be reached, the SNMP module replays (for example, retransmits) all events
generated to the SNMP notification log while the target address was removed from the route
table. Note that because of route table change convergence time, it is possible that one or more
events may be lost at the beginning or end of a replay sequence. The cold-start-wait and route-
recovery-wait timers under config>log>app-route-notifications can help reduce the probability
of lost events.
7450 ESS System Mangement Guide