similar to: CPQPOWER-MIB - nearly there

Hi Folks, I've tested and tidied it up. Please accept this contribution for consideration. The patch for snmp-ups.c is against the latest (at 10 am GMT) svn. Any changes you'd like made and tested, please let me know. Regards, - Philip Ward Unix Systems Administrator Ext 7274 -- The Sunday Times Scottish University of the Year 2009/2010 The University of Stirling is a charity

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, I've been asked to add upsBatteryAbmStatus to the cpqpower mib. We use it purely for the CGI display. Here are the patches for data/cmdvartab and drivers/cpqpowermib.h - Philip Ward Unix Systems Administrator Ext 7274 -- The Sunday Times Scottish University of the Year 2009/2010 The University of Stirling is a charity registered in Scotland, number SC 011159. -------------- next

Hi, I would like to contribute code to make the SNMP driver compatible with HP's AF401A UPS module. It is also compatible with HP's older SNMP modules. It's just a new mib specification plus the necessary changes to snmp-ups.c Several sources have told me that these UPSs use the cpqpower.mib, but comparing that mib at http://www.snmplink.org/cgi-bin/nd/m/Ent/H/Hewlett

We use HP R5500XR UPS, and they all have SNMP cards. These devices supposedly use the IETF MIB, but in order to get the SNMP driver to talk to them I have had to hack it slightly. I'd like to see these UPS proplerly supported in the official nut release (mostly so I don't have to faff around patching and repackaging when a new version comes out) and would be more than happy to provide

Here's a patch (against 2.2.2) which adds battery.temperature to the ietf-mib snmp driver. While looking at ietfmib.h I noticed that the value for IETF_OID_IN_LINES is actually that for upsOutputNumLines.0. Does anyone know whether that's deliberate or a typo? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/x-patch

What follows is a sample of the output of svn2cl for the trunk. I added the username-to-email mapping file, enabled revision numbers, and told it to group commits on a single day by the same author: $ svn2cl --group-by-day --include-rev --authors=../../svn2cl.authors Arjen: I used your main email address that you typically list in the ChangeLog entries. Arnaud: I wasn't sure which address

Additional question: I noticed on the HP Website that the latest version of "CPQPOWER.MIB" (1.76, dated Sept. 19, 2013) was more recent than the related file (./drivers/compaq-mib.c) in the NUT driver. Is the MIB structure as implemented on the management card perhaps no longer in line with the NUT driver ? The latest MIB file can be downloaded from the following URL:

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

Further information on this issue, attn. Arnaud Quette: Here is the result of a test I made a few days ago. I've pulled the input plug on the UPS and watched the 3 critical OIDs through a MIB browser: - 1.3.6.1.4.1.232.165.3.4.5.0 goes from 3 (OL) to 5 (OB) (as expected => good) - 1.3.6.1.4.1.232.165.3.7.3.0 stays at 1 (OB) (=> seems meaningless) - 1.3.6.1.4.1.232.165.3.7.4.0

Hello list, I've installed NUT on an HP blade server, and I try to get it communicating via SNMP with 2 HP R3000 UPSes, each fitted with a AF465A management card. To do this, I used the snmp-ups driver, and configured it for the "cpqpower" MIB. Communication with the UPSes is established. My problem is that both UPSes constantly return the "OL OB" status which, in

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The snmp-ups driver 2.6.4 as packaged with Debian wheezy crashes when talking to a UPS that uses the CPQPOWER MIB. I have built 2.6.5 from source and found the same problem. On July 29th I grabbed the latest source from svn, built it and now have a working snmp-ups driver. Would it be possible to update the debian package? I'd be happy to help

On Aug 26, 2013, at 6:11 AM, Philip Ward wrote: > The snmp-ups driver 2.6.4 as packaged with Debian wheezy crashes when > talking to a UPS that uses the CPQPOWER MIB. I have built 2.6.5 from > source and found the same problem. > > On July 29th I grabbed the latest source from svn, built it and now > have a working snmp-ups driver. > > Would it be possible to update the

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

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

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 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, I have two UPS SMART-UPS 2200 RM both of them have the same configuration.One of them works fine, but the other one it doesn't, it output as follows: snmp-ups -D -a nutdev10 Network UPS Tools - Generic SNMP UPS driver 0.72 (2.7.2) 0.000000 debug level is '1' 0.001013 SNMP UPS driver : entering upsdrv_initups() 0.048606 trying the new match_sysoid() method

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