Trap Configuration
The distribution of SNMP supports SNMPv1, SNMPv2 and SNMPv3 traps. Control over these traps is defined with a number of directives:
SNMPv1 and SNMPv2 traps
trapcommunity COMMUNITY
Defines the default community to be used when sending SNMPv1 or SNMPv2 traps.
Note that this directive must be used prior to a trapsink
or trap2sink
directive that wishes to use this community.
COMMUNITY
the community name to be used.
Example:
trapcommunity traps
trapsink HOST [COMMUNITY [PORT]]
trap2sink HOST [COMMUNITY [PORT]]
Defines a destination for SNMPv1 or SNMPv2 traps generated by the agent.
HOST
is an address specifier defining the network target that traps will be sent to.
It consists of an optional transport specifier (udp
(default if not specified) or tcp
), followed by a hostname or IPv4 address, followed by an optional port number.
The address components are separated by colons ":".
For example, localhost
or tcp:192.168.137.2:163
.
COMMUNITY
if specified will be the community name used for the traps.
If it is not specified, the most recently specified trapcommunity
will be used.
PORT
allows for port-number to be defined if it is not present as part of the HOST
specification.
If no port is defined, the default port number of 162 will be used.
When a TCP transport specifier is used the SNMP agent establishes the TCP connection with the trap manager at start-up.
Therefore the trap manger must be started before the SNMP agent otherwise an error is reported for the line in the snmpd.conf
file which defines the trap manager.
Likewise when the TCP connection between the SNMP agent and the trap manager is dropped, traps are lost. Therefore it is inadvisable to use TCP instead of UDP for the transport specifier of trap managers.
If TCP is used for the connection between the SNMP agent and the trap manager and the connection is lost, to re-establish the connection the SNMP agent must be restarted, with the trap manager running and able to accept a TCP connection from the SNMP agent.
For issues with the trap manager accepting TCP connections from a SNMP agent refer to trap manager documentation.
Example:
trap2sink udp:192.168.137.220:162 traps
SNMPv3 traps
trapsess [SNMPCMD_ARGS] HOST
Defines the configuration for a trap. This is the only way to define SNMPv3 traps and it is an alternative method for defining SNMPv1 and SNMPv2 traps.
SNMPCMD_ARGS
are arguments that would be used for an equivalent snmptrap
command.
So for example to send an SNMPv3 trap as USM user user1
with authentication and encryption, the value -v3 -u user1 -1 priv
would be used.
HOST
see host definition for trap2sink
above.
Example:
trapsess -v3 -u user1 -1 priv udp:192.168.137.220:162
trapsess -v2c -c public 192.168.137.221:162