Quoting Robert Story <[EMAIL PROTECTED]>:
> Dave,
>
> I was looking at linking the ifXTable ifLinkUpDownTrapEnabled object to
> the code that actually implements the monitoring ...
> .... I was wondering how easy/hard it would be for you to throw
> together a simple api to toggle the status of the trap for a given
> interface.
Hmmmm...
I'm not quite sure what sort of API you had in mind, but my immediate
reaction would be to implement this within the "interface_load()"
handling. The current DisMan-based monitoring is something of a
workaround, and it would be more efficient to implement this more
closely within the interface-related code itself.
Just off the top of my head, how about the following approach:
- The O/S-specific "interface_arch_load()" routine could populate
a temporary holding container with the current list of interfaces
and accompanying statistics.
- The common "interface_load()" routine could then compare
this latest list with the previous information, generating
linkUp or linkDown traps as necessary (as well as updating
the ifLastChange column value - see other thread).
The existing config directive would then become a means for setting
the default value for the I/F-specific trapEnabled column, rather
than setting up DisMan entries to monitor the I/F status from
outside.
Thoughts?
Dave
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
-------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
