On 14/12/2007, PoWah Wong <[EMAIL PROTECTED]> wrote:
> The trap receiver *didn't* log the trap until
> I modify snmptrapd.conf to:
> createUser -e 0x80001f88806a19937bd3c75547
> test_MD5_AES MD5 12345678 AES 87654321
> i.e. the modification is that I change the engineID.
> Now it started to log the trap.
> However, I am still confused about engineID.
Bottom line:
The username and engineID specified (either
implicitly or explicitly) by the sending application
must match the username and engineID specified
(implicitly or explicitly) by the receiving application.
For most requests (GET, GETNEXT, SET, and INFORM),
the receiving application will use a default engineID,
and the sending application will first probe to discover
the engine ID to use. The effect that everything just
works, and you don't have to worry about engineID.
That's not the case with TRAP requests. Such requests
are "non-acknowledged", so this engine probe mechanism
isn't used.
In this situation, the safest approach is to *explicitly* specify
the same engineID on both the sending side ("trapsess" in
snmpd.conf) and the receiving side ("createUser" in snmptrapd.conf)
Dave
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
