Alcatel-Lucent 7450 System Management Manual page 489

A single snmp-trap-group log-id can have multiple trap-receivers. Each trap receiver can have
different operational parameters.
An address can be configured as a trap receiver more than once as long as a different port is used for
each instance.
To prevent resource limitations, only configure a maximum of 10 trap receivers.
Note that if the same trap-target name port port parameter value is specified in more than one
SNMP trap group, each trap destination should be configured with a different notify-community
value. This allows a trap receiving an application, such as NMS, to reconcile a separate event
sequence number stream for each router event log when multiple event logs are directed to the same
IP address and port destination.
The no form of the command removes the SNMP trap receiver from the SNMP trap group.
Default
No SNMP trap targets are defined.
Parameters name — Specifies the name of the trap target up to 28 characters in length.
address ip-address — The IP address of the trap receiver in dotted decimal notation. Only one IP
port port — The destination UDP port used for sending traps to the destination, expressed as a deci-
snmpv1 | snmpv2c | snmpv3 — Specifies the SNMP version format to use for traps sent to the trap
7450 ESS System Mangement Guide
• SNMP community name for SNMPv1 and SNMPv2c receivers.
• Security name and level for SNMPv3 trap receivers.
address destination can be specified per trap destination group.
Values
ipv4-address
mal integer. Only one port can be specified per trap-target statement. If multiple traps need to be
issued to the same address then multiple ports must be configured.
Default
162
Values 1 — 65535
receiver.
The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-
community must be configured for the proper SNMP community string that the trap receiver
expects to be present in alarms and traps messages. If the SNMP version is changed from
snmpv3 to snmpv1, then the notify-community parameter must be changed to reflect the com-
munity string rather than the security-name that is used by snmpv3.
The keyword snmpv2c selects the SNMP version 2c format. When specifying snmpv2c, the
notify-community must be configured for the proper SNMP community string that the trap
receiver expects to be present in alarms and traps messages. If the SNMP version is changed
from snmpv3 to snmpv2c, then the notify-community parameter must be changed to reflect the
community string rather than the security-name that is used by snmpv3.
The keyword snmpv3 selects the SNMP version 3 format. When specifying snmpv3, the notify-
community must be configured for the SNMP security-name. If the SNMP version is changed
from snmpv1 or snmpv2c to snmpv3, then the notify-community parameter must be changed
to reflect the security-name rather than the community string used by snmpv1 or snmpv2c.
a.b.c.d (host bits must be 0)
Event and Accounting Logs
Page 489