I'm trying to extend the agents monitor capabilities, so that I'll get a trap every time the monitor does perform a check. But now I'm a bit confused where those traps are sent(a bit cisco style trapping).
The Release I use is net-snmp-5.2rc4. I added in the file agent/object_monitor.c and in the file agent/disman/mteEventNotificationTable.c some logging statements to see when which function is called ( --enable-debugging and -D flage were to extensive), but it seems the none of the functions in those files is called.
This is the way I understand the monitor of snmpd:
-the agent starts, read the config and register the oid's which should be monitored -> function netsnmp_monitor_register(..)
- the agent checks the oid's if there is one which should be reported by a trap -> add oid (or list entry) to the notify_pending list
- when all oid's are checked they are switched from pending to ready state
- a callback build the pdu and send out the traps.
Is this a correct understanding of the behavior of the monitor?
Where can i find more information how callbacks work. The notification example in the tutorial is very simple and didn't helped very much.
Thanks for help.
Regards Sven Herzing
-- Sven Herzing WEB.DE AG http://comwin.name/[EMAIL PROTECTED]
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
