similar to: Powerware 9155 with SNMP card

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

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

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

Hi, I just installed NUT to monitor 4 UPS, all APC, all with Network card APC 9617. NUT have problem to access the following SNMP OID on all the UPSes: Detected Smart-UPS 3000 XL on host apc4.cs.ait.ac.th (mib: apcc 1.1) [apc4] nut_snmp_get: .1.3.6.1.4.1.318.1.1.1.9.2.2.1.2.1: Error in packet: (noSuchName) There is no such variable name in this MIB. [apc4] nut_snmp_get:

I am working with three Liebert GXT2 UPSes connected via local TCP/IP under Linux 2.6.25.1 and getting a series of messages. First, at start, the drivers complains that the Liebert apparently extract information from certain MIBs in the ietf MIB file.... Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools - Multi-MIBS SNMP UPS driver 0.421 (2.2.2) Warning: This is an experimental

This mib used to work, so is there a way to go back to the version prior to this one without downgrading the whole package? * Starting UPS drivers... Network UPS Tools - UPS driver controller 2.4.1 Network UPS Tools - Generic SNMP UPS driver 0.44 (2.4.1) Detected GXT2-2000RT120 on host upswallleft (mib: ietf 1.3) [upswallleft] nut_snmp_get: 1.3.6.1.2.1.33.1.4.4.1.4.0: Error in

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

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

I use Wine release 20011226, and I am ver happy every time I can run my small windows-programs without booting into dos. However I try to run management from ORiNOCO, orman.exe, under wine and run in to some trouble. This program sends out an SNMP GET to retrieve info from the agent, but under wine the OID in the package is sometimes wrong. wine: GetRequest E:762.2.5.2.1.25.0

> It is a pleasure for me to help NUT Project and I will order a SNMP Web > card 66102 to following address [ address information removed ] > Is it OK ? (if yes, the order could be issued on next Monday) That would be a great help, I appreciate that. It's just too bad that you CC'ed the NUT development mailinglist with my full (private) address information. I'd rather keep

Gentlemen, Please note that what follows pre-dates the latest changes from Arnaud (just thought someone might want to look at these before I can test the latest!). When running newhidups with -D -D -D I saw messages that looked like errors, and it took me a while to understand that they were not really errors. I therefore added two new entries in apc-hid.h, and I modified a couple of diagnistic

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

Arnaud: in today's commits, I removed three lines that you apparently added on August 10: 1.1.1.1.8.1 (aquette 04-May-05): if (mode == HU_WALKMODE_INIT) 1.1.1.1.8.1 (aquette 04-May-05): { 1.1.1.1.8.1 (aquette 04-May-05): dstate_setflags(item->info_type, item->info_flags); 1.1.1.1.8.6.2.5 (aquette 10-Aug-05): /* Verify variable setability/RW */

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

Hi, I been using samba4 from git15 version of 4.0.0, when samba4 hit stable we made it a main ADDC. Around 4.0.6 or later, I stuck on a DNS problem (which results in stop responding to clients from time to time, channging to BIND didn't help when we tried some time ago. I would like to fix those problem with reinstalling DC, but first I would like to replicate it to other DC so AD trust wont

hi @ all, i just wonder, if it is posible to read the values for all the three phases of a mge galaxy 6000 ups? we have unfortunately one mge comet ups (one phase) to play at work, but it is important to know, how many information upsc can deliver from a galaxy. we plane to use web / snmp interface. can someone post the upsc from such ups? thanks in advance, miroslav -- SHALTEV.ORG

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

Hi, the diff inline below adds a new subdriver for snmp-ups to support Huawei UPS, based on an observed walk from a UPS5000-E with a few bits filled in from the MIBs (copy at http://junkpile.org/HUAWEI_UPS_MIB/). Sample output from upsc follows the diff. cheers, Stuart diff --git a/data/driver.list.in b/data/driver.list.in index a0e82fb..fac3d5a 100644 --- a/data/driver.list.in +++

G'day I'm currently using NUT on Debian squeeze box in the same subnet with an IBM 3000 HV (branded Eaton 5125 with Web/SNMP card), now I wanted to get our storage appliance running NexentaStor 3.1 set up to be using NUT too. Nexenta- Stor is an OpenSolaris / illumos-based appliance OS currently using NUT packages from ubuntu hardy. My question here is whether I'm running into a -

--- Arjen de Korte <nut+users at de-korte.org> wrote: > > > I also did: > > > > # ./megatec_usb -DDDDD -x vendor=06da -x mfr=OMRON > > /dev/usb/hiddev0 > > Please have a look at 'man 8 megatec_usb' again. > > You probably need to specify the '-x vendorid' and > '-x productid' options > and most likely, the