Problem Using TCP for Sending Traps

2007-05-18 Thread John Giaccotto
Hi, I have configured snmptrapd to listen on both UDP and TCP ports. I start snmptrapd as follows: $SNMPTRAPD -On -C -c $SNMPTRAPDCONF -Lf $LOGFILE udp:anIPAddress:162 tcp:anIPAddress:162 If I send a trap from another machine using the following line: snmptrap -v 2c -c public tcp:anIPAddress

RE: Reducing Risk of Missing SNMP Traps

2007-05-18 Thread John Giaccotto
Of Dave Shield Sent: Tuesday, May 15, 2007 4:17 AM To: John Giaccotto Cc: net-snmp-users@lists.sourceforge.net Subject: Re: Reducing Risk of Missing SNMP Traps On 14/05/07, John Giaccotto [EMAIL PROTECTED] wrote: . Is there an accepted method for ensuring that if [a trap] does [get dropped

Reducing Risk of Missing SNMP Traps

2007-05-14 Thread John Giaccotto
Hi, 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? Thanks, John

RE: Reducing Risk of Missing SNMP Traps

2007-05-14 Thread John Giaccotto
-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: net-snmp-users@lists.sourceforge.net Subject: Re: Reducing Risk of Missing SNMP Traps On 14/05/07, John Giaccotto [EMAIL PROTECTED