Master-agent vs. Sub-agent vs. pluggable object

Hi all, 

I'm adding SNMP support to our product. It is a network device with
quite a few parameters to control (about 100 scalars and a few tables..)
running on a linux machine. My target is to use the snmpd daemon and
expand it with these parameters (the value of the parameters will be
kept in a separate process).

I have a MIB file with the relevant parameters and I more or less
figured out how to use mib2c and complete the relevant code. Now I'm
trying to figure out what's the best way to use these files:
1. compile as part of the master agent
2. compile as subagent
3. compile as pluggable shared objects

The documentation gives all options, but I'm asking for recommendations
which one is the best in my case. 

One consideration I have: I would like to have all parameters integrated
into a common "object" (for example, build all parameters into a single
sub-agent). Which option supports this (if any)?

Any other considerations?

Thanks,
Alon



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
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