Alcatel-Lucent 7705 SAR-8 System Management Manual page 277

The trap-target command is used to add or remove a trap receiver from an
operational parameters specified in the command include:
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.
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
snmpv1 | snmpv2c | snmpv3 — specifies the SNMP version format to use for traps sent to the trap
7705 SAR OS System Management Guide
• the IP address of the trap receiver
• the UDP port used to send the SNMP trap
• SNMP version
• SNMP community name for SNMPv1 and SNMPv2c receivers
• security name and level for SNMPv3 trap receivers
Note: 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 7705 SAR
event log when multiple event logs are directed to the same IP address and port
destination.
address destination can be specified per trap destination group.
Values 1.0.0.0 to 223.255.255.255
decimal integer. Only one port can be specified per trap-target statement. If multiple traps need
to be issued to the same address, multiple ports must be configured.
Default 162
Values
1 to 65535
receiver
The keyword snmpv1 selects the SNMP version 1 format. When specifying snmpv1, the notify-
community parameter 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
community string rather than the snmpv3securityName that is used by snmpv3.
Event and Accounting Logs
snmp-trap-group
Page 277
. The