SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP DL360p gen8, two six-core Thuban-II workstations plua their monitors, and the network stack and KVM. The APC SU3000RM (3KVA) that blew up last week considered this to be just short of 60% load. The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power factor, considers this same load to be 43% load. I wasn't expecting that much of a reduction. I have the snmp-ups driver working with it, have not enabled upsmon yet, but upsc seems to get a rather limited set of data from it: minbar:root:~:1 # upsc backstop at localhost battery.runtime: 25200.00 battery.runtime.elapsed: 0.00 device.mfr: CYBERPOWER device.model: PR3000LCDRTXL2U device.serial: PTEHU2000098 device.type: ups driver.name: snmp-ups driver.parameter.mibs: cyberpower driver.parameter.pollinterval: 2 driver.parameter.port: backstop.caerllewys.net driver.parameter.snmp_version: v1 driver.parameter.synchronous: no driver.version: 2.7.4 driver.version.data: cyberpower MIB 0.1 driver.version.internal: 0.97 ups.firmware: 4.520 ups.mfr: CYBERPOWER ups.model: PR3000LCDRTXL2U ups.serial: PTEHU2000098 ups.status: OL In particular, no load, no input or output voltage. (And the runtime report is not to be trusted yet until I do a calibration run.) Is this to be expected from snmp-ups? (Also, I can so far connect only using snmpv1, but I don't know whether I should expect to get any additional data from snmpv3 anyway.) The HCL seems to imply that this UPS should *also* be supported by the powerpanel driver. However, I see from the documentation that the powerpanel driver is a lot of best-effort because cyberpower is uncommunicative about details of the protocol, and also I'm not seeing in the documentation of the powerpanel driver what type of connection it expects. Can anyone fill in that detail for me? I'd like to give it a try. -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
On 1/27/19 2:36 PM, Phil Stracchino wrote:> The HCL seems to imply that this UPS should *also* be supported by the > powerpanel driver. However, I see from the documentation that the > powerpanel driver is a lot of best-effort because cyberpower is > uncommunicative about details of the protocol, and also I'm not seeing > in the documentation of the powerpanel driver what type of connection it > expects. Can anyone fill in that detail for me? I'd like to give it a try.Actually, never mind, on re-examining the documentation I figured out it's serial. I gave it a try and it detected the UPS, but failed to establish communication: minbar:root:~:4 # /lib64/nut/powerpanel -a backstop-pp Network UPS Tools - CyberPower text/binary protocol UPS driver 0.27 (2.7.4) Warning: This is an experimental driver. Some features may not function correctly. CyberPower UPS with text protocol on /dev/ttyS0 detected Communications with UPS lost: Status read failed! According to https://networkupstools.org/ddl/Cyber_Power_Systems/PR3000E.html, at least the PR3000E is known to work with powerpanel, but apparently I'm missing something. Anyone have any hints to offer here? -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
Best result so far is actually with usbhid-ups. I'm going to have to get a USB hub though. [backstop-usb] driver = usbhid-ups port = /dev/ttyUSB0 vendorid = 0764 productid = 0601 desc = "PR3000LCDRTXL2U USB" minbar:root:~:24 # upsc backstop-usb at localhost battery.charge: 100 battery.charge.low: 35 battery.charge.warning: 20 battery.mfr.date: CyberPower Systems battery.runtime: 360 battery.runtime.low: 592 battery.type: PbAcid battery.voltage: 53.8 battery.voltage.nominal: 48 device.mfr: CyberPower Systems device.model: PR3000LCDRTXL2U device.serial: PTEHU2000098 device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ttyUSB0 driver.parameter.productid: 0601 driver.parameter.synchronous: no driver.parameter.vendorid: 0764 driver.version: 2.7.4 driver.version.data: CyberPower HID 0.4 driver.version.internal: 0.41 input.transfer.high: 131 input.transfer.low: 102 input.voltage: 116.0 input.voltage.nominal: 120 output.voltage: 116.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 42 ups.mfr: CyberPower Systems ups.model: PR3000LCDRTXL2U ups.productid: 0601 ups.realpower.nominal: 3000 ups.serial: PTEHU2000098 ups.status: OL ups.timer.shutdown: -60 ups.timer.start: -60 ups.vendorid: 0764 -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958
Charles Lepple
2019-Jan-28 02:13 UTC
[Nut-upsuser] Just an interesting data point [CyberPower SNMP]
On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net> wrote:> > SO, my full load on my core UPS is two Dell R610s, one Sun X4540, one HP > DL360p gen8, two six-core Thuban-II workstations plua their monitors, > and the network stack and KVM. > > The APC SU3000RM (3KVA) that blew up last week considered this to be > just short of 60% load. > The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power > factor, considers this same load to be 43% load. > > I wasn't expecting that much of a reduction.So... 50% load +/- 10% :-) (The use of the term "calibration" for an UPS is slightly unfortunate - it's certainly not a traceable metrology-style calibration. I would not be surprised if most of the passives were 5-10% tolerance, and not temperature compensated.)> I have the snmp-ups driver working with it, have not enabled upsmon yet, > but upsc seems to get a rather limited set of data from it:...> In particular, no load, no input or output voltage. (And the runtime > report is not to be trusted yet until I do a calibration run.)I forgot that this landed after 2.7.4: https://github.com/networkupstools/nut/pull/632/commits/3f5e3728a720aba0be76b2fccb603b04962bb904 <https://github.com/networkupstools/nut/pull/632/commits/3f5e3728a720aba0be76b2fccb603b04962bb904> I forget, is your copy of NUT built from an RPM? If so, it shouldn't be too hard to add that patch to get load, charge, input voltage/frequency and output voltage (assuming the RM205 is a superset of the RM202). You can also use snmpwalk to see what other values might be available. Since there is already a skeleton MIB mapping in NUT, the only two things needed are probably the snmpwalk outputs described at the end of this section: https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers <https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers>> (Also, I can so far connect only using snmpv1, but I don't know whether > I should expect to get any additional data from snmpv3 anyway.)Again, not my area of expertise, but as far as NUT is concerned, I think the different versions are for authentication methods (SNMPv1 is cleartext). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20190127/66f1c323/attachment.html>
Phil Stracchino
2019-Jan-28 02:31 UTC
[Nut-upsuser] Just an interesting data point [CyberPower SNMP]
On 1/27/19 9:13 PM, Charles Lepple wrote:> On Jan 27, 2019, at 2:36 PM, Phil Stracchino <phils at caerllewys.net > <mailto:phils at caerllewys.net>> wrote: >> The new Cyberpower PR3000 (also 3KVA), wqhich operates at a 90% power >> factor, considers this same load to be 43% load. >> >> I wasn't expecting that much of a reduction. > > So... 50% load +/- 10% :-) > > (The use of the term "calibration" for an UPS is slightly unfortunate - > it's certainly not a traceable metrology-style calibration. I would not > be surprised if most of the passives were 5-10% tolerance, and not > temperature compensated.)Oh, I know. But it should give the UPS a better idea of how long it can *actually* support that load, and for this purpose that's good enough for me.>> In particular, no load, no input or output voltage. (And the runtime >> report is not to be trusted yet until I do a calibration run.) > > I forgot that this landed after 2.7.4: > > https://github.com/networkupstools/nut/pull/632/commits/3f5e3728a720aba0be76b2fccb603b04962bb904 > > I forget, is your copy of NUT built from an RPM? If so, it shouldn't be > too hard to add that patch to get load, charge, input voltage/frequency > and output voltage (assuming the RM205 is a superset of the RM202).This is Gentoo Linux so it's built from the latest source version in the repository. I would tend to make the same assumption about the RM205 vs. the RM202.> You can also use snmpwalk to see what other values might be available. > Since there is already a skeleton MIB mapping in NUT, the only two > things needed are probably the snmpwalk outputs described at the end of > this > section: https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers > >> (Also, I can so far connect only using snmpv1, but I don't know whether >> I should expect to get any additional data from snmpv3 anyway.) > > Again, not my area of expertise, but as far as NUT is concerned, I think > the different versions are for authentication methods (SNMPv1 is cleartext).I actually switched to the usbhid-ups driver, and it is working far better than the snmp driver did. I just need a small USB hub now, because there's only two back-panel USB ports on this server and I now need three (KVM, GPS receiver, and UPS). -- Phil Stracchino Babylon Communications phils at caerllewys.net phil at co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958