similar to: Updating snmp-mib.c with new Cyberpower v2.0 MIB

On 10/31/2017 01:13 AM, Jim Klimov wrote: > If the new data is in a separate OID tree, it can quite be a new MIB. Otherwise you can use the UNIQUE flag and set the preferred (e.g. newer, more precise) source for a value first in the list of same-named mappings in existing file - if there's a hit on an actual device, it will be used and not iterated onwards. The flag is not yet supported for

On October 31, 2017 2:32:36 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > >?I'm feeling spunky... and want to update nut to handle the new v2.0 >MIB from CyberPower. > >I've looked at the cyberpower v0.1 .c/.h and being new to working on >nut to this level -- anything anyone has to offer on adding code >besides the obvious? >

On 11/02/2017 01:52 AM, Jim Klimov wrote: > > I believe the main reason for a new set of .c/.h files here would be if the new MIB is defined in a separate subtree. The top-level mapping binds the vendor entry OIDs (often "hidden" so one has to know where to poke). It may also be higher in the list of snmp-ups.h, in case the device also serves the older MIB but you'd prefer the

On November 2, 2017 5:31:42 AM GMT+01:00, Ben Kamen <ben at benkamen.net> wrote: >On 10/31/2017 01:13 AM, Jim Klimov wrote: >> If the new data is in a separate OID tree, it can quite be a new MIB. >Otherwise you can use the UNIQUE flag and set the preferred (e.g. >newer, more precise) source for a value first in the list of same-named >mappings in existing file - if

Chugging along... Question for the gang -- CyberPower lists other items in their MIB for controlling PD units and some other things. Does NUT support all that and should I make an effort to get all that in or should we skip for now and get UPS primary ingredients inserted and tested? just wondering, ?-Ben -- Ben Kamen - O.D.T., S.P.

Build from source, and done . . . wasting your time looking for a less out of date RPM is pointless. . . RPM, .deb, etc are almost always downrev. . . - Tim On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >Hey all, > > I recently got an RMCARD205 for my Cyber UPS.... > >if I use no MIBS line in the config file, I get this: > > >> Network

I did a bunch of work on this today. It should be all set to go. This patch is to add support for the Cyberpower RMCARD snmp cards. I basically copied the driver for bestpower, changed the name and updated the mib map. I have this running on two separate systems (two separate ups's) and it looks good. The only thing I could not figure out was updating the Makefile.am (my aclocal/libtools

On June 11, 2017 8:58:11 AM GMT+02:00, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: >On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >>Build from source, and done . . . wasting your time looking for a less >>out of date RPM is pointless. . . RPM, .deb, etc are almost always >>downrev. . . >> >>- Tim >>

Hey there, I got a new UPS (CyberPower PR1500LCDRTXL2Ua) and found the serial drivers don't quite work... So I decided to jump in and make changes to the driver that would hopefully make it happier. I have it working (I really only changed powerp-txt.c) but still have a couple questions... Charles said I should mention them here to talk to anyone interest but specifically Arjen (one of

root at Monitor:/etc/nut# upsc ups1 Init SSL without certificate database battery.runtime: 133200.00 battery.runtime.elapsed: 0.00 device.mfr: CYBERPOWER device.model: PR2200LCDRT2U device.serial: 1 device.type: ups driver.name: snmp-ups driver.parameter.pollfreq: 1 driver.parameter.pollinterval: 2 driver.parameter.port: 192.168.1.7 driver.parameter.snmp_version: v1 driver.version:

OpenBSD 5.6 nut-2.7.2 (bin package) Liebert IntelliSlot Unity Card IS-UNITY-DP ups.conf: ...... ? mibs = ietf ? snmp_version = v1 ...... The problem is that the card responds to other snmp (v1,2c,3) requests normally but not to the 1.3.6.1.2.1.33.1.1.1.0 (UPS-MIB.upsIdentManufacturer). # snmp-ups -a laes2ups -DDDDDDD Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) ?? 0.000000???? debug

Hi, This appears to be related to a thread from January 2010: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-January/004470.html NB: This is on an HP-UX 11.31 box, using a self compiled and packaged version of NUT 2.6.3, and net-snmp v5.7.1. Therefore some of the search paths and things like that may well be wrong because I've done something dumb. I'm also only just getting

Hi all. I am having an issue and quite frankly would rather not spend the entire next two days learning the entire snmp program. I am hoping someone out there has used MRTG and SNMP to make it work. I have both installed. Single server, polling itself. Question 1- does snmpd have to run as a daemon, or only run once so I can get OID and MIBs from it? Question 2- does anyone know the command

Hey all, I recently got an RMCARD205 for my Cyber UPS.... if I use no MIBS line in the config file, I get this: > Network UPS Tools - UPS driver controller 2.6.5 > Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) > No matching MIB found for sysOID '.1.3.6.1.4.1.3808.1.1.1'! > Please report it to NUT developers, with an 'upsc' output for your device. >

On 10 June 2017 23:26:47 EEST, Tim Dawson <tadawson at tpcsvc.com> wrote: >Build from source, and done . . . wasting your time looking for a less >out of date RPM is pointless. . . RPM, .deb, etc are almost always >downrev. . . > >- Tim > >On June 10, 2017 2:06:42 PM CDT, Ben Kamen <ben at benkamen.net> wrote: >>Hey all, >> >> I recently got an

I have been working with NUT to get this working since upgrading to a web snmp card in a UPS. I keep getting seg faults when running snmp-ups also. Below is the output. kernel: [1365065.178230] snmp-ups[1940]: segfault at 0 ip b7555470 sp bf8d89e8 error 4 in libc-2.18.so[b74c2000+1a9000] Running: Arch i686 current Nut is current git Device is Tripp Lite SU2200XLa with WEBSNMPCARD running

Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! New data added, here is the gdb output: Reading symbols from /usr/bin/snmp-ups...(no debugging symbols found)...done. (gdb) run -a tripplite -DD Starting program: /usr/bin/snmp-ups -a tripplite -DD warning: Could not load shared library symbols for

On Feb 24, 2014, at 10:29 PM, Jason R Begley wrote: > Thanks for the quick response Charles! I may not have gotten the correct output from the snmpwalk, let me know if the attachment is usable. Thanks! Sorry, it's basically all comments. Do you have the stdout from the subdriver script? Also, how is the MIB file installed? > New data added, here is the gdb output: > Reading

On Feb 24, 2014, at 6:57 PM, Jason R Begley wrote: > Segmentation fault That's not good. If you crank up the debug level past 2, does it provide any more detail about where it crashed? (We'd only need the last few lines, if they are different.) I don't know how Arch Linux does debug symbols, so the dmesg output doesn't pinpoint which function in libc got bad data. Can you run

Hi, ? have a necron snmp ups. nut-scanner cant find it. i tried to add with these definition but it fails.. [test5-ups] driver = snmp-ups port = 10.9.40.19 community = asdf12 desc ="test" i run driver with debugging , result is , root at upsviewer-debian:/usr/local/ups/bin# ./snmp-ups -DDDDDDD -a test5-upsNetwork UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000