similar to: Multipathed monitoring of an UPS

This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;) Also, are those oids apc-private or commonly used/standard among snmp upses? Thanks, //Jim Typos courtesy of my Samsung Mobile -------- ???????? ????????? -------- ??: Charles Lepple <clepple at gmail.com> ????: 2014.02.25 13:08 (GMT+01:00) ????:

My personal experience with a number of UPSes that are monitored via USB cable is that communications errors such as the ones referenced in the issue you linked to below are a result of USB hardware incompatibilities between the USB chipset and the USB port on the motherboard.*? This is NOT specific to the NUT project as it affects both apcupsd and in fact, has been reported as an issue with

On 2014-02-27 14:21, Charles Lepple wrote: > On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru <mailto:jimklimov at cos.ru> > wrote: > >> This apparently implies that, unlike some docs say, the snmp-ups >> driver can send the shutdown signals (is not crippled by design)? ;) > > We're working on it: > >

We only have a few open items that I think should be resolved before releasing 2.7.3. The list grew a bit in the past week, but we'll cover that later. Here is the list: * #93: Devices Dumps Library improvements <https://github.com/networkupstools/nut/issues/93> * #158: Powerware BCMXCP advanced features <https://github.com/networkupstools/nut/pull/158> * #185: insecure storage

On Feb 27, 2014, at 7:07 AM, jimklimov at cos.ru wrote: > This apparently implies that, unlike some docs say, the snmp-ups driver can send the shutdown signals (is not crippled by design)? ;) We're working on it: http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/docs/man/snmp-ups.html#_shutdown A quick check says that the implementation has been there since v2.6.4, and

Hi One idea I&#39;ve had for some time, but unfortunately not had time to implement, is to add a general SNMP agent, which will work with all UPSes supported by nut. The idea is to have the SNMP agent use the "nut API" to fetch values from the UPS. So the SNMP agent will be similar to the "upsc" utility. Whenever the SNMP agent is queried for information, it will use the

Hi, I've submitted a patch to the Alioth tracker but thought to give a heads up here as well, I have an issue with nut not working when the clock is moved backwards. I provided a patch[1] to use clock_gettime with CLOCK_MONOTONIC to fix this, based on comments from Charles Lepple I made a few changes and it can be seen in a git branch I created at [2]. Let me know what you think. Baruch

2014-02-16 8:31 GMT+01:00 <alf at i100.no>: > Hi > Hi Alf, > One idea I've had for some time, but unfortunately not had time to > implement, is to add a general SNMP agent, which will work with all UPSes > supported by nut. > The idea is to have the SNMP agent use the "nut API" to fetch values from > the UPS. > So the SNMP agent will be similar to

On 2014-02-19 03:04, Tim Rice wrote: > If you've got a AP9630 card these notes may be useful. > > # APC ap9630 notes: > # Use firmware 6.0.6 or later if you want SNMPv3 > # Configuration->Shutdown > # In "Start of Shutdown" section, set "Low Battery Duration" and > # "Shutdown Delay" to get enough grace time for the ESXI shutdown > #

Hello all, I am trying to set up my brother's UPS (remotely over internet) on an OpenIndiana-based storage box. According to him, the UPS is probably an Ippon Back Power Pro 600 dated around 2003 (battery recently replaced), and it has an USB connection. Sorry for a relatively long post with a log of my successes and failures, in the hopes that someone would point out what I did wrong.

Hello, I am trying to get my synology DS 418play to connect to my new INTERNET600U UPS, but it appears not to work. I contacted TrippLite and they said the unit is using a new comm protocol 3024. Is there a way to make this work with usbhid-ups? More details of my story here: https://community.synology.com/enu/forum/1/post/132984 Thanks for your help! -Troy

Hi, There is one issue that I would consider as a major issue and not fixed yet. It is the use of wall time for scheduling ups polls instead of a monotonic clock source. I provided a (partial) patch in the past and I believe there was some work on it. The bug manifests itself as a stop of monitoring with no alarm when the clock is moved backwards in time. Please consider adding this to the

> Previously, the manufacturer tested this UPS on version 2.6.5-6 NUT for Windows. Thanks for this important detail. For immediate re-testing, I would recommend to use either NUT v2.8.0 already packaged by some distributions in their testing/bleeding-edge repositories (unfortunately, during the almost year since release many distros - especially for LTS versions - did not change recipes to

Makes sense, and a PR is a way to solicit feedback :) I'd document this for ups.conf (man page and examples), including a note that for devices which do provide a healthy LB these values may be set to 0 safely. Wondering if non-zero defaults should be there anyway. @Community, WDYT? Also, this critical-state check should be done only when the UPS is on battery (and perhaps not calibrating),

I also operate an HP T1500 G3 which it's an Eaton made UPS. Connected on usb i get frequent communication errors and data aquisition stopped. Mine has a serial connection, also. Operating via serial has no trouble. Maybe it's something related to usb setting in bios, i.e. Legacy mode, speed setting, etc. However on serial mode looks like the eaton or hoe power protector software does not

On 10/31/2017 01:13 AM, Jim Klimov wrote: > If the new data is in a separate OID tree, it can quite be a new MIB. Otherwise you can use the UNIQUE flag and set the preferred (e.g. newer, more precise) source for a value first in the list of same-named mappings in existing file - if there's a hit on an actual device, it will be used and not iterated onwards. The flag is not yet supported for

Great, thanks! Also just for context, this sounded reminiscent of one of the first NUT drivers, `genericups` (for simple contact-closure support, with IIRC serial-port connections rather than GPIO). Nearby there's also a `generic_modbus" name. Wondering if the new driver should be (similar to) `generic_gpio`. @Community verdict: Then there was also an effort some years ago to name

?Hello everybody, I'm working on the "Use difftime for time comparison" bug (#313634). Charles directed me to the other one "Use monotonic clock for monitoring" attended to by Baruch; I believe that's very good idea, however I'd use a bit more encapsulated & general approach: 1/ I'd create an opaque timer type and its get/set/cmp/inc/dec etc interface

Hi, Every guide I'm finding is connecting their NUT server to the UPS directly. Is there no option to monitor a network-attached UPS? On its IP or hostname? This was my first assumption when looking at a product called 'Network UPS Tools', but it seems I'm misunderstanding? Thanks for any advice you can give me. Regards, Nichole -------------- next part -------------- An HTML

Hi, We have 2 UPS Chloride 80 NET 120 ( a black and white one ) in our datacenter. Could you please tell me if it is possible to use upsmon or other free solution with these two UPS for shuting down servers during electrical lost power before battery crash . Beet regards, Roger -------------- next part -------------- An HTML attachment was scrubbed... URL: