similar to: APC 1500 USB problem

Hello, I've got a setup with NUT, where we've got two UPSes, ups1 and ups2. UPS1 supports our servers, while UPS2 supports our desktop boxes. We monitor both of them via USB on a box now called "upsmon". The interesting point comes here. We monitor both UPSes on the upsmon box, but if UPS2 fails, which supports our desktop boxes, NUT shouldn't initiate a shutdown in

Hello I'm having a bit of a trouble to set up a Back-UPS on a production box. We're using the newhidups driver for this module here, in the office, and I'd like to monitor the one, out in our server farm. The situation is the following: # /lib/nut/newhidups -u root -DD -a ups1 2> ups1.out Network UPS Tools: 0.28 USB communication driver 0.28 - core 0.30 (2.0.5) this one worked

Hi, I've got two MGE Ellipse 1500 UPS connected via usb to an ubuntu jaunty system with nut and libupsclient1 2.4.1-2ubuntu4. As soon as I start the driver for the second one, they start fighting each other and I get no data. I found an older post to this list that said: If you want to monitor multiple UPSes through usbhid-ups, you *must* make sure that each one can be uniquely identified

New NUT install dealing with three APC Smart-UPS 5000s, two of which have AP9617 and the third has a AP9619 card. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three

Hi, I've got a question about managing two UPSes under NUT. I have two similar model APC usb-connected UPSes to work with, but don't know how to manage them simultaneously from under Windows. Long story short, my ups.conf looks like this: --- ups.conf --- [ups1] driver= usbhid-ups port= auto serial=AS1054340323 [ups2] driver= usbhid-ups port= auto serial=AS1026662626 ---

Hi, I didn't found an answer for my question in NUT documentation/FAQ or this mailing list archive so I?m posting it here. I want to start a timer only if both of my UPSes remain on battery. Not just one, both. My UPSes are: - ups1@host-a - ups2@host-b Is it possible to use something like this in upssched.conf? AT ONBATT ups1.* && ups2.* START-TIMER onbattwarn 180 Thanks,

Hi Charles, Running upsdrvctl -D start on the host with all three configured to SNMPv3 kicks out 56 different "unhandled ASN 0x81 from ..." lines on all three but importantly they all start up and keep running. I'm starting to suspect the startup is taking so long that systemd is timing out and killing it. time -p reports real time of 133.27. I'm not a fan of systemd but

I can't find a way to configure bcmxcp_usb to communicate with 2 UPS units. Maybe more simply, I can't find a way to tell the driver to only talk to one of the units on the bus. That is, I cannot find that the driver configuration file supports "serial =" or "bus = " or other such discriminators that other drivers do (usb_apc, etc.). So, I can't assign one Eaton

I have three APC SmartUPS 5000s. Two of them are AP9617 and one is AP9619. I have a RS-232 connections from my monitor host to all three. All three report status and give information. One of the two AP9617 - ups3-1 - does not shut down when FSD is sent. It did when I first set this system up a year or two ago but it's stopped doing so since then. Resetting the management interface does not

Hi all, I have an APCC Back-UPS XS 1000 (it's a USB device) that I'm using with nut 2.0.2 that came with Fedora Core 4. It reports itself like this: Back-UPS RS 1000 FW:7.g8 .D USB FW:g8 in the nut web status page, which seems a tad messy. It otherwise works fine, except I don't get any information on the input and output voltages. I'm using the hidups driver. My

I am currently trying to use your NUT program to monitor a SMART3000RMOD2U TRIPP LITE device. I find that it connects with the in the device folder as hiddev0 and if I connect a second device it connects under hiddev1. I attempted to use your software with the driver=usbhid-ups and port=auto, but when I try to discover it it can't be found. Then when I run the command /sbin/usbhid-ups -a

I'm trying to setup a server controlling 8 ups, 6 APC Smartups 1500 and two 1000. Because of the number of ups, i connected them using usb cables. I'm using Debian Etch AMD64 and nut 2.2.0 from testing (already tried 2.0 from stable, but had problems reading the ups serials and all the following problems of 2.2). This is my ups.conf: [ups2] driver = usbhid-ups port =

Hi, I have had a long standing problem with NUT talking to 110V MGE UPSs on FreeBSD, I was recently investigating again and noticed that upsd seems overly noisy, eg.. May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5 03:50:36 egbert upsd[96662]: Data for UPS [ups1] is stale - check driver May 5 03:50:36 egbert upsd[96662]: UPS [ups1] data is no longer stale May 5

Hi, this is the 2nd part of the PowerChain RFC. 2011/6/13 Arnaud Quette <aquette.dev at gmail.com> > As already presented, the links below will describe in details the > PowerChain notion: > > https://wiki.ubuntu.com/ServerOneiricInfraPower > https://wiki.ubuntu.com/ServerOneiricInfraPower#PowerChain%20design >

(Note that I mentioned this *was* previously working with an older version of Nut). [irs2-ups1] driver = snmp-ups port = irs2-ups1.sum.naoj.org mibs = auto community = private irs2-ups1.sum.naoj.org responds to pings. On Tue, Oct 8, 2013 at 3:55 PM, Tim Rice <tim at multitalents.net> wrote: > On Tue, 8 Oct 2013, Philip Tait wrote: > > > Here is the upsc

Hello!! I'm a sysadmin at La Laguna University in Spain. We are using NUT to manage our UPS with great success, but we miss a feature and we would like to send this patch to you. If you apply this patch running upsd -c info you'll get information about client connections in syslog. This is very simple and helpfull if you have hundreds of servers connected to the same upsd. Thank you for

Hi, I've stumbled over a race condition in upssched when using 3 or more UPSes in combination with START-TIMER/CANCEL-TIMER. I have a solution that works but is ugly, so I'm going to describe the bug here in the hope somebody can come up with a better solution. The problem is in upssched.c:629 check_parent() (see https://github.com/networkupstools/nut/blob/master/clients/upssched.c ).

Hi, my name is Sebasti?n from Spain I need help for that. I have 2 salicru ups I need monitor with a fedora 14 pc. Someone knows if i can configure ups.conf to monitor one or another ups? only make a upsc "ups" for take data. The upses are connected via usb and nut always read the first one connected. The upses are the same model. Thanks for all! Sebasti?n Le?n del Moral urticaries at

I'm trying to set up nut with a MGE UPS equiupped with a network management card, but encountered a problem. UPS: MGE Pulsar M 3000 Network Management card (installed in the UPS): 66102 (2006 edition) Operating system: FreeBSD Nut port version: 2.0.5 Nut driver: snmp-ups According to MGE in Norway this card is supported by nut, but only the old version of the card (66244) is listed on

Hi, I have the above UPS connected to a FreeBSD 6.2 box and it shows 'data stale' very frequently (every few minutes). I have tried the usual trick of setting maxage, poll interval, etc etc but to no avail. When I wind up logging I see (on mge-shut) entering shut_get_report(id: 0d, len: 1800) shut_wait_ack(): ACK received entering shut_get_report(id: 16, len: 1800) shut_wait_ack():