[Nut-upsuser] Tripplite UPS (SU10KRT3/1X) through snmp-ups (nut 2.6.5)
clepple at gmail.com
Fri Feb 14 14:59:11 UTC 2014
On Feb 14, 2014, at 9:26 AM, Charles Lepple wrote:
> On Feb 13, 2014, at 10:49 PM, Иши Кылса wrote:
>> Slightly changed the list, took from running snmptranslate for all parameters:
>> snmptranslate -IR -On upsBaseIdentModel upsBaseBatteryStatus upsSmartBatteryCapacity upsSmartBatteryTemperature upsSmartInputLineVoltage upsBaseOutputStatus upsSmartOutputVoltage upsSmartOutputFrequency upsSmartOutputLoad upsSmartControlUpsOff upsSmartControlSimulatePowerFail upsSmartControlFlashAndBeep
> All but the last three are mapped here: https://github.com/networkupstools/nut/tree/snmp_subdriver @ ab7b0452e (might need to re-clone this; I rebased this on master.)
I forgot to mention, if you don't want to deal with autoconf, etc., when building from Git, you can grab a snapshot from Buildbot:
This builder generates the snapshots: http://buildbot.networkupstools.org/public/nut/waterfall?show=Debian-x64-gcc
> I haven't read up on the difference between NUT variables and commands in snmp-ups.
> Please try building snmp-ups, and let me know how the output of upsc looks.
>> .188.8.131.52.4.1.9184.108.40.206.6.2.5 (Last 3 OIDs didn't return values with snmpget, all others returned correct values as listed above.)
> The upsSmartControl* OIDs are probably write-only (although the MIB indicates you should be able to read them back).
> Charles Lepple
> clepple at gmail
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsuser