On 14/05/07, John Giaccotto <[EMAIL PROTECTED]> wrote: > > ..... Is there an accepted method for ensuring that > > .... if [a trap] does [get dropped] that the sending > > component is made aware of this?
> 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? Keeping track of responses (and re-sending requests if appropriate) ought to be handled by the low-level SNMP library. I wouldn't expect an application to have to do this explicitly. But if the trap receiver isn't accepting the notifications (for whatever reason), then fundamentally, the sending application needs to be able to do something sensible. What action is appropriate isn't something that can be dictated in general - it really depends on your management requirements. So this is something you'll probably have to code yourself. 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
