Got one of these up and running with the tripplite_usb driver on Ubuntu Server 12.04 x64. This particular model has product code 0x1000. Setup and installation was pretty standard. The only hiccup was I had to create a udev rule to give the nut group access to USB devices. If anyone has any questions let me know. Here's what I am got back from the upsc command: battery.charge: 100 battery.test.status: Battery OK battery.voltage: 14.75 battery.voltage.nominal: 36 device.mfr: Tripp Lite device.model: UPS device.type: ups driver.name: tripplite_usb driver.parameter.pollinterval: 2 driver.parameter.port: /dev/usb/hiddev0 driver.version: 2.6.3 driver.version.internal: 0.20 input.voltage: 106.97 input.voltage.nominal: 120 output.voltage: 114.0 ups.debug.load_banks: 0 ups.debug.V: 31 30 36 30 58 58 0d '1060XX.' ups.delay.shutdown: 64 ups.firmware: F1247.A ups.firmware.aux: protocol 2001 ups.mfr: Tripp Lite ups.model: UPS ups.power.nominal: 750 ups.productid: 0001 ups.status: OL ups.vendorid: 09ae One question I have thought is this: What triggers the drive to send the shutdown command? I am curious because this server draws about 600W and this model of UPS should only last about 10min under that load and I need 3 minutes to shutdown 20 guest VMs. Thanks, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130325/45f19504/attachment.html>
Dave, My NUT skills are rusty so I may need correcting, list feel free to enlighten me. Last I recall there are two main triggers for shutdown, LB (low battery) from the "status" variable or a timer that begins when the "status" varible goes from OL (on line) to OB (on battery). In your case I would think the timer is the way to go. Now with that said I also recall that at least on some UPS units you can adjust the LB point. If yours is one of these you can increase the LB setting and thus give yourself more time before the battery dies. Like I said it has been a while since I have been in the docs so there may be a better method but I am sure there is a solution of some type. Doug On Mar 25, 2013 2:34 AM, "David Vree" <david.h.vree at gmail.com> wrote:> Got one of these up and running with the tripplite_usb driver on Ubuntu > Server 12.04 x64. This particular model has product code 0x1000. > > Setup and installation was pretty standard. The only hiccup was I had to > create a udev rule to give the nut group access to USB devices. > > If anyone has any questions let me know. Here's what I am got back from > the upsc command: > > battery.charge: 100 > battery.test.status: Battery OK > battery.voltage: 14.75 > battery.voltage.nominal: 36 > device.mfr: Tripp Lite > device.model: UPS > device.type: ups > driver.name: tripplite_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.6.3 > driver.version.internal: 0.20 > input.voltage: 106.97 > input.voltage.nominal: 120 > output.voltage: 114.0 > ups.debug.load_banks: 0 > ups.debug.V: 31 30 36 30 58 58 0d '1060XX.' > ups.delay.shutdown: 64 > ups.firmware: F1247.A > ups.firmware.aux: protocol 2001 > ups.mfr: Tripp Lite > ups.model: UPS > ups.power.nominal: 750 > ups.productid: 0001 > ups.status: OL > ups.vendorid: 09ae > > One question I have thought is this: What triggers the drive to send the > shutdown command? > > I am curious because this server draws about 600W and this model of UPS > should only last about 10min under that load and I need 3 minutes to > shutdown 20 guest VMs. > > Thanks, > Dave > > _______________________________________________ > Nut-upsuser mailing list > Nut-upsuser at lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20130325/15529849/attachment.html>
On Mar 25, 2013, at 2:34 AM, David Vree wrote:> Got one of these up and running with the tripplite_usb driver on Ubuntu Server 12.04 x64. This particular model has product code 0x1000.I haven't run across a product code on these units before (just the USB VID, PID, and a Tripp-Lite specific protocol, which appears to be 2001 in your case).> Setup and installation was pretty standard. The only hiccup was I had to create a udev rule to give the nut group access to USB devices.Did you install via the official .debs, or source? The Ubuntu .debs should set everything up with udev - if not, please file a bug: https://launchpad.net/ubuntu/+source/nut> If anyone has any questions let me know. Here's what I am got back from the upsc command: > > battery.charge: 100 > battery.test.status: Battery OK > battery.voltage: 14.75 > battery.voltage.nominal: 36 > device.mfr: Tripp Lite > device.model: UPS > device.type: ups > driver.name: tripplite_usb > driver.parameter.pollinterval: 2 > driver.parameter.port: /dev/usb/hiddev0 > driver.version: 2.6.3 > driver.version.internal: 0.20 > input.voltage: 106.97 > input.voltage.nominal: 120 > output.voltage: 114.0 > ups.debug.load_banks: 0 > ups.debug.V: 31 30 36 30 58 58 0d '1060XX.' > ups.delay.shutdown: 64 > ups.firmware: F1247.A > ups.firmware.aux: protocol 2001 > ups.mfr: Tripp Lite > ups.model: UPS > ups.power.nominal: 750 > ups.productid: 0001 > ups.status: OL > ups.vendorid: 09ae > > One question I have thought is this: What triggers the drive to send the shutdown command?As Doug mentioned, by default NUT shuts down when the UPS signals LB (low battery). If there is no "upsrw" variable available to adjust, it means one of two things: the UPS can't adjust this limit, or we don't know how to adjust it. [update: I see that this is not listed in the upsrw output. bummer.] It is worth pointing out that the serial and non-PDC Tripp-Lite UPSes are all based on reverse-engineered protocols. Only the Tripp-Lite models supported by usbhid-ups are based on an open standard protocol (HID Power Device Class), and even then, some experimentation was needed. -- Charles Lepple clepple at gmail
On 03/25/2013 09:36 AM, Charles Lepple wrote:> On Mar 25, 2013, at 9:20 AM, David Vree wrote: > >> [ups.delay.shutdown] >> Interval to wait after shutdown with delay command (seconds) >> Type: STRING >> Value: 64 >> >> There is nothing apparently settable about its LB point via the driver. BTW -- What do you think "ups.delay.shutdown" means? > ups.delay.shutdown is the number of seconds between when the driver (in response to LB) sends the UPS the shutdown command, and when the UPS should actually pull power.You mean pull power to the server? Then I should definitely increase that from 64 to 180 seconds as it takes some minutes to shut to 20+ VMs.> The alternative, if you are not as concerned about maximizing runtime, is to start a timer with upssched when the UPS first loses power, and cancel the timer if the power returns before the LB threshold is hit. I would advocate the belt-and-suspenders approach of doing both, just in case your battery starts to weaken, and you hit the LB threshold before the timer expires. The upssched approach has the disadvantage of being time-based rather than percentage-based, but it should get the job done.I will look into this approach as well. Thanks for the pointer.