Re: bug in trapsess directive?

2013-11-28 Thread sarath azad
Hi Paul,

I too have observed this that trapsess directive, was requiring the engine-id 
for properly sending the traps. Otherwise, though we were able to generate and 
send the traps from our device, but they were not able to be detected at the 
receiving manager. Once we gave the engine-id of our device (trap generating 
device) in trapsess directive, the traps were successfully received at the 
manager. 
In case of SNMPv3 traps the engine-id the sending device (trap generating 
device) needs to be used in trapsess, which will be common for all the traps 
generated from our device. 

Please let me know if you have any questions regarding this.

thanks and regards
S Sarath


On Tuesday, November 19, 2013 9:52 AM, Paul Jaehne paul.jae...@gmail.com 
wrote:
 
Version: 5.7.2


Hi all,

I'm currently experiencing strange behaviour while experimenting with SNMPv3 
traps. Every time I define a trapsess directive like followed I get an error 
about an unknown user:

trapsess -v3 -u trapuser -l authPriv -n  -a MD5 -A authPass1 -x AES -X 
privPass1 192.168.2.240
--
snmpd: send_trap: USM unknown security name (no such user exists)

When I change the trapsess directive to explicitely specify an imaginary 
engineId, I don't get any errors any more:

trapsess -v3 -u trapuser -e 0x0102030405 -l authPriv -n  -a MD5 -A authPass1 
-x AES -X privPass1 192.168.2.240

My problem is that I don't really want to set the engineIDs manually, since I 
would need different ones to distinguish between the devices.

Any thoughts on what I'm doing wrong and how this can be solved?

Cheers,
Paul

--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk
___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351iu=/4140/ostg.clktrk___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders


bug in trapsess directive?

2013-11-18 Thread Paul Jaehne
Version: 5.7.2

Hi all,

I'm currently experiencing strange behaviour while experimenting with
SNMPv3 traps. Every time I define a trapsess directive like followed I get
an error about an unknown user:

trapsess -v3 -u trapuser -l authPriv -n  -a MD5 -A authPass1 -x AES -X
privPass1 192.168.2.240
--
snmpd: send_trap: USM unknown security name (no such user exists)

When I change the trapsess directive to explicitely specify an imaginary
engineId, I don't get any errors any more:

trapsess -v3 -u trapuser -e 0x0102030405 -l authPriv -n  -a MD5 -A
authPass1 -x AES -X privPass1 192.168.2.240

My problem is that I don't really want to set the engineIDs manually, since
I would need different ones to distinguish between the devices.

Any thoughts on what I'm doing wrong and how this can be solved?

Cheers,
Paul
--
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311iu=/4140/ostg.clktrk___
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders