thanks Sir,
As you said i set like this in my conf
trapsess -v 3 ..... localhost:162
snmp trap are received by snmptrapd so port number might be
the problem.
thanks you very much Sir
Regards
bhushan. E . Sonawane
On 11/22/06, Dave Shield <[EMAIL PROTECTED]> wrote:
On 22/11/06, bhushan <[EMAIL PROTECTED]> wrote:
> 1) trapsess -v 3 -e 0x010203040506 -a MD5 -A auth_password -l authPriv
-u
> my_user -x AES128 -X priv_password localhost
> 2 )trap2sink localhost public 162
> dump of snmptrapd as follows when i send trap using my code
>
> Received 107 bytes from 127.0.0.1
> 0000: 30 69 02 01 01 ....
OK - That's the SNMPv2c trap (i.e. from "trap2sink")
> by looking at both dump of snmpd & snmptrapd i understood that
> snmpv3 packet send by snmpd to destination was not received by snmptrapd
I'd agree.
> as i said for enabling snmptrapd to receive snmp v3 trap i also
configured
> snmpv3 user in snmptrapd.conf as follows
No - that's not relevant here.
It looks as if snmptrapd isn't even receiving the PDU, so it never gets as
far
as looking at what users are or are not configured.
Ummm....
Try the following:
trapsess -v 3 ..... localhost:162
Dave
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
