search for: su10krt3

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

On Feb 16, 2014, at 11:33 PM, ??? ????? wrote: > > > 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: > > nut-2.7.1.5.tar.gz > > > Thanks a lot, I downloaded it from this link and ran commands "autoreconf && ./configure && make" to build it: > You

> Since you didn't specify an install prefix, check /usr/local/ups for your > new installation. > Thanks, found the installation there. Please try building snmp-ups, and let me know how the output of upsc looks. > Rebuilt is with "*--with-snmp" *option, installed and started nut processes, and they are working :) upsc trippliteups at 10.200.254.26 command output

On Feb 17, 2014, at 4:35 AM, ??? ????? wrote: > ups.status: OL Actually, during your next maintenance window, is it possible to verify that the driver sees the "OB" and "LB" status values? We also might want to add R/W variables, and the instant command to enable shutdown. -- Charles Lepple clepple at gmail

> > 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: > > nut-2.7.1.5.tar.gz<http://buildbot.networkupstools.org/~buildbot/cayman/snapshot/snmp_subdriver/rab7b0452e21aef8aaf308963da6380e712427e1d-146/nut-2.7.1.5.tar.gz> > > Thanks a lot, I downloaded it from this link and ran commands

[Please keep the list CC'd. Thanks!] On Feb 13, 2014, at 4:55 AM, ??? ????? wrote: > Can you try adding "-v 1" to the snmpwalk command? If that works, we can add it to gen-snmp-subdriver.sh. > > Yes, I tried it before, ran command "snmpwalk -v 1 -On -c public 10.200.254.39 .1.3.6.1.4.1.935" > > Output: > .1.3.6.1.4.1.935 = NULL > Error: OID not

> Does it have the same behavior if you start from .1.3.6.1.4.1.935*.1* or . > 1.3.6.1.4.1.935.1.1? If not, no worries - see below. > > Yes, says "Timeout: No Response from 10.200.254.39", Ok. > ..... > > >> The important part of "mode 2" is to have the output of snmpwalk. It is >> possible to query each OID, and manually build the *-mib.c

Hi, Nut-upsusers, I am having problem configuring NUT to work with Tripplite UPS through SNMP. There is a Tripplite SmartOnline SU10KRT3/1X and attempts to monitor it using NUT though SNMP are failing... OS: Enterprise Linux 6, Nut version: 2.6.5. ups.conf is configured: [trippliteups] driver = snmp-ups port = 10.200.254.39 desc = "ProductionServer" snmp_version = v1 community...

On Feb 10, 2014, at 1:16 AM, ??? ????? wrote: > Thanks for you reply. Concerning the subscribtion list, I have earlier filled in the fields and sent request to subscribe to this list, but still haven't got an answer. I added you manually, but check your spam folder just in case it ended up there. > Yes, I do have a MIB file that was on CD that came with the UPS, attached it to this

Thanks, now I started getting messages from the list. As you advised, I renamed the mib file NETCARD.mib to Tripplite and ran command ./gen-snmp-subdriver.sh -H 10.200.254.39 -c public -n Tripplite Here is what it says: snmp_build: unknown failuresnmpget: Error building ASN.1 representation (Can't build OID for variable) COUNT = 0 / 0 Creating tripplite-mib.h Creating tripplite-mib.c Done.