search for: su_infosize

...(FIXME: ...) + * oid2info: lookup table between OID and NUT values + * setvar: variable to set for SU_FLAG_SETINT + * + * Example: + * { "input.voltage", 0, 0.1, ".1.3.6.1.4.1.705.1.6.2.1.2.1", "", SU_INPUT_1, NULL }, + * { "ups.status", ST_FLAG_STRING, SU_INFOSIZE, ".1.3.6.1.4.1.705.1.7.3.0", "", SU_FLAG_OK | SU_STATUS_BATT, onbatt_info }, + * + * To create a value lookup structure (as needed on the 2nd line), use the + * following kind of declaration, outside of the present snmp_info_t[]: + * static info_lkp_t onbatt_info[] = { + *...

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

...3.1.6.3.8 Is it possible to solve it, i can support with tests. Best solution would be possibility to tweak SNMP keys from config file eg. prepare mappings loaded from external files because I saw key 1.3.6.1.2.1.33.1.7.1 directly inside ietf-mib.c : { "ups.status", ST_FLAG_STRING [1], SU_INFOSIZE [2], IETF_OID_UPS_MIB [3] "6.3.8", "", 0, ietf_overload_info }, /* upsAlarmOutputOverload */ { "ups.status", ST_FLAG_STRING [1], SU_INFOSIZE [2], IETF_OID_UPS_MIB [3] "7.1.0", "", 0, ietf_test_active_info }, /* upsTestId */ Tweak file could be a...

...tery misses the .0 at the end: #define PW_OID_BATTEST_START "1.3.6.1.4.1.534.1.8.1.0" And by the way, the RFC1628-way of initiating tests works (by hand using snmpget [SpinLock]/snmpset) with this ups, too. And I took the ups status from ietf: { "ups.status", ST_FLAG_STRING, SU_INFOSIZE, IETF_OID_POWER_STATUS, "OFF", SU_STATUS_PWR, &ietf_pwr_info[0] }, because 1.3.6.1.4.1.534.1.4.5.0 isn't answerd by the card. CU, Gernot

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet: