Stan Gammons
2014-Jun-23 02:32 UTC
[Nut-upsuser] Multiple servers connected to the same UPS
Can one have a single UPS powering multiple servers and have them all shutdown in an orderly fashion pending a power loss? It seems as though this is possible from what I gathered from the docs, but I've yet to make this work on an OpenBSD and FreeNAS machine that are powered from the same UPS. The master server that the UPS is connected to via USB receives messages from the UPS, but the slave doesn't receive any messages. Any tips on how to make this work? Stan
Philippe Andersson
2014-Jun-23 09:20 UTC
[Nut-upsuser] Multiple servers connected to the same UPS
On 23/06/14 04:32, Stan Gammons wrote:> Can one have a single UPS powering multiple servers and have them all > shutdown in an orderly fashion pending a power loss? It seems as > though this is possible from what I gathered from the docs, but I've yet > to make this work on an OpenBSD and FreeNAS machine that are powered > from the same UPS. The master server that the UPS is connected to via > USB receives messages from the UPS, but the slave doesn't receive any > messages. Any tips on how to make this work?Yes, it is indeed possible. Here is a brief description of my typical configuration: - install NUT on all the participating servers - the machine that is physically connected to the UPS (serial or USB) becomes the "NUT server", all others are "NUT clients". - the NUT server has the entire NUT stack (driver, upsd, upsmon, upssched) - NUT clients only use upsmon, and "MONITOR" the UPS published by the NUT server - on the NUT server, use "upssched" to initiate a countdown timer on "ONBATT" events - if the countdown timer expires before the power returns, a custom script is called that issues a "FSD" (forced shutdown) -- this message is sent to all participating servers - on each participating server, configure the shutdown command (upsmon.conf) with a suitable grace period to take into account the dependencies between servers (if any). If you need more information, please mail me directly -- I can share the configuration files and scripts I use. HTH Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan at iba-group.com <http://www.iba-worldwide.com> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 263 bytes Desc: OpenPGP digital signature URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20140623/155d9408/attachment.sig>
Greg Vickers
2014-Jun-24 10:46 UTC
[Nut-upsuser] Multiple servers connected to the same UPS
Hi Philippe, On 23/06/2014 7:20 pm, Philippe Andersson wrote:> On 23/06/14 04:32, Stan Gammons wrote: >> Can one have a single UPS powering multiple servers and have them all >> shutdown in an orderly fashion pending a power loss? It seems as >> though this is possible from what I gathered from the docs, but I've yet >> to make this work on an OpenBSD and FreeNAS machine that are powered >> from the same UPS. The master server that the UPS is connected to via >> USB receives messages from the UPS, but the slave doesn't receive any >> messages. Any tips on how to make this work? > Yes, it is indeed possible. Here is a brief description of my typical > configuration:Excellent, thank you very much for sharing this information, this is exactly what I wish to do with my NUT installation :)> - install NUT on all the participating servers > > - the machine that is physically connected to the UPS (serial or USB) > becomes the "NUT server", all others are "NUT clients". > > - the NUT server has the entire NUT stack (driver, upsd, upsmon, upssched) > > - NUT clients only use upsmon, and "MONITOR" the UPS published by the > NUT server > > - on the NUT server, use "upssched" to initiate a countdown timer on > "ONBATT" events > > - if the countdown timer expires before the power returns, a custom > script is called that issues a "FSD" (forced shutdown) -- this message > is sent to all participating servers > > - on each participating server, configure the shutdown command > (upsmon.conf) with a suitable grace period to take into account the > dependencies between servers (if any). > > If you need more information, please mail me directly -- I can share the > configuration files and scripts I use.Can I get a copy of your configuration files too please? I've got a laptop with low power requirements hooked up as my nut server, so I'm actually going to configure nut to not shutdown the laptop, I want it to keep on running even after the UPS has run out of battery, and the power management on the laptop will shut down the laptop. I'd even like to do a wake-on-LAN to the server, once the UPS has gotten back to, say, 50% battery. Cheers, Greg> > HTH > > Cheers. Bye. > > Ph. A. > > > > _______________________________________________ > 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/20140624/04172102/attachment.html>
Apparently Analagous Threads
- Multiple servers connected to the same UPS
- upssched timer configuration with redundant UPSes ?
- snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
- snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]
- snmp-ups sends status "OL OB" on HP R3000 UPS with AF465A management card [UPDATE]