Hello, I'm trying to see if there are best practices for organization of routines to send traps. In my application I use the mib2c generated table load routine to populate a mib table with application status. I'd like to send traps based on values of those stats but not sure if I should send the trap from the table load routine as I discover the values (the table is cached with a refresh period even when not accessed) or should I register the snmp callback in the module init routine and maybe the callback has some way to access the MIB table and read the stats from the mib table. In summary:
1. send traps as I get stats from data source (e.g. from <table>_Load) 2. check MIB value and send trap (assuming trap callback can get access to MIB data...how?) Which one is preferred. I did not see too many examples in net-snmp-5.3.2.2 (RHEL5). The disman module had a few examples (traceRoute.c and pingCtlTable) which sent the traps directly as the data was obtained. Thanks. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ 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
