On Sat, 7 Jan 2006 10:14:46 +0000 Dave wrote: DS> > I was looking at linking the ifXTable ifLinkUpDownTrapEnabled object to DS> > the code that actually implements the monitoring ... DS> > .... I was wondering how easy/hard it would be for you to throw DS> > together a simple api to toggle the status of the trap for a given DS> > interface. DS> DS> Hmmmm... DS> DS> I'm not quite sure what sort of API you had in mind, but my immediate DS> reaction would be to implement this within the "interface_load()" DS> handling. The current DisMan-based monitoring is something of a DS> workaround, and it would be more efficient to implement this more DS> closely within the interface-related code itself.
Now why didn't I think of that? DS> - The O/S-specific "interface_arch_load()" routine could populate DS> a temporary holding container with the current list of interfaces DS> and accompanying statistics. DS> DS> - The common "interface_load()" routine could then compare DS> this latest list with the previous information, generating DS> linkUp or linkDown traps as necessary (as well as updating DS> the ifLastChange column value - see other thread). Already done, except for the trap generation. -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
