Snmptrap help

Koaps <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hello all,

I'm trying to setup snmptrapd on a linux server to
catch traps from IBM hardware.

I'm having a hell of time getting this to work. After
much google'n around and testing I was finally able to
send a trap to localhost on the server and write the
trap to a file using this command:

snmptrap -e 0x0102030405 -v 3 -u myuser -a MD5 -A
mypassword -l authNoPriv localhost:162 42 coldStart.0

With a config file like this:

createUser -e 0x0102030405 myuser MD5 mypassword DES
myotherpassword
authUser log,execute,net myuser

traphandle default /usr/bin/tee -a
/home/myuser/logs/traps.log

Problem is, the IBM hardware doesn't have an area to
specify the engineID, so the trap it sends fails with:

snmp_parse: Parsed SNMPv3 message (secName:myuser,
secLevel:authNoPriv): USM unknown security name (no
such user exists)

I've tried to remove the engineID from the createUser
statement and I've tried to use the following options
in the config file:

disableAuthorization yes
ignoreAuthFailure yes

But nothing seems to work.

Is there a way to either discover the engineID to use
for the IBM hardware or setup the server to not
require it to send SNMPv3 traps?

Thanks
-Chris

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.