The usual behavior of an SNMP agent is to wait for incoming SNMP requests and respond to them; if no requests are received, an agent will typically not initiate any actions.
This section describes various directives that can configure snmpd to take a more active role.
Notification Handling
trapcommunity STRING
defines the default community string to be used when sending traps. Note that this directive must be used prior to any community-based trap destination directives that need to use it.
trapsink HOST [COMMUNITY]
trap2sink HOST [COMMUNITY]
informsink HOST [COMMUNITY]
define the address of a notification receiver that should be sent SNMPv1 TRAPs, SNMPv2cTRAP2s, or SNMPv2 INFORM notifications respectively. If COMMUNITY is not specified, the most recent trapcommunity string will be used.
If the transport address does not include an explicit port specification, then PORT will be used. If this is not specified, the well-known SNMP trap port (162) will be used.
If several sink directives are specified, multiple copies of each notification (in the appropriate formats) will be generated.
authtrapenable {1|2}
determines whether to generate authentication failure traps (disabled(2) - the default). Ordinarily the corresponding MIB object (snmpEnableAuthenTraps.0) is read-write, but specifying this directive makes this object read-only, and attempts to set the value via SET requests will result in a notWritable error response.
v1trapaddress HOST
defines the agent address, which is inserted into SNMPv1 TRAPs. Arbitrary local IPv4address is chosen if this option is omitted. This option is useful mainly when the agent is visible from outside world by specific address only (e.g. because of network address translation or firewall).