Anyone Have A US-16-150W Resetting POE Module Randomly

I was wondering if anyone has seen this before. I noticed that my CK2+ and AP were rebooting at random, at first I thought maybe its a thermal issue on the CK causing a reboot which is in turn pulling down the AP but checking the logs for the CK it doesn't report anything out of the ordinary.

I have checked the switch logs and I see the below each time an outage occurs. I don't lose traffic on non-poe devices so it appears to be a reset of the POE module. Also I have monitored the switches temp and it never goes above 60c.

Any ideas would be great, I have read other comments on here regarding the reliability of the 16-150s before and advice to just go for the 24 port switches instead.

Jul 10 05:45:26 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jul 10 05:45:26 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data   
Jul 10 05:45:28 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jul 10 05:45:28 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jul 10 05:45:28 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jul 10 05:45:28 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jul 10 05:45:30 POE daemon.info switch: UBNT_POE: PoE firmware check failed, reset the module. rc 0x000f
Jul 10 05:45:30 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jul 10 05:45:30 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jul 10 05:45:30 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jul 10 05:45:30 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jul 10 05:45:34 POE user.err syslog: mcad[1000]: ace_reporter.reporter_fail(): Unknown[11] (http://<CK2 FQDN>:8080/inform)
Jul 10 05:45:34 POE user.err syslog: mcad[1000]: ace_reporter.reporter_fail(): inform failed #1 (last inform: 23 seconds ago), rc=11
Jul 10 05:45:34 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jul 10 05:45:34 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jul 10 05:45:34 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jul 10 05:45:34 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jul 10 05:45:36 POE daemon.crit switch: UBNT_POE: Re-apply PoE config.
Jul 10 05:45:36 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jul 10 05:45:36 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jul 10 05:45:36 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jul 10 05:45:36 POE daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jul 10 05:45:41 POE daemon.notice switch: TRAPMGR: Link Down: 0/1
Jul 10 05:45:41 POE daemon.info switch: DOT1S: Port (1) inst(0) role changing from ROLE_DESIGNATED to ROLE_DISABLED
Jul 10 05:45:43 POE daemon.notice switch: TRAPMGR: Link Up: 0/4
Jul 10 05:45:43 POE daemon.info switch: DOT1S: Port (4) inst(0) role changing from ROLE_DISABLED to ROLE_DESIGNATED
Jul 10 05:45:48 POE daemon.notice switch: TRAPMGR: Link Up: 0/1
Jul 10 05:45:48 POE daemon.info switch: DOT1S: Port (1) inst(0) role changing from ROLE_DISABLED to ROLE_DESIGNATED
Jul 10 05:45:48 POE daemon.info switch: DOT1S: Port (2) inst(0) role changing from ROLE_DISABLED to ROLE_DESIGNATED
Jul 10 05:45:48 POE daemon.notice switch: TRAPMGR: Link Up: 0/2
Jul 10 05:45:51 POE daemon.notice switch: TRAPMGR: Link Down: 0/1
Jul 10 05:45:51 POE daemon.info switch: DOT1S: Port (1) inst(0) role changing from ROLE_DESIGNATED to ROLE_DISABLED
Jul 10 05:45:53 POE user.err syslog: mcad[1000]: ace_reporter.reporter_fail(): Unknown[11] (http://<CK2 FQDN>:8080/inform)
Jul 10 05:45:53 POE user.err syslog: mcad[1000]: ace_reporter.reporter_fail(): inform failed #2 (last inform: 42 seconds ago), rc=11
Jul 10 05:45:54 POE daemon.notice switch: TRAPMGR: Link Up: 0/1

Posted Jul 10, 2019, 10:34 AM UTC

24
[deleted]•

[removed]

1
2spky4u•

I have the same issue and the same log outputs. It’s happened 3 times in the last month, oddly enough every time it’s been during a thunderstorm. No direct strikes on or near my house, but oddly enough that’s when it always occurs. I’ve purchased some ETH-SP-G2 units to try and see if that helps. My whole rack is surge protected with a UPS otherwise.

1
WuzzlemeanstomixUnifi User•

Had same issue during storms, replaced my switch with a different one of the same model, no issues. On UPS and grounded the switch.

1
robjwalker•

Pretty sure there are several reports of this on the official forums. Mine seems fine so far, but maybe I'm just lucky.

1