similar to: NUT namespace: RFC for new variable addition

I've recently been working a bit on adding PDU (http://en.wikipedia.org/wiki/Power_distribution_unit) support in NUT. Some of you might have seen the Powerman thread, which also deals with adding more PDUs support: http://powerman.sourceforge.net/supported.html The result is that we now have support for 2 Eaton | Powerware ePDUs (Managed and Monitored iirc, check http://www.epdu.com). I plan

On Aug 4, 2017, at 3:00 AM, Arnaud Quette <arnaud.quette at gmail.com> wrote: > > Comments and feedback warmly welcome. > Please however note that I'll be pushing the related commit, since it seem trivial. It does sound trivial, but do we have that sort of information for other PDUs, and if not, how should names be represented in a GUI if outlet.n.name isn't present?

Hi Powermen ;-) I recently came across the Powerman project (http://sourceforge.net/projects/powerman/), pointed by Tony Merenda, from Opengear (thanks Tony). Congrats for your work in this area! I've thought a bit about Powerman and NUT since then... NUT currently supports hosts of UPSs and few PDUs (RPCs), and provides tons of features: http://test.networkupstools.org

Hi guys, I'm very new to NUT, and power monitoring in general, so please forgive me if this question is dumb. I'd like to write a Linux app that will know, in approximate real-time, how much power is being drawn by a computer plugged into an outlet. Is NUT well-suited to this usage? And if so, can anyone recommend relatively cheap monitoring hardware (ideally less than $200 US) that

Hi fellows, I'm really pleased to announce that a first stage of NUT and HAL [1] integration has been reached: NUT drivers (in fact, only newhidups, tripplite_usb and bcmxcp_usb for the moment) can feed HAL data. It's a "quick and dirty" hack, as a proof of concept, and there is still lots of things to be done, both on NUT and HAL sides. But it's a good base, and very

Hello, we have a MGE Pulsar Evolution 800 connected to a Fedora Core5 Server using a serial cable. Installed and configured properly are RPM versions of nut-2.0.3-0.1.fc5 nut-client-2.0.3-0.1.fc5 nut-cgi-2.0.3-0.1.fc5 which all work (mostly) fine. The server is connected to outlet.0 and properly shuts down when it's loosing power after around 20 minutes. It also boots up whenever the ups

Hi all, in order to track which phase (L1, L2, L3) feeds a physical outlet groups on a rack PDU, I'd like to extend the NUT namespace to add a new variable: outlet.group.n.phase Details and implementation can be found on: https://github.com/networkupstools/nut/pull/422 Comments and feedback warmly welcome. cheers, Arno -- Eaton Data Center Automation Solutions - Opensource Leader -

Hi all, here is another one, related to ATS (automatic transfer switch) this time. in order to track "dephasing" between input sources (1 and 2), I'd like to add a new variable: "input.phase.shift" Details and implementation can be found on: https://github.com/networkupstools/nut/pull/433 Comments and feedback warmly welcome. cheers, Arno -- Eaton Data Center

Hi all, here is another variable addition, related to iPDU, that I'd like to make: outlet.group.n.color | Color of outlet group (hex code) | #daa520 For the sake of completion, Eaton ePDU outlet groups are identified with a color code on the device itself: http://powerquality.eaton.com/images/product-images/ePDU/more-images/EMA324-10DaisyChainWith2.jpg Here the first group

Hi, I am trying to talk to an MGE Pulsar Extreme UPS over RS232 with the mge-shut driver but I'm having some problems. It appears to init OK but I can't, say, turn the outlets off, eg.. harrow:~>upsc mge@localhost battery.charge: 78 battery.charge.low: 20 battery.runtime: 05760 driver.name: mge-shut driver.parameter.port: /dev/cuad1 driver.version: 2.0.3 driver.version.internal: 0.65

I was looking at how other drivers deal with outlet collections, and I noticed some differences between newhidups in 2.0.4 (from Debian's 2.0.4-2.3) and the SVN trunk (rev 723) on an Evolution. Full diff is below, but here are the highlights: * MGE HID 0.9 vs 1.0 * outlet.#.switch seems to have moved to the commands outlet.#.load.{on,off} Then I found this in the ChangeLog: * fix

Hi, I have recently purchased MGE ellipse 1200 UPS for my home system. Obviously, the choice of this particular brand was mainly dictated by MGE's long-standing support for Linux and NUT project. The fact that the box was clearly the prettiest looking one on the block did help also ;-). I have had NUT tools installed and configured in no time, as I did it numerous times before -- kudos

On May 24, 2017 1:08:09 PM GMT+02:00, Charles Lepple <clepple at gmail.com> wrote: >On May 24, 2017, at 5:11 AM, Arnaud Quette <arnaud.quette at gmail.com> >wrote: >> >> Hi all, >> >> here is another one, related to ATS (automatic transfer switch) this >time. >> >> in order to track "dephasing" between input sources (1 and 2),

Hi Kjell, a few notes: - you should bump the DRV_VERSION upon every change - you should track the drivers TODO list in a comment header (such as "implement smart load segment detection" completed with your info, ...). That would help to bootstrap new contributors. - you can also use the alioth trackers (features request, or task) to give some external visibility on what remains to be

Hi, I have several Linux machines at home and I'm considering buying a UPS for them. I see that many models are supported by NUT (great!) but since I'm new to the UPS world I have some questions about UPS features and NUT support of them I couldn't find an answer for: 1/ are there UPS models who report/meter power usage through USB? per UPS socket or globally? 2/ are there UPS models

On Wed, Jun 22, 2016 at 11:08 AM, Barak Korren <bkorren at redhat.com> wrote: > > > > My question is: Is this even possible? All the documentation for HA that > I've found appears to not > > do this. Am I missing something? > > You can use oVirt for that (www.ovirt.org). > When an UNCLEAN SHUDWON happens or ifdown eth0 in node1 , can OVIRT migrate VMs

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! We have two MGE Evolution 1100 here, and I want to make use of the powershare outlets to force a particular boot sequence on the machines powered by them. However I'm not sure how to set those variables upon NUT starting, without having to change the init scripts to call "upsrw". Is there some place where I can set them, where they can be read automatically on startup? One of

fellows, You can now commit to the trunk everything that is scheduled for 2.4 For my part, the november month will be mostly dedicated to the following: - commit the USB "improved maintenance" code. I'm about to finish that one, which allows to extract USB info and generate the various USB related files (hotplug, udev and hal). so the end of that bothering era ^_^ - complete &