-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Monday, May 14, 2007 3:25 PM To: John Giaccotto Cc: [email protected] Subject: Re: Reducing Risk of Missing SNMP Traps
On 14/05/07, John Giaccotto <[EMAIL PROTECTED]> wrote: > Can anyone provide some advice on how to minimize the risk that a trap may > not arrive at its destination? Is there an accepted method for ensuring > that a trap does not get dropped or if it does that the sending component is > made aware of this? Use SNMPv2c or SNMPv3, and send an INFORM instead of a TRAP. Thanks for your response. What is the general practice for dealing with this when the traps are emitted from a software component which is not capable of keeping track of responses to INFORM messages? In our case we are mostly emitting traps from a log4j Appender and from various Perl and Bash scripts. ------------------------------------------------------------------------- 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
