Hi List. I have an old Compaq 3000 (Eaton 5119). It is running servers, disk-arrays, one workstation etc. I am planning to install NUT (master) on a headless CENTOS 6.8 system. Connect the UPS with seral cable. Now my main question is, Does NUT support the power segments on the UPS. My intention is to be able to take down the system in an ordered way before the batteries are exhausted. I.e 5 mins after Power Loss take shut down the servers on segment 3. When they are down, shut down power for segment 3 Then repeat for segment 2 And finally process servers on segment 1 Servers are a mix of Centos, W2k8R2 and ESXi5.5 with W2k8(R2). Workstationisi W10Pro NAS is Synology Rackstation RS816 With best regards Tomas Larsson Sweden -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/bd6e641f/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: Tomas Larsson.vcf Type: text/x-vcard Size: 4555 bytes Desc: Tomas Larsson.vcf URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/bd6e641f/attachment.vcf>
On Jul 22, 2017, at 4:13 AM, Tomas Larsson <tomas.larsson at enrad.se> wrote:> > I am planning to install NUT (master) on a headless CENTOS 6.8 system. > Connect the UPS with seral cable.It looks like this might be using the upscode2 driver (UPScode-II protocol), right?> Now my main question is, Does NUT support the power segments on the UPS. > My intention is to be able to take down the system in an ordered way before the batteries are exhausted.The upscode2 driver does not seem to support the segments, although this is a limitation of that driver rather than the rest of NUT. I have not looked into the protocol document too much, but it should be possible to add this. (It would probably be best if we could find someone with a spare UPS who is willing to test, though - you might not want to do this in production.)> I.e > 5 mins after Power Loss take shut down the servers on segment 3. > When they are down, shut down power for segment 3 > Then repeat for segment 2 > And finally process servers on segment 1I do not use upsched (which is generally necessary for shutting down after a specified time on battery, rather than when the UPS determines that the battery is low), but it should be possible to do this even without controlling the segments. Perhaps someone else with more recent experience can comment on this.> Servers are a mix of Centos, W2k8R2 and ESXi5.5 with W2k8(R2). > Workstationisi W10Pro > NAS is Synology Rackstation RS816I also have not used a Synology device, but as I recall, they generally expect to be the NUT master system. This may cause problems if you need to do something fancy with upssched.
Ok, If I'll get an SNMP-card, would I have better control over the ups. With best regards Tomas Larsson -----Ursprungligt meddelande----- Fr?n: Charles Lepple [mailto:clepple at gmail.com] Skickat: den 22 juli 2017 14:49 Till: Tomas Larsson Kopia: nut-upsuser at lists.alioth.debian.org ?mne: Re: [Nut-upsuser] Compaq R3000h support On Jul 22, 2017, at 4:13 AM, Tomas Larsson <tomas.larsson at enrad.se> wrote:> > I am planning to install NUT (master) on a headless CENTOS 6.8 system. > Connect the UPS with seral cable.It looks like this might be using the upscode2 driver (UPScode-II protocol), right?> Now my main question is, Does NUT support the power segments on the UPS. > My intention is to be able to take down the system in an ordered way before the batteries are exhausted.The upscode2 driver does not seem to support the segments, although this is a limitation of that driver rather than the rest of NUT. I have not looked into the protocol document too much, but it should be possible to add this. (It would probably be best if we could find someone with a spare UPS who is willing to test, though - you might not want to do this in production.)> I.e > 5 mins after Power Loss take shut down the servers on segment 3. > When they are down, shut down power for segment 3 Then repeat for > segment 2 And finally process servers on segment 1I do not use upsched (which is generally necessary for shutting down after a specified time on battery, rather than when the UPS determines that the battery is low), but it should be possible to do this even without controlling the segments. Perhaps someone else with more recent experience can comment on this.> Servers are a mix of Centos, W2k8R2 and ESXi5.5 with W2k8(R2). > Workstationisi W10Pro > NAS is Synology Rackstation RS816I also have not used a Synology device, but as I recall, they generally expect to be the NUT master system. This may cause problems if you need to do something fancy with upssched. -------------- next part -------------- A non-text attachment was scrubbed... Name: Tomas Larsson.vcf Type: text/x-vcard Size: 4555 bytes Desc: Tomas Larsson.vcf URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/745bfb29/attachment.vcf>
On Sat, Jul 22, 2017 at 7:48 AM, Charles Lepple <clepple at gmail.com> wrote:> > I also have not used a Synology device, but as I recall, they generally > expect to be the NUT master system. This may cause problems if you need to > do something fancy with upssched. >The Synology boxes work fine as NUT clients, *however* they provide very little ability to configure NUT options. Specifically, the UPS name, username and password are all hard-coded (at least on DSM 6.x last time I looked at it), so the main NUT configuration on the NUT master must use these values for slaves: UPS - ups Username - monuser Password - secret Therefore protect the NUT network segment appropriately. --Larry -- Larry Fahnoe, Fahnoe Technology Consulting, fahnoe at FahnoeTech.com Minneapolis, Minnesota www.FahnoeTech.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170722/c2b0410b/attachment.html>