BUILD Is UPS CyberPower CP900EPFCLCD natively supported?

[Arkhen]

Hi

So I'm currently looking for a UPS solution for my FreeNAS server, and I was wondering if the CyberPower CP900EPFCLCD is natively supported under Services -> UPS -> Driver drop-down list
(example: http://i.imgur.com/m79qVam.png )
I'm not able to find a matching driver, do you know if this product would work with FreeNAS' integrated drivers, if yes, which one?

I'm from Sweden, so the naming conventions for the UPS might be a little different from the American. I assume the CP900EPFCLCD stands for EU due to our wall socket form factors.

Link to the desired UPS:
https://www.proshop.se/UPS/CyberPower-PFC-Sinewave-Series-CP900EPFCLCD-UPS-/2498520?s=CP900EPFCLCD

My FreeNAS' parts, in case you need it to determine an answer:
- Motherboard: SuperMicro X11SSH-F
- Build: FreeNAS-9.10.1-U4
- CPU: Xeon E3-1270 v5
- HDD: WD 4TB Reds
- RAM: Crucial 32GB Kit (2 x 16GB) DDR4 ECC

Thanks a lot in advance!

 

[m0nkey_]

Yes, this UPS is supported, I have the 1350VA NA version. I doubt the EU version would be any different.

Select your UPS from the list and ensure the selected driver is usbhid-ups.

 

[Arkhen]

Yes, this UPS is supported, I have the 1350VA NA version. I doubt the EU version would be any different.

Select your UPS from the list and ensure the selected driver is usbhid-ups.

That's the problem. I'm unable to find the exact model of "CP900EPFCLCD" on the list, where I can only find the "CP1000PFCLCD USB (usbhid-ups)" option, being the closest resemblance.
Screenshot of my list: http://i.imgur.com/gi8NHT8.png

 

[m0nkey_]

Use the CP1000PFCLCD. It's the same driver.

 

[Arkhen]

Use the CP1000PFCLCD. It's the same driver.

Ah okay, thanks.

 

[indy]

I bought that exact model about a month ago from amazon.

The unit seems to have a nice build quality but there are 2 areas with problems, at least for me.

1) The log is showing random disconnects about once every day

Code:

Nov 11 08:02:11 freenas ugen1.3: <vendor 0x0764> at usbus1 (disconnected)
Nov 11 08:02:17 freenas devd: Executing 'kldload -n uhid'
Nov 11 08:02:17 freenas usbd_set_config_index: could not read device status: USB_ERR_TIMEOUT
Nov 11 08:02:17 freenas ugen1.3: <CPS> at usbus1
Nov 11 08:02:43 freenas upsd[2229]: Data for UPS [ups] is stale - check driver
Nov 11 08:02:46 freenas upsmon[2237]: Poll UPS [ups] failed - Data stale
Nov 11 08:02:46 freenas upsmon[2237]: Communications with UPS ups lost
Nov 11 08:02:46 freenas upsd[2229]: UPS [ups] data is no longer stale
Nov 11 08:02:51 freenas upsmon[2237]: Communications with UPS ups established

I did not yet follow this up in detail yet but there seem to be some bug reports pertaining to that problem.
Setting the "MAXAGE 30" option in the upsd.conf seems to help the problem, but there are are stilly (roughly) daily disconnects.

2) The ethernet protection port causes lots of disconnects to the lan connection

Code:

Nov  8 07:07:05 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:07:05 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:07:10 freenas kernel: igb0: link state changed to UP
Nov  8 07:07:10 freenas kernel: igb0: link state changed to UP
Nov  8 07:07:10 freenas devd: Executing '/etc/rc.d/dhclient quietstart igb0'
Nov  8 07:09:52 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:09:52 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:09:56 freenas devd: Executing '/etc/rc.d/dhclient quietstart igb0'
Nov  8 07:09:56 freenas kernel: igb0: link state changed to UP
Nov  8 07:09:56 freenas kernel: igb0: link state changed to UP
Nov  8 07:11:36 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:11:36 freenas kernel: igb0: link state changed to DOWN
Nov  8 07:11:41 freenas devd: Executing '/etc/rc.d/dhclient quietstart igb0'

Again I did not do much troubleshooting on this but rather just plugged the cable directly into the switch port again.

Maybe someone else who has had the unit for longer can comment on this and give you some buying advice

 

[m0nkey_]

