Todd Bradley <todd.brad...@nirvanix.com> writes: > First, what is supposed to happen when snmpd is unable to send a TRAP > due to the network interface being down?
There is nothing it can do; it doesn't queue traps until they can be sent (because though it might be able to tell about it's own interface, it certainly can't tell about interfaces on the nearest neighbor, etc, that might also affect delivery). > How does this differ with an INFORM? INFORMs will at least retry. IE, it'll try to send the INFORM, fail to get a response and will retry to send it up until the retry limit has been reached. But, it's probably trying those pretty quickly and it's likely that the interface will be down longer than the retryLimit*timeout seconds that it'll be using to attempt to send the INFORMs. > Second, when snmpd restarts (or crashes) does it remember TRAPs and > INFORMs that it hasn't yet delivered, and then retry them when it > comes back up? Or is that list kept in memory and is therefore lost? No, it does not. It's only in memory and generally doesn't have that many to send out in the first place (or if it has built up that big of a queue, you probably have much more serious issues). -- Wes Hardaker SPARTA, Inc. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Net-snmp-users mailing list Net-snmp-users@lists.sourceforge.net Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
