2009/12/16 Jordi Gutiérrez Hermoso <jord...@gmail.com>: > Our MIB has information about what modules are available in our > application and what information they should respond to. However, our > modules are largely independent between each other and communicate > with standard network protocols. Should our customers at any time wish > more or less functionality from our product, we can add or remove > modules, and our MIB has to change to reflect this. > > How should a subagent handle this? At present, we have scripts that > add to snmpd.conf whatever new OIDs we need, and we map the OIDs to > their values with "extend" commands and the external application we've > written.
Your question definitely makes sense. Making information appear or disappear dynamically is possible e.g. as follows: 1. By defining a table in the MIB and by adding and/or removing rows at runtime. 2. By defining a scalar object in a MIB, by declaring it optional instead of mandatory. Net-SNMP allows you to register and unregister scalar objects dynamically. Both (1) and (2) are possible with a static MIB -- a MIB that does not change at runtime. Functions like netsnmp_create_handler_registration() and netsnmp_unregister_handler() make it possible to let scalar objects appear and disappear dynamically. Bart.
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
