similar to: Patch for addition of Cyberpower RMCARD100, 201, 202, 301 (snmp mib)

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

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

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

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

The problem will only affect newer firmwares on the BestPower FerrUPS 2.1kva units. Additional white-space was the issue. I added a if clause to the bestfcom driver to account for this without breaking what was there. Here is the patch: diff -rupN release-orig/nut-2.7.1/drivers/bestfcom.c release-patched/nut-2.7.1/drivers/bestfcom.c --- release-orig/nut-2.7.1/drivers/bestfcom.c 2013-07-31

I did the testing you suggested, and it was indeed the whitespace. I added another if clause test to the function and everything seems to work. I have working driver that I will email a patch for this list. My coworker says the model ID is configurable though, so we will try that first, which would negate the need to patch the driver. ________________________________________ From: Charles Lepple

Hi, the diff inline below adds a new subdriver for snmp-ups to support Huawei UPS, based on an observed walk from a UPS5000-E with a few bits filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). Sample output from upsc follows the diff. cheers, Stuart diff --git a/data/driver.list.in b/data/driver.list.in index a0e82fb..fac3d5a 100644 --- a/data/driver.list.in +++

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

Greetings to you all, We are attempting to use NUT to interface with a BestPower FerrUPS FE2.1KVA. We are using the bestfcom driver because the driver listed our UPS as supported. The driver fails, however, because "fc" commands do not exist on the unit. We are running NUT v2.7.1 on CentOS 6.5 with the bestfcom driver. We setup a serial tap and see the UPS error out on the fc command

On Feb 7, 2014, at 3:44 PM, Ritter, Nicholas wrote: > Greetings to you all, > > We are attempting to use NUT to interface with a BestPower FerrUPS FE2.1KVA. We are using the bestfcom driver because the driver listed our UPS as supported. The driver fails, however, because "fc" commands do not exist on the unit. There is a upsdrv_init_nofc() function, but it seems to be

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

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? like: should the 0.1 and 2.0 coexist somehow? (maybe different files) (also, is there a list of all the parms I can match up from the

> I will try to remember to update the list of unsupported characters. Done. > Hmm, I will have to look at some of the dependencies - the "Last updated" dates aren't getting modified. (I am just doing a "make" (all) rather than "make dist" since I don't have a new NUT tarball or the GPG key.) What do we want to do with 'Last updated' and

Hello, i'm trying to monitor a APC Smart-UPS 1000 behind a APC AP9630 Network Management Card via SNMPv3 using the AES Privacy Protocol. * OS name and version: Debian 10.1 * exact NUT version: 2.7.4 * NUT installation method: from debian package 2.7.4-8 * exact device name and related information * Model Number AP9630 * Hardware Revision 08 * Manufacture Date

On 22:17, Thu 25 Sep 14, Charles Lepple wrote: > > I think the OMNIVS800 protocol 2012 entry came from Tripp Lite test results. (There have definitely been naming collisions in the past; hence, the messages in the drivers if you accidentally choose the wrong one.) > > Confusingly, if the USB ProductID is 0001, the Tripp Lite specific "Protocol" number (shown in

Hi, I'm trying connect a device: * OS name and version: root at nut:/etc/nut# hostnamectl Static hostname: nut Icon name: computer-vm Chassis: vm Machine ID: d7a3b7fc724f4fe1a79a3d0eeff08f72 Boot ID: 40a561c464064b5184150f5909af0aa7 Virtualization: vmware Operating System: Debian GNU/Linux 9 (stretch) Kernel: Linux 4.9.0-9-amd64 Architecture: x86-64 * NUT version

On 2/24/2014 11:10 PM, Charles Lepple wrote: > 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?

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

Here is the upsc output: # /usr/local/ups/bin/snmp-ups -DD -a irs2-ups1 Network UPS Tools - Generic SNMP UPS driver 0.68 (2.6.5) 0.000000 debug level is '2' 0.000327 SNMP UPS driver : entering upsdrv_initups() 0.000341 SNMP UPS driver : entering nut_snmp_init(snmp-ups) 0.056112 SNMP UPS driver : entering load_mib2nut(auto) 0.056126 trying the new

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