On 18/04/07, M, Somashekhar (Somashekhar) <[EMAIL PROTECTED]> wrote: > I am giving the agent's engineID....
Sorry, you're quite correct. That's a more sensible engine ID when sending a TRAP notification (though not for an INFORM). > .... and this will be discovered by Mib Browser. Errr.... no it won't. Although you may be using the same application to handle the browsing of MIB values, and receiving traps - these are actually two completely separate operations, and are handled very differently. If you want the 'snmptrapd' receiver to accept incoming SNMPv3 traps, you need to explicitly configure the engine IDs accordingly. This is covered in the tutorial page I mentioned this morning. > Now in snmptrapd.conf I am seeing usmUser entry being replaced. Good. But what was the exact directive that you used? > I tried to send the trap still it is not reaching the mib browser, with > tcpdump I am able to see the trap has been sent successfully and > received. It's probably been received by the trap receiver, but then discarded because the SNMPv3 user is unknown. (Or more accurately, the user/engineID pair is unknown). You *must* include the correct engineID when creating the SNMPv3 user in snmptrapd.conf. Unlike snmpwalk et al, it will *not* discover the engineID automatically. (This is one of the major deficiencies in unacknowledged SNMPv3 traps) Please read through the tutorial page until you're happy that you understand the issues at work here. It is not as simple as it might seem. Dave ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ 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
