> My immediate reaction would be to use the "extend" directive > to invoke the westell command directly. That would provide the > basic information very simply. > > The main problem is that the output of this directive is string-based, > rather than numeric values (even if those strings actually contain > numbers!). My suspicion is that cacti probably requires numeric > data to work with.
well cacti doesn't have a standard data query for ADSL, there are various add-on templates out there, but I don't mind tweaking that end too, I'll see if I can persuade it to convert numeric strings. > Otherwise, you're probably looking at using either "perl" perl is probably a bit big to go fitting into the limited flash memory on the openwrt box. > or "pass" to > take this raw data, and report it back as proper numeric values - either > using your own private MIB structure, how would I pick an OID, just start with a 1.3.6.1.3.random experimental one? > or the standard ADSL MIB. > Or else craft a simple C-based MIB module, populating it by > invoking this command and parsing the output (probably within > a cache load routine). Is there a simple example of a MIB module? presumably ity just ends up as a .so? the westell routing is pretty straightforward C, so if I end up that route, rather than spawning the original utility and then parsing its output, it would make sense to just call its guts as a function and return a struct of results. Thanks. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
