similar to: NUT upgrade to 2.6.0 in Gentoo with Liebert UPS

Displaying 20 results from an estimated 2000 matches similar to: "NUT upgrade to 2.6.0 in Gentoo with Liebert UPS"

2011 May 30
2
UPS Liebert GXT3 config
Hi all, I?ve a UPS Liebert GXT3 500-3000VA with USB port. I?ve install NUT version 2.2.2 from repository packages for Debian Lenny. Linux kernel 2.6.26 I?ve try to use usbhid-ups driver in ups.conf [liebert] driver=usbhid-ups port=/dev/usb/hiddev0 Debian get the usb: # lsusb -v Bus 001 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive UPS Device Descriptor: bLength
2017 Jun 03
0
Fwd: Emerson Liebert GXT4
On Jun 2, 2017, at 8:28 AM, zefanjas <nut at zefanjas.de> wrote: > I couldn't get the GXT4 working with usbhid-ups driver. So I need some > advise to continue to get this device working. The GXT3 seems to be > working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). > > Here is my ups.conf > > [ups] > driver = usbhid-ups > port =
2009 Nov 10
1
[PATCH] Add support for Liebert PowerSure PSA to liebert-hid.c
This patch adds support for the following ups to liebert-hid.c: $ lsusb | grep Liebert Bus 007 Device 005: ID 10af:0001 Liebert Corp. PowerSure PSA UPS Using this patch, I'm able to obtain information about the ups via upsc: $ upsc upsname battery.charge: 100 battery.runtime: 1012 battery.type: PbAc battery.voltage: 1172 battery.voltage.nominal: 12 driver.name: usbhid-ups
2023 Apr 08
1
Vertiv Liebert
Hello, I was able to get the Vertiv/Liebert UPS (Vertiv Liebert PSA5 1500VA 900W - PSA5-1500MT120) to start working with NUT and "usbhid" driver, but would appreciate help to get it to work properly. Here's the output from the "upsc" command for a Cyberpower UPS I have: battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS
2017 Jun 02
2
Fwd: Emerson Liebert GXT4
Hello, we have a Emerson Liebert GXT4, that we like to connect to our servers to shut them down if there is a power failure (which happens quite often in our area). I couldn't get the GXT4 working with usbhid-ups driver. So I need some advise to continue to get this device working. The GXT3 seems to be working ok with NUT (http://networkupstools.org/ddl/Liebert/GXT3.html). Here is my
2010 Apr 23
1
Liebert powersure psp
Hi, I have a Liebert POWERSURE PSP connected via USB. Cleanly built and installed from source nut-2.4.3.tar.gz using kernel 2.6.30.5 #cat /proc/bus/usb T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=10af ProdID=0003 Rev= 0.00 S: Manufacturer=Liebert S: Product=Liebert PSP 350 FW: 02 S:
2013 Aug 20
0
Liebert GXT3 ID 10af:0000 Not working
[please keep the list CC'd.] On Aug 20, 2013, at 12:50 AM, Korviakov Andrey wrote: > Yes, it's my mistake: UPS used USB cable for communication, but i think that it's simple usb-com cable because nut work with liebert driver on ttyS0 port. If that is the case, I doubt that usbhid-ups will be able to retrieve any additional information. > In ups.conf i tried: > >
2023 Apr 09
1
Vertiv Liebert
Bruce Pleat via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> writes: > Here's the (far less lengthy) output for the Vertiv Liebert: > > device.mfr: Vertiv Co > device.model: Liebert PSA5 > device.serial: 22223106602D04C > device.type: ups > driver.name: usbhid-ups > driver.parameter.pollfreq: 30 > driver.parameter.pollinterval: 2 >
2005 Aug 30
0
Liebert PowerSure PSA 500
[FAQ on USB-connected UPSes] > Remember: this is brand new *experimental* software and is probably > very broken. Do us a favor and report successes or failures to > the mailing lists. No problem ... : UPS: Liebert PowerSure PSA 500 NUT: Version 2.0.2 Kernel: 2.6.11.5, with CONFIG_USB_HID, CONFIG_USB_HIDINPUT, and CONFIG_USB_HIDDEV compiled in (statically)
2013 Aug 20
0
Liebert GXT3 ID 10af:0000 Not working
On Aug 19, 2013, at 12:58 PM, Korviakov Andrey wrote: > I have Liebert GXT3 UPS connected to CentOS Linux with kernel 2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2. > lsusb: Bus 002 Device 003: ID 10af:0000 Liebert Corp. UPS > > And this UPS detected only with this section in ups.conf: > > [liebert] > driver = liebert > port = /dev/ttyS0 I am confused.
2014 Nov 06
2
Emerson/Liebert GXT3
2014-10-30 0:49 GMT-03:00 Charles Lepple <clepple at gmail.com>: > On Oct 29, 2014, at 5:08 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > >> Hi, >> >> I've bought a Liebert GXT3 UPS and I'm trying to use it with nut. I'm >> using Ubuntu 14.04, but I'm having troubles (similar to this thread >> [1]) using the
2013 Aug 19
3
Liebert GXT3 ID 10af:0000 Not working
Hello. I have Liebert GXT3 UPS connected to CentOS Linux with kernel 2.6.32-131.0.15.el6.x86_64 and nut version 2.6.5-2. lsusb: Bus 002 Device 003: ID 10af:0000 Liebert Corp. UPS And this UPS detected only with this section in ups.conf: [liebert] driver = liebert port = /dev/ttyS0 but only this variables available: device.mfr: Liebert device.model: MultiLink device.type: ups
2017 Jun 05
2
Fwd: Emerson Liebert GXT4
Hi, thanks for your helpful reply. I've added the productid in the ups.conf and it seems to work (better) now. > After starting the driver and upsd, what does "upsc ups" return? If you can also include "upsrw ups" and "upscmd -l ups" output, we can update the DDL. #upsc ups Init SSL without certificate database battery.charge: 100 battery.charge.low: 20
2023 Jul 18
0
Liebert PSA 1500 (500, 1000, 650, ...)
Hello The page https://networkupstools.org/ddl/Liebert/PSA_1500.html don't contain all information about UPS series PSA. First, the variable "*device.serial*" is dummy, it is always empty , and "*ups.serial*" also always empty. Second, configuration file for the all UPS "PSA" contain these lines: [PSA] ??? driver = "usbhid-ups" ?? ?port =
2011 Feb 03
3
Status OB (on battery) when polling a Liebert PSA
Hi all, This is my first experience with NUT. I'm trying to test a Liebert PSA 1500 UPS, connected via USB to a single PC. I have followed the instruction in the "Configuration" section of the online user manual. Everything seems to be fine, except that, when I run "upsc liebert at localhostups.status", it retuns "OB", even if the UPS is currently online. Here
2014 Oct 01
3
Return on experience with an Emerson/Liebert GXT3
Hi. I would like to share with you my experience on trying to use nut with a Liebert GXT3 on a Debian wheezy with nut-server 2.6.4. Please find my observations below. (1) I've installed the packaged version of nut-server # aptitude install nut-server (2) I did some tuning for my configuration #??cat << EOF >> /etc/nut/ups.conf user=nut [liebert] ??????? driver=usbhid-ups
2013 Feb 19
1
UPS Liebert GXT-3
Hello, I (now) own an Emerson Liebert GXT3 6000VA conected via USB. I've searched the web trying to configure nut (nut-2.6.5-1.el6.x86_64 epel rpm on CentOS 6.3) to monitor the UPS, but couldn't find a successful configuration. I'm running kernel 2.6.32-279.14.1.el6.x86_64. The UPS is connected with an USB cable: Bus 004 Device 002: ID 10af:0008 Liebert Corp. PowerSure Interactive
2014 Nov 09
2
Emerson/Liebert GXT3
2014-11-08 20:46 GMT-03:00 Charles Lepple <clepple at gmail.com>: > On Nov 7, 2014, at 7:30 AM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: > >> 2014-11-07 0:16 GMT-03:00 Charles Lepple <clepple at gmail.com>: >>> On Nov 6, 2014, at 5:56 PM, Marcelo Fernandez <marcelo.fidel.fernandez at gmail.com> wrote: >>> >>>>
2023 Dec 04
1
Liebert UPS driver
Replaced ups with a new Liebert UPS and it seems the device may not be known to nut. Below is output of lsusb: ID 10af:0002 Liebert Corp. PowerSure PST UPS Sent from Outlook<http://aka.ms/weboutlook> -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20231204/7c08a727/attachment.htm>
2017 Apr 17
1
New UPS information - Liebert GXT4 via US
Hi UPS List members, I have purchased a number of Emerson Power / Liebert GXT4 UPS units. I have these working correctly under nut, but limited detsils are being reported. I am happy to supply information on the USB communications to improve the reported details I can use WireShark to capture the comms between the supplied Windows GUI tool and the UPS Please advise the best way I can