The log is showing random disconnects about once every day

I had the same problem. Replace the cable and make sure you're not using a USB3 port. No longer seeing disconnects.

The ethernet protection port causes lots of disconnects to the lan connection

Don't use the Ethernet port protection. It's only good for FastEthernet.

 

[indy]

I switched the USB port and the USB cable.

This is what it looks like without "MAXAGE 30"

Code:

Nov 13 23:23:03 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:23:04 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:23:04 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:23:06 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:23:09 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:24:40 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:24:41 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:24:41 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:24:43 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:24:46 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:26:19 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:26:22 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:26:22 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:26:24 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:26:27 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:29:26 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:29:29 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:36:52 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:36:57 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:38:29 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:38:29 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:42:15 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:42:15 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:43:18 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:43:19 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:43:19 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:43:19 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:43:24 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:45:27 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:45:28 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:47:31 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:47:32 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:47:32 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:47:33 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:47:37 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:49:03 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:49:04 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:49:04 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:49:06 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:49:09 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:50:40 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:50:43 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:51:42 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:51:44 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:52:14 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:52:16 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:53:15 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:53:18 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:53:18 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:53:21 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:53:24 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:56:25 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:56:26 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 13 23:56:26 freenas upsmon[2304]: Communications with UPS ups lost
Nov 13 23:56:31 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 13 23:56:31 freenas upsmon[2304]: Communications with UPS ups established
Nov 13 23:59:41 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 13 23:59:44 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 14 00:00:00 freenas syslog-ng[1628]: Configuration reload request received, reloading configuration;
Nov 14 00:01:45 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 14 00:01:46 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 14 00:01:46 freenas upsmon[2304]: Communications with UPS ups lost
Nov 14 00:01:49 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 14 00:01:52 freenas upsmon[2304]: Communications with UPS ups established
Nov 14 00:03:23 freenas upsd[2296]: Data for UPS [ups] is stale - check driver
Nov 14 00:03:24 freenas upsmon[2304]: Poll UPS [ups] failed - Data stale
Nov 14 00:03:24 freenas upsmon[2304]: Communications with UPS ups lost
Nov 14 00:03:26 freenas upsd[2296]: UPS [ups] data is no longer stale
Nov 14 00:03:29 freenas upsmon[2304]: Communications with UPS ups established

 

[Arkhen]

Do you just add the "MAXAGE 30" to the auxiliary parameters from the UPS GUI?
Edit: "Auxiliary parameters (upsd.conf):" that is.

 

[indy]

Yes, that is where you can enter the line.

 

[Arkhen]

Yes, that is where you can enter the line.

Have you seen any noticeable improvements or changes by using "MAXAGE 25" instead of 30? I read a few forum topics where people have been using 25.

 

[indy]

From my understanding MAXAGE specifies how long the service waits for the driver to respond.

This is an example from the log with MAXAGE 30 set

Code:

Nov 16 20:19:23 freenas upsd[13835]: Data for UPS [ups] is stale - check driver
Nov 16 20:19:24 freenas upsd[13835]: UPS [ups] data is no longer stale

My guess is that if MAXAGE would have been set to 32 or more this sequence would have been avoided.

 

[Arkhen]

Received the new UPS and it has been running for a day now, without any issues. Used the driver for CP1000PFCLCD, works fine.
I didn't bother using the stock USB cable, and swapped it with an old one I had handy. Also added "MAXAGE 30" under "Auxiliary parameters (upsd.conf):" just for good measure.

Thank you for your help!

 

[glauco]

After using UPS CyberPower CP900EPFCLCD for over a year to protect FreeNAS, I've finally gotten around to setting up a USB connection between the two.
And hooray, it works!
Even though this is an old thread, I just wanted to confirm that it works.
I'm using driver Cyber Power Systems ups 2 CP900AVR USB (usbhid-ups). The exact model is still not listed, but it works nonetheless.
One thing that puzzles me, though, is I set /dev/ugen0.4 as port, because dmesg | grep CP900EPFCLCD gave me ugen0.4: <CPS CP900EPFCLCD> at usbus0. But after the machine booted up again, dmesg | grep CP900EPFCLCD gave me ugen0.2: <CPS CP900EPFCLCD> at usbus0.
Even if I haven't changed anything in Services > UPS > Settings, I still get the e-mail alerts.
So, does it really make any difference what port I set in the UPS settings?
Thank you.