similar to: [Nut-upsuser] Powerware 9155 with SNMP card

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:

Hi, I got a shiny pair of new PowerWare 9155 UPS (3 input phaes, one output phase), running parallel. Since I didn't want to install a Windows box to run Powerwares software I now went nut(s) ;-) So far things look pretty good, snmp-ups talks to both ups using the pw mib. Though I get these messages, when I start the driver: [ups2] nut_snmp_get: 1.3.6.1.4.1.534.1.4.4.1.3: Error in packet:

Thanks to Olli, I can now talk to my PW9125 via SNMP: > upsc cscfups001@localhost ambient.temperature: 031.0 battery.charge: 090.0 battery.runtime: 2640.0 battery.voltage: 055.5 driver.name: snmp-ups driver.parameter.mibs: pw driver.parameter.port: cscfups001.cs.uwaterloo.ca driver.version: 2.1.0 driver.version.internal: 0.41 input.frequency: 060.0 input.voltage: 120.0 output.current: 020.0

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

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Here are some Powerware compatibility info I got by a colleague, and authorized to publish. @Kjell: can you take over checking our driver.list and other info source to see if there's a gap? thanks, Arnaud ________________________________________________________________________ Old info from ca. 2002, but still mostly valid except that some 5125s got a

Hello... I have a PowerWare 9120 attached via USB to my Debian system. My ups.conf looks like this: [ups1] driver = bcmxcp_usb port = auto desc = "PowerWare 9120" When testing the driver with "upsdrvctl -u root start" I get: Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4) Communications with UPS

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

THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... Please, anybody can help me.... nut-upsuser-request@lists.alioth.debian.org escribi?: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit

Le 23/06/2011 14:00, nut-upsuser-request at lists.alioth.debian.org a ?crit : > Send Nut-upsuser mailing list submissions to > nut-upsuser at lists.alioth.debian.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > or, via email, send a message with subject or body 'help' to >

On 1/2/07, Eric A. Hall <ehall@ehsco.com> wrote: > I can hack up a Cacti PHP script to monitor UPS state via the upsc client > in the meantime. I'll have to manually enumerate the UPS names associated > with a host target (is there a way to probe for them with upsc now?), but > otherwise it ought to be pretty straightforward scripting. NUT developers, The NUT protocol

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

Hello! It looks like bcmxcp driver doesn't fit my device: UPS Model ? ? ? ? ? ? ? ? ? ?PW9125 UPS Firmware Version ? ?FP: 1.10 INV: 1.10 VA Rating ? ? ? ? ? ? ? ? ? ? ?3000 VA Web/SNMP card is present. Minicom connection to /dev/ttyS0 gives nice banner and control menu, but they prevent nut driver from working correctly (I guess). UPS should be switched into "Pass-Through" mode

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I figured out why nut seemed to segfault at startup from my Solaris boxes (and snmp-ups too) - I believe that nut is trying to use some MIBs that do not exist on my particular PW9170, for whatever reason. It dies on my Linux box too, complaining like this: pkdick:~/nut/bin# ./snmp-ups -x mibs=pw -x community=publicstring upsname Network UPS Tools -

Hi Arjen, thanks for the heads up. 2011/5/25 Arjen de Korte <nut+devel at de-korte.org> > Arnaud, > > Since a couple of days I'm unable to connect to SVN since the root CA that > signed the server certificate of 'svn.debian.org' is not trusted. I guess > this is because the previous certificate was no longer valid. My question > is, if this is only a

On Tuesday 10 June 2008 08:00:39 am nut-upsuser-request at lists.alioth.debian.org wrote: > Message: 2 > Date: Tue, 10 Jun 2008 10:58:11 +0200 (CEST) > From: "Arjen de Korte" <nut+users at de-korte.org> > Subject: Re: [Nut-upsuser] Nut-upsuser Digest, Vol 36, Issue 5 > To: "Alex Peyser" <a.peyser at umiami.edu> > Cc: nut-upsuser at

It is possible at least on linux to get the port associated with a device from userspace - I'd assume that on each platform it's possible, just that libusb is incomplete (on top of being undocumented). Here's a patch for matching portnum on linux, with a few pieces pulled from libusb. It lacks autoconf macros to isolate it -- but it does appear to work. Regards, Alex Peyser On

Hi Georg, > one question with regard to a Powerware 5115 UPS connected to a Debian 3.1 > Sarge box via USB: I downloaded and compiled nut 2.0.2 but I am unable to > configure the USB subsystem so that upsdrvctl recognizes the UPS. > > My /usr/local/ups/etc/ups.conf contains: > > [bla] > driver = bcmxcp > port = /dev/usbdev2.2 > desc = "bla bla

I am using nut-snmp driver on ubuntu 8.04 to query a Powerware ConnectUPS Web/SNMP Card V4.20. With 0.41 I used to be able to query these field that are now gone with 0.42: input.frequency input.voltage output.voltage ups.load Any idea how I can get ups.load back ? -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi all We're considering getting some Powerware 9355-30-M-0 UPSes to replace some older ones, so I wonder if it would be possible to use NUT for this. It seems 9315 is supported, but AFAICS that's the top model. Thanks roy -- Roy Sigurd Karlsbakk (+47) 97542685 roy at karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det