similar to: monitoring Eaton parallel/redundant UPSs

I'm setting up a NUT server. During testing, I have deployed it on both CentOS and SUSE. I have both servers looking at two physical UPSs and two "dummy" UPSs. My NUT client is running on Solaris and is rigged to look at the "dummy" UPSs. As I toggle states on the dummy UPSs, the client correctly detects the changes and throws a message of the type: > Broadcast

I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. Can anyone share a how-to for solaris? -- Do things because you should, not just because you can. John Thurston 907-465-8591 John.Thurston at alaska.gov Enterprise Technology Services Department of Administration

On 7/1/2013 8:27 PM, Bernd Markgraf wrote: > On Mon, 2013-07-01 at 15:42 -0800, John Thurston wrote: >> On 7/1/2013 2:55 PM, Charles Lepple wrote: >>> On Jul 1, 2013, at 12:47 PM, John Thurston wrote: >>> >>>> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the

On 7/1/2013 2:55 PM, Charles Lepple wrote: > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. >> >> Can anyone share a how-to for solaris? > > Here's some general NUT-on-Solaris

It appears that, without munging the startup scripts, it isn't possible to create a slave-only configuration. The scenario is this: My NUT server doesn't need to turn off, it isn't allowed to turn the UPS off, and it isn't authoritative to turn any other server off. Its only job is to make UPS status available to NUT clients. My NUT clients are independent of the NUT server.

I bought a very nice little, self contained, UPS from mini-box: http://www.mini-box.com/OpenUPS2 thinking it would be handled by NUT. I think I misread or misinterpreted the HCL http://www.networkupstools.org/stable-hcl.html The OpenUPS UPS is listed as supported under usbhid-ups, and I had assumed that OpenUPS2 would be as well. Bzzzzt. I get a unknown device ID for d005 Is adding (or

On Mon, 2013-07-01 at 15:42 -0800, John Thurston wrote: > On 7/1/2013 2:55 PM, Charles Lepple wrote: > > On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > > > >> I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. > >> > >> Can anyone

On Jul 1, 2013, at 12:47 PM, John Thurston wrote: > I'm running Solaris 10 on a dozen SPARC boxes. I'd like to explore NUT for use with our snmp UPS, but I'm unable to complete the configure/make/install process. > > Can anyone share a how-to for solaris? Here's some general NUT-on-Solaris information: http://people.cs.clemson.edu/~gdowdin/work/ch06.html Can't

On Sep 8, 2014, at 5:46 PM, John Thurston <john.thurston at alaska.gov> wrote: > I bought a very nice little, self contained, UPS from mini-box: > http://www.mini-box.com/OpenUPS2 > thinking it would be handled by NUT. > I think I misread or misinterpreted the HCL > http://www.networkupstools.org/stable-hcl.html Correct, we only knew about the original openUPS (USB ID

On Aug 28, 2013, at 8:03 PM, John Thurston wrote: > It appears that, without munging the startup scripts, it isn't possible to create a slave-only configuration. > > The scenario is this: > My NUT server doesn't need to turn off, it isn't allowed to turn the UPS off, and it isn't authoritative to turn any other server off. Its only job is to make UPS status available

Scenario: * Two windows 2003 servers (different models) * Each server has two PSUs * Each server has a single serial port * Two UPSs are available of the exact same type (XPower Tigra 1kVA). Each has a serial port * The 1st PSU of each server is powered by the 1st UPS * The 2nd PSU of each server is powered by the 2nd UPS I am trying to install NUT on the best "optimal" way for these

Hi, I hope some one can help. I need to compute Thurston's case 5 on a large set of data. I have gotten as far as computing the proportional preference matrix but the next math is beyond me. Here us my matrix 0.500 0.472 0.486 0.587 0.366 0.483 0.496 0.434 0.528 0.500 0.708 0.578 0.633 0.554 0.395 0.620 0.514 0.292 0.500 0.370 0.557 0.580 0.615 0.329 0.413 0.422 0.630 0.500 0.783 0.641 0.731

tags 441342 upstream thanks Hi Robert, thanks for your report and investigation. We will check to fix this and give you news back. 2007/9/9, Robert Woodcock <rcw at debian.org>: > Package: nut > Version: 2.2.0-2 > Severity: important > > I recently set up nut at work to monitor the 15 APC Smart-UPS 1500s we have > in our server room. Since we currently only have one

Hi Guys, I'd like to submit a patch to enable NUT to communicate with APC 5G UPSs. The current usbhid-ups driver recognises APC UPSs by the Vendor ID and Product ID of 0x051D and 0x0002. This needs to be amended with the new Product ID of 0x0003. (See attached file: apc-hid.patch) Secondly, when Nut polls the UPS via the interrupt channel, these will time out, resulting in frequent lost

This was the secret sauce! I first modified my BASH script to stuff the output of the 'set' command into a variable, then passed that variable in to my email command. Then I triggered an event and saw what variables were there in the body of the message. Voila! $UPSNAME and $NOTIFYTYPE were there and available. I modified the script to pump THOSE into the mail command, and the problem

On October 31, 2017 4:09:46 PM GMT+01:00, Garrett Michael Hayes <Garrett at VerbalImaging.com> wrote: >Greetings Gentlebeings, > >I have started deploying a number of NUT instances on Raspberry Pi >machines (Raspbian Jessie) across my network. The purpose of these >"nutcases" as we refer to them is to monitor the status of the UPSs >supporting our network

There's supposedly another way with a custom upsmon.conf: NOTIFYMSG type message upsmon comes with a set of stock messages for various events. You can change them if you like. NOTIFYMSG ONLINE "UPS %s is getting line power" NOTIFYMSG ONBATT "Someone pulled the plug on %s" Note that %s is replaced with the identifier of the UPS in question. The message must be one

I'm running a single "nut-server" that monitors seven ups units. In upsmon.conf: MONITOR ups-1 0 <User> <Pw> master MONITOR ups-2 0 <User> <Pw> master MONITOR ups-3 0 <User> <Pw> master MONITOR ups-4 0 <User> <Pw> master MONITOR ups-5 1 <User> <Pw> master MONITOR ups-6 1 <User> <Pw> master MONITOR

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

I'm obviously biased but I like Tripp Lite stuff. I try to pitch in and help with Network UPS Tools issues related to Tripp Lite when I can too (albeit the developers and users on this list are usually more helpful than me). Just to confirm, it sounds like you are looking at the SU5000RT4UHV, correct?