>>>>> "AG" == Antonio Grassi <[EMAIL PROTECTED]> writes: AG> - First of all, can snmp notifications be sent over TCP instead of UDP?
Yes. AG> - snmpinform talks with snmpd in order to deliver the notification. I've AG> seen that snmpd has a buffer of commands to process. Does snmpinform AG> exit after passing the notification to snmpd (even if snmpd hasn't AG> processed it yet)? I think not, but want to be sure. snmpd can send informs, not receive them. snmptrapd is what can receive informs (from anything that generates them, including snmpd and snmpinform). snmpinform will wait for the remote receiver (snmptrapd) to acknowledge that it received it before exiting. AG> - If not, wich are the exit codes of snmpinform (snmpcmd?) I mean, I saw AG> that snmpinform can be used in such a way that it retries the AG> inform-request n times, with x seconds between each retry. But how can I AG> differentiate the case in wich the program exits because it receives the AG> confirmation from the manager, from that in which the program exits AG> because it has reached the maximum number of retries? It'll exit with a 1 if it failed to get the inform to its destination. AG> - Does snmptrapd recognize a repeated snmp notification (because it's AG> previous confirmation was lost)? No, it will log it twice. AG> - If yes, is there a way to identify a notification as being the same, AG> even between different invocations of snmpinform? no, which is exactly why it doesn't assume that it's a duplicate. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
