Snmptrapd.conf output option
By default, snmptrapd does not do anything with received notifications.
man page belucydyret.web.fc2.com section 5
You have to tell it what you want to receive notifications. To receive SNMPv1 or SNMPv2c notifications you need to tell snmptrapd your community strings. The easiest way to do this is by using the authCommunity snmptrapd.
For example, this line:. Will let snmptrapd process notifications received using the "public" community string.
snmptrapd | Unix Linux Forums | UNIX for Advanced & Expert Users
Those notifications may be logged, allowed to trigger executable actions see below , and resend data to the network forward. SNMPv3 adds security to the SNMP protocol and is a safer way to receive notification data.
But, it's a bit more complex to set up. Configuration of SNMPv3 notifications is described fully on a separate page:. Generating traps is only half of the battle.
We also need something to receive the notification, and respond accordingly. The Net-SNMP suite includes an application snmptrapd which can accept and process such notifications. By default, it will simply log all incoming notifications via syslog. The two snmptrap commands described in TUT: The snmptrapd utility also has the ability to execute other programs on the reception of a trap. This is controlled by the traphandle directive, with the syntax.
Notice, that this only takes an OID to determine which trap or notification is received. This means that SNMPv1 traps, which have a trap type and specific type , need to be represented in SNMPv2 format, which is described in RFC SNMPv1 traps fall into two broad categories: Generic traps use trap types 0 through 5, and do not use the specific type.
snmptrapd
To match a generic trap, the traphandle OID should be the SNMPv2-MIB:: For example, to match linkDown traps trap type 2 , the correct OID would be "1.
When the trap type is 6, the trap is an enterprise specific trap. When matching these traps, the traphandle OID is constructed using the enterprise OID and specific type specified in the trap. Earlier in the tutorial, we sent a SNMPv1 enterprise specific trap with an enterprise OID of UCD-TRAP-TEST-MIB:: To match this trap type, the traphandle OID should be the enterprise OID, plus 0, plus the specific type. So the correct OID would be ". SNMPv2 traps and informs are much easier, because they include the correct OID in the SNMPv2-MIB:: The command specifies a command to be executed by snmptrapd upon reception by the command.
This command is executed with the data of the trap as its standard input. The first line is the host name, the second the IP address of the trap sender, and the following lines consists of an OID VALUE pair with the data from the received trap. The following snmptrap invocation, to issue a generic Link down trap OID 1. These tutorial links talk about SNMP generically and how the protocol itself works. They are good introductory reading material and the concepts are important to understand before diving into the later tutorials about Net-SNMP itself.
These tutorial pages discuss the command line tools provided in the Net-SNMP suite of tools. Nearly all the example commands in these tutorials works if you try it yourself, as they're all examples that talk to our online Net-SNMP test agent. Given them a shot!
Net-SNMP comes with two long-running daemons: Net-SNMP comes with a highly flexible and extensible API. The API allows you to create your own commands, add extensions to the agent to support your own MIBs and perform specialized processing of notifications.
All our tools and applications have extensive debugging output. These tutorials talk about how the debugging system works and how you can add your own debugging statements to you code:. Retrieved from " http: Navigation menu Views Page Discussion View source History. Personal tools Create account Log in. Tools What links here Related changes Special pages Printable version Permanent link Page information.