Re: [Nut-upsuser] Support for APC Smart-UPS X 3000
Just my experiences speaking, look at another brand. I use MGE/Eaton and have had much better life and the quality has been much better. APC does not release the protocol for comunicating with the UPS and so to get NUT to work you have to sniff the traffic and then figure out what the commands and responses mean.(thus reverse engineered) APC also will change the protocol between models. (Thus why that model is not listed, it may work, it may not) I have had four APC brand UPS units melt the batteries. We bought 13 identical units in one order. One blew up on power up. One had loose connections giving a false ground issue. Four did not have all the holes tapped out for mounting. And 6 were rusty. Those were the last APC units we bought. Eaton Evolution line is the old MGE brand and we have had great service from them as well as working with NUT. Just my $0.02 worth. And for the record I do not work for Eaton or have any affiliation with NUT other than a long time user. Doug On Sep 17, 2013 5:09 PM, "Paul O'Rorke" wrote: > Hi all, > > I am completely new to NUT and setting up a UPS shut down in Linux. I am > looking at buying a APC Smart-UPS X 3000. When I look this device up in > the compatibility list this specific model is not listed, only a generic > entry for "Smart-UPS". It says to use the *apcsmart* driver. The legend > shows this as "protocol based on reverse engineering". What does this mean > in terms of using the driver? Can I expect to get this working to shut > down my Debian servers gracefully or is it a bad idea to use a UPS with > only this driver? > > Have users on this list experience with a similar Smart-UPS? Is it going > to be compatible with NUT or should I be looking for a different UPS that > is supported with one of the other drivers? > > Sincerely > -- > > *Paul O’Rorke* > Tracker Software Products > p...@tracker-software.com > > > PLEASE NOTE : - If you are sending files for us to look at or assist with > these must ALWAYS be wrapped in either a ZIP/RAR or 7z FILE > or they will be removed by our Firewall/Virus management software. > > > **Certified by Microsoft** > "Works with Vista" > PDF-XChange & SDK, Image-XChange > PDF-Tools & SDK, TIFF-XChange & SDK. > > Support: > http://tracker-software.com/support/ > or > http://www.tracker-software.com/forum/index.php > > Download latest Releases > http://www.tracker-software.com/downloads/ > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp-Lite OMNI750ISO
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" 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@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Multiple UPS and shutdown sequence.
Daniel, Yes this can be done with some manipulation of the minsupplies setting and the monitor settings. The LDAP servers would monitor themselves as normal and shut down as normal. The NFS server would get a weird config. It would monitor its own UPS as well as the UPS on each LDAP server. Set the monitor command for the NFS to have 3 supplies. (Yeah you are lying to the system). Set the monitor statement on the NFS server for the LDAP servers to have 2 supplies each. Then set your minsupplies to 5. In effect you have told the NFS server it has seven power supplies and it needs 5 to run. If the NFS UPS goes down the number drops to 4 (less than 5) so the system starts to shutdown. If only one of either of the LDAP servers goes down you are still at 5 so NFS stays up. If both go down you are at 3 so less than 5 then shutdown. The NFS can look at the UPS monitored on itself as well as look at the UPS on other boxes at the same time those boxes are monitoring themselves. Check out http://www.networkupstools.org/docs/man/upsmon.conf.html And http://www.networkupstools.org/docs/man/upsmon.html For command details. There are also some timer settings that should allow you to shut down the NFS server before the LDAP servers go down. Doug On Mar 16, 2013 12:25 AM, "Daniel Lopes de Carvalho" wrote: > Hello, > > I would like to know if it is possible to use NUT to monitor more than one > UPS and shutdown the computer only when the battery of the last alive UPS > gets low? > > I have a file server that relies on two other LDAP servers (each with its > UPS) and I would like to shutdown the file server when its UPS battery gets > low or when the battery of the other two UPS (LDAP servers) gets low too. > > Scenario: > > 1 - If UPS01 battery low, shutdown LDAP1 and keep LDAP2 and NFS alive. > 2 - If UPS02 battery low, shutdown LDAP2 and keep LDAP1 and NFS alive. > 3 - If UPS03 battery low, shutdown NFS. > 4 - If UPS01 (and LDAP1) down and UPS02 battery low, shutdown NFS and > LDAP2 (in this sequence). > 5 - If UPS02 (and LDAP2) down and UPS01 battery low, shutdown NFS and > LDAP1 (in this sequence). > > Thanks and best regards. > > Daniel > > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT on Windows Clients
Although I am not on the latest version, actually it has been two years since I upgraded, I have several Windows clients running against a Linux master that monitors multiple UPS units. On Feb 28, 2013 4:12 AM, "Ilia Shapira" wrote: > I want to try to use NUT on Linux server, but most of the servers I need > to shutdown are Windows. > > Before I try to install I wanted to ask you how stable is the Windows Beta > of NUT ? > > I need only the client part of the Windows port, only to shut down the > Windows servers > > ** ** > > ** ** > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] OT: gadget to display time remaining
Primary goals: >UPS(s) and Server(s) automatically talk together with no need for > configuration using just 1 cable, the power cable, without the need for new > special power cables > Don't forget not all UPS have computers connected to them but still need to be monitored for state and condition. Doug ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] SMS PowerVision PV2200 BIFX
> Does your system have the drivers loaded for the converter? If your system >> can see the USB device AND the serial port then NUT needs a serial driver. >> > > Most likely, this works fine. Otherwise the megatec driver would be > complaining about not being able to open the port. So most likely, either > the UPS doesn't speak megatec protocol at all, or uses a modified version > that the megatec driver doesn't support. Upgrading to blazer_ser would at > least give us a chance to see what is going on. > > > So just for my understanding, the NUT ups driver doesn't care if the USB to serial converter is built into the ups or an external unit? Thanks, Doug ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite SmartOnline 3U
Greg, The units I use are Lavalink. I have used them on a couple of flavors of CentOS. My Nut server currently has about 60 virtual serial ports that monitor ups units spread across the campus. The only issue I have run into is sometimes a Lavalink unit will hang during a reboot and not come back online. I attribute this to the number of units and the slowness of the disconnect. I never had a problem during testing with only 4 ports. Other than that and the last time I checked I had to ask support to get the latest drivers for the kenel I was running, they work pretty good. Doug On Apr 7, 2010 4:16 PM, "Greg Terkanian" wrote: *From:* Douglas Parsons [mailto:d...@parsonsemail.com] *Sent:* Wednesday, April 07, 2010 12:41 PM *To:* Greg Terkanian *Cc:* nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] Tripp Lite SmartOnline 3U Oops hit the button on my phone. Another advantage to the converter is it can be moved to any brand the supports serial and there i... > > On Apr 7, 2010 10:23 AM, "Greg Terkanian" wrote: > > Citeren Arjen ... Doug, That was the theory I was going for when I implemented the current solution, however I would have preferred a USB/Ethernet device that supported Linux clients. I couldn’t find one. Do you have a recommendation for your serial/Ethernet hardware for Linux clients? Thanks, Greg ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite SmartOnline 3U
Oops hit the button on my phone. Another advantage to the converter is it can be moved to any brand the supports serial and there is a nut driver for. Doug On Apr 7, 2010 1:37 PM, "Douglas Parsons" wrote: Greg, Another option to look at is to use an ethernet to serial converter. Nut works fine with these set up as a virtual serial port on the guest. Your unit appears to have serial support according to the web and for most of the cards I havd priced the converters are cheaper than the SNMP cards. As a plus the converter can be On Apr 7, 2010 10:23 AM, "Greg Terkanian" wrote: Citeren Arjen de Korte >: > Somehow reading the report descriptor fails, eit... > > Arjen, > Actually it does apply. This is an Ubuntu machine on ESXi. To get around the difficu... ___ Nut-upsuser mailing list nut-upsu...@lists.alioth.d... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Tripp Lite SmartOnline 3U
Greg, Another option to look at is to use an ethernet to serial converter. Nut works fine with these set up as a virtual serial port on the guest. Your unit appears to have serial support according to the web and for most of the cards I havd priced the converters are cheaper than the SNMP cards. As a plus the converter can be On Apr 7, 2010 10:23 AM, "Greg Terkanian" wrote: Citeren Arjen de Korte >: > Somehow reading the report descriptor fails, eit... Arjen, Actually it does apply. This is an Ubuntu machine on ESXi. To get around the difficulties with USB passthrough, I'm using USB Redirector software from Incentives Pro. I was happy when I found that I was actually communicating with the device, but was weary that it might not work with NUT. Apparently it won't. Why these units were purchased without SNMP/web cards is beyond me. I guess I'll have to beg and plead for them to be purchased. Thanks for all your help. If you think it might work with the above scenario, please let me know. -Greg ___ Nut-upsuser mailing list nut-upsu...@lists.alioth.d... ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] communications lost/established
One suggestion would to be to determine if the serial port is working and what it is named without Nut involved. Use a terminal program and a loopback or some known device to test and confirm the port. There are several cases in the archives that talk about testing serial ports as well as Google. On Mar 18, 2010 5:19 PM, "ricman" wrote: Scrive Arjen de Korte >: > Citeren ricman : > > > here are a couple of logs: log 1 and 2 are pretty simi... serial-pci card installed and ups connected. since it is the only serial port in use i guess it is ttyS0... anyway i tried ttyS0 and ttyS1 but it doesn't work. connecting or not the cable the result doesn't change Mar 18 22:02:40 maialinux upsd[2895]: listening on 127.0.0.1 port 3493 Mar 18 22:02:40 maialinux upsd[2895]: Can't connect to UPS [myups] (blazer_ser-myups): No such file or directory Mar 18 22:02:40 maialinux upsd[2903]: Startup successful Mar 18 22:02:40 maialinux upsmon[2905]: Startup successful Mar 18 22:02:40 maialinux upsd[2903]: User local_...@127.0.0.1 logged into UPS [myups] Mar 18 22:02:40 maialinux upsmon[2908]: Poll UPS [my...@localhost] failed - Driver not connected Mar 18 22:02:40 maialinux upsmon[2908]: Communications with UPS my...@localhost lost Mar 18 22:02:45 maialinux upsmon[2908]: Poll UPS [my...@localhost] failed - Driver not connected Mar 18 22:02:45 maialinux upsmon[2908]: UPS my...@localhost is unavailable Mar 18 22:02:50 maialinux upsmon[2908]: Poll UPS [my...@localhost] failed - Driver not connected debug level is '3' Trying megatec protocol... send: Q1 read: timeout blazer_status: short reply Status read 1 failed send: Q1 read: timeout blazer_status: short reply Status read 2 failed send: Q1 read: timeout blazer_status: short reply Status read 3 failed Trying mustek protocol... send: QS read: timeout blazer_status: short reply Status read 1 failed send: QS read: timeout blazer_status: short reply Status read 2 failed send: QS read: timeout blazer_status: short reply Status read 3 failed Trying megatec/old protocol... send: D read: timeout blazer_status: short reply Status read 1 failed send: D read: timeout blazer_status: short reply Status read 2 failed send: D read: timeout blazer_status: short reply Status read 3 failed No supported UPS detected Network UPS Tools - Megatec/Q1 protocol serial driver 1.51 (2.4.1) where am i wrong? ___ Nut-upsuser mailing list nut-upsu...@lists.alioth ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Recommended UPS brand (OffTopic sort of)
If these are like the last units they are convertible and will do tower (TWR) or rack (2U). The 5-20 and 6x5-20 are designation for the receptacles and the L5-20 is for a Twist lock plug on the cord which I will replace with a 5-20. This unit has six outlets on the back and one on a cord. 5-20 and L5-20 are NEMA designations for the plug and receptacle designs used in the US and some other countries. On Tue, Feb 17, 2009 at 4:05 AM, Arnaud Quette wrote: > > 2009/2/16 Douglas Parsons > >> Arnaud, >> > > Hi Doug, > > >> The supplier came back with this description and part number. >> >> Eaton Corporation MGE OPS PULSAR 2200VA TWR 5-20 6X5-20 1XL5-20 2U 86722 >> >> So this should be the one. I hope. >> > > indeed, this is this one (with the MGE name ; EX being for Eaton): > > http://tools.mgeops.com/selector/products/index.php?prod_temp=Pulsar%20M&gzone=USA&partnum=86722 > > the last number is the commercial ref ; TWR is for tower (as opposed to > rack) > I'm not sure about the other figures though... > > Arnaud > -- > Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > Debian Developer - > http://people.debian.org/~aquette/<http://people.debian.org/%7Eaquette/> > Free Software Developer - http://arnaud.quette.free.fr/ > > >> On Mon, Feb 16, 2009 at 9:13 AM, Arnaud Quette wrote: >> >>> >>> 2009/2/13 Douglas Parsons >>> >>>> Arnaud, >>>> >>>> Cool. Found the unit. Looks like they renamed it as I had a Pulsar EX >>>> 2200 and it is now the Pulsar M 2200. The EX line only goes to 1500 now. >>>> Sent the link to the reseller. >>>> >>> >>> not that easy again ;-) >>> the various ranges are under renaming between MGE and Powerware, to have >>> something uniform and coherent for Eaton. For example, the previous"Pulsar" >>> / "Pulsar M" are starting to be found as "EX". >>> It then depends on the Marketing and the region. >>> So you will find the one you want as either "Pulsar M 2200" or "EX 2200" >>> >>> cheers, >>> Arnaud >>> -- >>> Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops >>> Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ >>> Debian Developer - >>> http://people.debian.org/~aquette/<http://people.debian.org/%7Eaquette/> >>> Free Software Developer - http://arnaud.quette.free.fr/ >>> >>> >> > > >> >> ___ >> Nut-upsuser mailing list >> Nut-upsuser@lists.alioth.debian.org >> http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser >> > > > > > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Recommended UPS brand (OffTopic sort of)
Arnaud, The supplier came back with this description and part number. Eaton Corporation MGE OPS PULSAR 2200VA TWR 5-20 6X5-20 1XL5-20 2U 86722 So this should be the one. I hope. Doug On Mon, Feb 16, 2009 at 9:13 AM, Arnaud Quette wrote: > > 2009/2/13 Douglas Parsons > >> Arnaud, >> >> Cool. Found the unit. Looks like they renamed it as I had a Pulsar EX 2200 >> and it is now the Pulsar M 2200. The EX line only goes to 1500 now. Sent >> the link to the reseller. >> > > not that easy again ;-) > the various ranges are under renaming between MGE and Powerware, to have > something uniform and coherent for Eaton. For example, the previous"Pulsar" > / "Pulsar M" are starting to be found as "EX". > It then depends on the Marketing and the region. > So you will find the one you want as either "Pulsar M 2200" or "EX 2200" > > cheers, > Arnaud > -- > Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > Debian Developer - > http://people.debian.org/~aquette/<http://people.debian.org/%7Eaquette/> > Free Software Developer - http://arnaud.quette.free.fr/ > > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Recommended UPS brand (OffTopic sort of)
Arnaud, Cool. Found the unit. Looks like they renamed it as I had a Pulsar EX 2200 and it is now the Pulsar M 2200. The EX line only goes to 1500 now. Sent the link to the reseller. Thanks, Doug On Fri, Feb 13, 2009 at 2:52 PM, Arnaud Quette wrote: > > > 2009/2/13 Douglas Parsons > >> Hello, >> > > Hi Doug, > > >> I am looking for a compatible brand for nut. I currently have both APC and >> MGE units in house. I liked the MGE units and had switched to them after >> several bad experiences with the APC line. We ordered 13 APC Rack mount >> units and the quality was horable. One blew up, two did not have the mount >> holes threaded and several had considerable rust on them. With this I swore >> off APC and found MGE. Then what happens? MGE purchases APC. Now I find that >> most of the MGE models that I use are no longer available and so I am in the >> market for a new brand of UPS. >> >> I am looking for a 2200 VA rack mount in a 2U package. 120V in 120V out >> single phase. What I would like is a product that is compatible with NUT and >> supports serial communication. I know that some brand support more commands >> than others. >> >> I am not out to start a flame war on brands just get a list of one that >> users have had good experiences with. >> >> Really hate that MGE drop those models as I really like the quality and >> design. >> > > not that easy! > > This part of MGE has not been droped, but sold to Eaton. > All the good things, including the NUT and more generally FLOSS support has > so gone to Eaton. > Check my sig for the new link, and rejoice: what you like is still alive, > and more than even ;-) > > cheers, > Arnaud > -- > Linux / Unix Expert R&D - Eaton - http://www.eaton.com/mgeops > Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ > Debian Developer - > http://people.debian.org/~aquette/<http://people.debian.org/%7Eaquette/> > Free Software Developer - http://arnaud.quette.free.fr/ > > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Recommended UPS brand (OffTopic sort of)
Hello, I am looking for a compatible brand for nut. I currently have both APC and MGE units in house. I liked the MGE units and had switched to them after several bad experiences with the APC line. We ordered 13 APC Rack mount units and the quality was horable. One blew up, two did not have the mount holes threaded and several had considerable rust on them. With this I swore off APC and found MGE. Then what happens? MGE purchases APC. Now I find that most of the MGE models that I use are no longer available and so I am in the market for a new brand of UPS. I am looking for a 2200 VA rack mount in a 2U package. 120V in 120V out single phase. What I would like is a product that is compatible with NUT and supports serial communication. I know that some brand support more commands than others. I am not out to start a flame war on brands just get a list of one that users have had good experiences with. Really hate that MGE drop those models as I really like the quality and design. Oh well. Thanks, Doug ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] early shutdown of VMware VMs
What version of VMWare are you running? This makes a difference as to your choices. Do you have the VMWare tools installed on the virtual machines? With most versions you can have the host shut down the guest. Some versions give more options than others. As I understood from a previous thread there is no current means to trigger at set battery levels for particular slaves. But you may be able to trigger at a higher battery level so the host will start the guest shutdown and have time to complete before you run out of battery. If I mis speak here please correct me list. I an a novice on nut. Doug On Fri, Feb 13, 2009 at 11:01 AM, Jon Bendtsen wrote: > On 13/02/2009, at 16.48, David Newman wrote: > > > On 2/12/09 11:19 PM, Arjen de Korte wrote: > >> Citeren David Newman : > >> > >>> How to shut down VMWare guest virtual machines earlier than the host > >>> machine they run on? (For example, if everything normally shuts > >>> down at > >>> 5% UPS battery, then the VMs should shut down at 10%.) > >> > >> First question is, why do you want to do that? > > > > Because a clean shutdown of the VMs is more important than high uptime > > for the VMs. > > > > If both guest and host machines shut down at the same time, the host > > might finish its shutdown before the guests have, leading to possible > > filesystem corruption. I will gladly trade off some downtime of the > > VMs > > to ensure clean shutdowns. > > > > > >> > >>> I also read upssched.txt but I can't tell from the early shutdown > >>> section which settings to use on the master and which on the slaves. > >>> > >>> This seems like a fairly standard problem -- are there sample > >>> configs > >>> posted someplace? > >> > >> I'm not an expert on VMware, but I would expect that you can > >> configure > >> on the host that it shuts down the guests before going down. > > > > Thanks -- that's what I'm asking for -- what is it that I configure, > > and > > are there sample configs someplace that do this? > > I think you have to ask on a VMware list how you configure the VMware > server to tell the VMware clients to shut down. Maybe just sending > ctrl+alt+delete is enough. > > Or you could just use the notify command? Once ONBATT is reached, > then sleep for a 1 minute or more, and start the shutdown? > If you get a ONLINE then have the script check if all virtual machines > are running. > > There might be a problem if the UPS has very little power left. So > when you > get a LOWBATT execute a script that doesnt sleep but start the shutdown > now. > > NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC > NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC > NOTIFYFLAG ONLINE SYSLOG+EXEC > > NOTIFYCMD /sbin/upsmail.sh > > Then just include something that tells the virtual machines to shut > down. > And install it on every vmware client unless you can instruct vmware to > shut the clients nicely down. Maybe tell vmware to sleep the machines > at ONBATT? > > > > JonB > > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] ordered shutdown
Lars, The win client includes several timers that can be used to simulate what you seek. There is a timer that can be set to cause the server to shut down after X minutes on battery. You can set this to the needed times giving you the sequencing you are looking for. The down side is the issue of mid shutdown recovery. On a large UPS system with the windows client you have to cycle power to the server to get it to reboot. Unless you have a way to switch off the output that the server is on, you will have to continue the shutdown of the entire system and then trigger a restart of the UPS unit OR require manual intervention. This is exactly the point I am facing in my system. At this point we are concerned with a clean shutdown and are willing to do a manual restart. I have about 50 ups units on campus and monitor them all with one NUT server. All of the windows clients then talk to that one master server to get the status to it's UPS unit. Mine is still a work in progress and has many things left to fix. Doug On Fri, Jan 30, 2009 at 7:32 AM, Lars Täuber wrote: > Hallo there. > > I'm new to this list and also to NUT. > Our previous ups-system was APC based and apcupsd was serving the ordered > shutdowns in our network. > > Our new ups is made by MGE and that's why we can't use apcupsd anymore. > This led us into trouble. > Our network system is quite complex and we need shutdown sequence levels. > The servers depend on each other because of NFS and SQL connections and the > like. > We have one 60kVA UPS and more than 20 servers/routers/SANs supplied with > energy by it. > > With apcupsd we could confiure the servers to shutdown on a specified > battery level or the remaining time. Is there a way to do this with NUT > anyhow? > I thought about using the schedule mechanism with own bash scripts but this > won't work on windows. In the docs is nothing written about such a feature. > BTW, is there a feature request website for NUT somewhere? > > Thanks > Lars > > ___ > Nut-upsuser mailing list > Nut-upsuser@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser > ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
