similar to: snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card

Hi, I am using the NUT Software 2.7.4 (Ubuntu Repository) on Ubuntu 18.04. Configuring a UPS with the snmp-ups driver and overriding the battery.runtime.low variable leads to following warnung/error: Sep 23 11:10:08 hostname snmp-ups[27115]: dstate_setflags: base variable (battery.runtime.low) is immutable Default for battery.runtime.low is 180 seconds. My idea is to increase the value to

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

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"

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:

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, Trying to add support for my unit, which is a 3-phase UPS. I can't find any oids that holds that data so I can determine that, so I think I need to add it statically. I've tried the following, (nut-2.7.2) ... { "input.phases", 0, 1.0, NULL, "3", SU_FLAG_SETINT, NULL, &input_phases }, ... That ends up as (snmp-ups -a foo -DDDD) ... 0.177686 getting

Hello, I have two UPS from PowerWalker: VFI 1500RM LCD and VFI 3000RM LCD both equiped with SNMP card, but NUT with snmp-ups does not support them. PowerWalker declare support RFC1213, RFC162 but there is a problem with some snmp values: # upsdrvctl start Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Generic SNMP UPS driver 0.66 (2.6.4) Detected 3K on host 10.0.0.236

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

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

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. I'm at the point where I can start the driver with upsdrvctl and start the daemon with upsd. When I check the UPS status though it shows as OL DISCHRG OB,

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 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 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 ;)

Hi Matthijs, > Arnaud. >After some trial and error, i found out that the HP R3000 XR ups's we have >can be used with Network Ups Tools. >This using the bcmxcp driver. > >Note that in the code of this driver (line 1420) , the Baudrate is fixed to >9600 baud. >to connect to a serial HP R3000 XR ups one needs to change this to 19200 >baud. > >ideally, this should

Hi All, I put my Compaq R3000 UPS on NUT. Every once in a while the battery alarm light turns on, on the front of the UPS. Maybe once every couple of days or so. When that happens I get the following output in /var/log/messages: Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: .20 MOUL1 Sep 22 01:51:46 mail upscode2[90734]: Unknown response to UPDS: 0119.20 MOIL1 Sep 22

Hi, So far I've gleaned heaps of useful info from the list and got mostly running with NUT. There was a thread by Paul Battaglia and Kjell Claesson about the R3000 which has helped me get so far, but now with the patched driver I still have this on startup: # /usr/local/ups/bin/upsdrvctl start Network UPS Tools - UPS driver controller 2.0.5 Network UPS Tools - BCMXCP UPS driver 0.11

Hello Paul and Simon, (Sorry - I'm not sure about the social conventions in mailing lists) Both of your answers helped me a lot! So If I understand it correctly, Clang knows what 'mips1' and 'mips5' are - but can't generate code for it? Why is it like that? I actually have a more in general questions about processors... If this is the wrong place for it, please ignore it,

Hi there. I need some advise on how to configure NUT, if it is possible to do it. My UPS, a Compaq R3000 has three individual power segments. I want NUT to: When mains is interrupted. Shut down all serves immediately. When all servers are completely down, in sequence with time delay shut down two of the power segments. When batteries is about to be depleted shut down itself and the last power

Hi I have a HP R3000 XR UPS which NUT never says is at 100% battery. It seems stuck in 98 or 99 . something percentage. How accurate should i expect the reports to be? All my other UPSes has been and is at 100%, even those i have retired. My monitor system runs debian. The host that is physically connected to this ups runs: nut 2.2.2-6.4 The web script runs nut-cgi 2.0.4-4 JonB