Snmptrapd - Revision history

Rstory: typo

2014-04-29T16:17:45Z

typo

Rstory: /* MySQL Logging */

2012-08-31T12:54:04Z

‎MySQL Logging

Rstory: /* MySQL Logging */

2012-08-30T15:49:15Z

‎MySQL Logging

Rstory: document sql trap logging

2012-08-29T12:38:42Z

document sql trap logging

Wes at 23:18, 30 June 2011

2011-06-30T23:18:15Z

Wes: Created page with "{{tool|snmptrapd|code=apps/snmptrapd.c|manual=1}} The '''snmptrapd''' application typically listens to port 162 (and maybe 10162) and logs or acts upon any notifications ([[TRAP..."

2011-06-30T23:16:35Z

Created page with "{{tool|snmptrapd|code=apps/snmptrapd.c|manual=1}} The '''snmptrapd''' application typically listens to port 162 (and maybe 10162) and logs or acts upon any notifications ([[TRAP..."

New page

{{tool|snmptrapd|code=apps/snmptrapd.c|manual=1}}

The '''snmptrapd''' application typically listens to port 162 (and maybe 10162) and logs or acts upon any notifications ([[TRAP]]s or [[INFORM]]s) that it receives.

== Configuring snmptrapd ==

snmptrapd is configured through its [[snmptrapd.conf]] file.

← Older revision		Revision as of 16:17, 29 April 2014
Line 46:		Line 46:
	sqlSaveInterval 9		sqlSaveInterval 9

−	No traphandler is needed. If MySQL support is configured in a handler will be registered automatically. ~~Loggin~~ to the database is disabled by setting sqlSaveInterval to 0.	+	No traphandler is needed. If MySQL support is configured in a handler will be registered automatically. Logging to the database is disabled by setting sqlSaveInterval to 0.

@@ Line 31: / Line 31: @@
   [snmptrapd]
   host=localhost
 A different user may also be configured, if using a MySQL user besides root. See the [http://dev.mysql.com/doc/refman/5.1/en/adding-users.html MySQL page on creating users] for help creating MySQL users.

@@ Line 33: / Line 33: @@
   host=localhost
   password=sql
- # user may also be configured, if using a MySQL user besides root
 Then ''snmptrapd.conf'' must be modified to indicate how often received traps should be written to the database:

← Older revision		Revision as of 12:38, 29 August 2012
Line 16:		Line 16:

	will let any incoming notification with a community name of ''myInsecureCommunity'' be logged to it's output file/syslog/etc.		will let any incoming notification with a community name of ''myInsecureCommunity'' be logged to it's output file/syslog/etc.
		+
		+	== MySQL Logging ==
		+	The ability to log received traps to a MySQL database was added in Release 5.5. The ''--with-mysql'' option must be specified when configuring the package. e.g.
		+
		+	./configure --with-defaults --with-mysql
		+
		+	The database schema must be loaded into MySQL:
		+
		+	cd ~/net-snmp-5.7.1
		+	mysql -u USER -p PASSWORD < dist/schema-snmptrapd.sql
		+
		+	The user that runs snmptrapd (usually root) needs a MySQL configuration file with
		+	user credentials configured. e.g. ~/.my.cnf
		+
		+	[snmptrapd]
		+	host=localhost
		+	password=sql
		+	# user may also be configured, if using a MySQL user besides root
		+
		+	Then ''snmptrapd.conf'' must be modified to indicate how often received traps should be written to the database:
		+
		+	# maximum number of traps to queue before forced flush
		+	# set to 1 to immediately write to the database
		+	sqlMaxQueue 140
		+
		+	# seconds between periodic queue flushes
		+	sqlSaveInterval 9
		+
		+	No traphandler is needed. If MySQL support is configured in a handler will be registered automatically. Loggin to the database is disabled by setting sqlSaveInterval to 0.

← Older revision		Revision as of 23:18, 30 June 2011
Line 6:		Line 6:

	snmptrapd is configured through its [[snmptrapd.conf]] file.		snmptrapd is configured through its [[snmptrapd.conf]] file.
		+
		+	== Access Control ==
		+
		+	snmptrapd, at a minimum, needs access control settings to allow notifications using various SNMP protocols access to its logging and execution framework.
		+
		+	Example snmptrapd.conf line:
		+
		+	authCommunity log myInsecureCommunity
		+
		+	will let any incoming notification with a community name of ''myInsecureCommunity'' be logged to it's output file/syslog/etc.