similar to: HP R12000/3 UPS reports status as OL DISCHRG OB

Here's the first update of ups.status: 0.102449 getting data: ups.status (.1.3.6.1.4.1.232.165.3.4.5.0) 0.102546 su_ups_get: ups.status .1.3.6.1.4.1.232.165.3.4.5.0 0.102646 nut_snmp_get(.1.3.6.1.4.1.232.165.3.4.5.0) 0.104539 SNMP UPS driver : entering su_status_set() 0.104641 su_find_infoval: found OL (value: 3) 0.104730 => value: 3 0.104823 getting data: ups.status

Sorry about that! Chris. Chris Pratt Development Infrastructure Manager T: +44 118 929 4176 | M: +44 7979 854 307 | F: +44 118 929 4001 -----Original Message----- From: Charles Lepple [mailto:clepple at gmail.com] Sent: 16 July 2013 00:32 To: Pratt Chris Subject: Re: [Nut-upsuser] HP R12000/3 UPS reports status as OL DISCHRG OB On Jul 15, 2013, at 9:35 AM, Pratt Chris wrote: > Debug output

On Jul 15, 2013, at 6:17 AM, Pratt Chris wrote: > Hi. > > Back before Christmas Arnaud sent me a patch for the snmp-ups driver for my HP R12000/3 UPS. Unfortunately shortly after I had to take quite a lot of sick leave so wasn?t able to progress it, but I?m working on it again now. Hi Chris, Is this the patch you are referring to?

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

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

Hi all, I recently upgraded an ubuntu jaunty machine with nut 2.4.1 to lucid LTS. The previously working nut configuration is a no-go, but I got it up and running using the snmp-ups executable from the previous install. What it happens (from what I can see at least) is that the status has been changed and it's not read as before. In the 2.4.1 release I had an "OL" string (online, I

Hi. I'm trying to configure NUT to manage a HP R12000/3 3-phase UPS fitted with an AF401A management module but it immediately crashes with a segmentation fault. O/S is CentOS 6.3 64-bit NUT built from tarball AF401A Firmware version 2.1.3 Extract from /etc/ups/ups.conf [UPS-HP01] driver = snmp-ups port = 192.168.0.89 desc = " HP R12000/3 UPS"

Hi! Have a similar issue with one of our customers having HP R12000/3 UPS with AF430A card. Upsmon shows the UPS as Online, on Battery and Battery discharging at the same time: [root at smrsrvslv06 lib64]# upsc hpups at localhost ambient.temperature: 19.0 ambient.temperature.high: 0.00 ambient.temperature.low: 0.00 battery.charge: 94.00 battery.current: 0.00 battery.runtime: 4620.00

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:

Hello all, as users of certain (primarily CyberPower and APC) devices know, some firmwares report both "online" and "discharging" in some situations. These depend on the device, vendor and firmware, but cases seen in practice include: * calibration (APC), * being on-battery (CPS), * having got charged to 100% (APC) Recent attention to this area culminated in PR

Hi Charles, 2015-03-29 0:44 GMT+01:00 Charles Lepple <clepple at gmail.com>: > On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com> > wrote: > > > 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with > the complementary ones for battery.charger.status. And advocate (document) > for the use of / switch to the latter, that is

Hello Arnaud, On 05/04/14 22:01, Arnaud Quette wrote: > Philippe, Ivan, > > please see https://github.com/networkupstools/nut/issues/118 > and send back your data. I've pasted the requested files in github, but the auto-formatting may have damaged them, so here they are. Also, when I ran gen-snmp-subdriver.sh, it gave me the following message:

Philippe, Ivan, please see https://github.com/networkupstools/nut/issues/118 and send back your data. cheers Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140405/682f10dd/attachment-0001.html>

Hi NUT developers, part of the 2.7.3 release, we are about to merge the below branch / PR for the bcmxcp drivers family: https://github.com/networkupstools/nut/pull/158 https://github.com/networkupstools/nut/tree/pull_158_bcmxcp_rebased It has introduced the battery.charger.status variable, which is something I wanted to implement since around 2007. However, while considering a similar

On Mar 25, 2015, at 4:11 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > 1) Keep the legacy CHRG / DISCHRG status bits for ups.status, along with the complementary ones for battery.charger.status. And advocate (document) for the use of / switch to the latter, that is more suitable for publishing such information. All that with an impact on all the NUT driver, and a transition

Hi all! I'm wondering if there's anyone doing any hacking on the snmp-ups driver at the moment. I've started looking at implementing 3phase-support, and this uncovered some rather unpleasant stuff in the snmp-ups driver that I really need to fix in order to get things sane. Those of you that's allergic to SNMP might want to stop reading now, this is rather icky ;)

Hello We have an Socomec Sicon Netys PR3000 UPS equipped with NetVision Web/SNMP adaptor. I try to monitor the ups using snmp-ups driver and netvision mibs set. The snmp-ups driver starts correctly and connects to the UPS, upsd confirms it, but upsmon constantly shows "No communication" error I think the cause is the SNMP adapter reports the UPS status as "ECO mode"

(was: false alerts/shutdown) 2007/6/18, Arjen de Korte <nut+devel at de-korte.org>: > > > driver.name: newhidups > > [...] > > > ups.status: OL CHRG > > Euhm, there is no status 'CHRG' according to 'docs/new-drivers.txt' > folks. If you feel the need to create new status flags, at the very > least mention them in the section 'Status

On Sat, Jun 27, 2020, at 23:11, Manuel Wolfshant wrote: > On 6/28/20 5:54 AM, Scott Colby wrote: >> >> I'm not convinced this is the problem; I think that pfSense has an alternative way of running the NUT components: # ps aux | grep ups root 45456 0.0 0.1 6796 884 - Is 02:22 0:00.01 /usr/local/sbin/upsmon uucp 45751 0.0 0.1 6796 772 - S 02:22

I'm running nut 2.0.1 with an MGE pulsar evolution 3000 with the mge-utalk (serial) driver on NetBSD 3.1 . I had a very strange occurance in my basement datacenter this early AM. the following was logged by upslog: 20080219 023452 100.0 123.0 049.0 [OL CHRG] NA 60.00 20080219 023522 100.0 122.8 049.0 [OL CHRG] NA 60.00 20080219 023552 098.0 123.0 049.0 [OL DISCHRG] NA 60.00 20080219 023622