.
And it works fine with the snmpv3 informs as well :-)
Thank you so much!
Eugen
-Original Message-
From: Dave Shield [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 25, 2006 4:42 AM
To: Eugen
Cc: 'Thomas Anders'; Net-snmp-users@lists.sourceforge.net
Subject: RE: Bad engine ID value after -e
On Tue, 2006-01-24 at 17:02 -0500, Eugen wrote:
Without double quotes there is no error message
indeed but the traps are not intercepted by snmptrapd.
Does it not receive them at all, or does it receive
them but refuse to process them? Try running
snmptrapd -f -Le -d
Do you see the
Eugen wrote:
trapsess -e 0x0102030405 -v 3 -u myuser -a MD5 -A my_password -l
authNoPriv localhost
Try without the double quotes.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
---
This SF.net email is sponsored by: Splunk
Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas
Anders
Sent: Tuesday, January 24, 2006 4:41 PM
To: Net-snmp-users@lists.sourceforge.net
Subject: Re: Bad engine ID value after -e flag
Eugen wrote:
trapsess -e 0x0102030405 -v 3 -u myuser -a MD5 -A my_password -l
Eugen wrote:
Without double quotes there is no error message indeed but the traps are
not intercepted by snmptrapd.
Receiving with snmptrapd is a different story. Did you read the tutorial
on SNMPv3 notifications?
http://www.net-snmp.org/tutorial/tutorial-5/commands/snmptrap-v3.html
@lists.sourceforge.net
Subject: Re: Bad engine ID value after -e flag
Eugen wrote:
Without double quotes there is no error message indeed but the traps
are
not intercepted by snmptrapd.
Receiving with snmptrapd is a different story. Did you read the tutorial
on SNMPv3 notifications?
http://www.net
Eugen wrote:
Yes, and using that instructions I was able to send v3 traps using
sendtrap tool, as I've described in my original email. The same snmpcmd
like parameters for trapsess I suppose should tell the agent to generate
the same kind of traps but for some reason it seams that they are
