Reply
New Member
Posts: 6
Registered: ‎10-23-2018

US-16-150W restarting AP-AC-Pro every 5 minutes...

Good afternoon,

 

I will start off my saying im not a network professional, just an enginner thats decent with computers and networks. That being said, Installed a all new unfi in my new house about 3 months ago.

 

Comcast Modem - USG - CloudKey - US-16-150W - AP-AC-PRO AP. 

House is a little over 2,000 SqFt so I just have the one wireless AP in the ceiling. I have cat6 runs to all the tv's, gaming systems etc.

 

Everything worked perfect till last night around 8pm. I noticed the AP was powering off and on. It would do it every 3-5 min.

 

To try and trouble shoot some, I took the AP down and plugged it into the switch with a small patch cable and it done the same thing. Also tried different ports. Then I hooked it up with a POE injector and it worked perfect. I put it back in place and now from port 2 on the switch, it goes to the POE injector then to the AP in the ceiling. It has been up for hours now with no isses.  So I can only conclude that the switch is dropping POE power to the AP.

 

Any idea WTF is going on?

 

Thank you,

 

Jeremy

New Member
Posts: 13
Registered: ‎10-17-2018
Kudos: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

[ Edited ]

Jeremy - open a terminal on the US-16-150W (in the controller, go to devices, select the switch, go to tools, choose open terminal) and do "cat /var/log/messages"

That should give you some insight on what's going on. I've been battling a PoE problem on US-16-150W, and the log shows "daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data" each time my PoE restarts happen, though the sensor number changes. Just an idea.

New Member
Posts: 6
Registered: ‎10-23-2018

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

I guess it has been going down before yesterday. Here is some of the log 

 

Dec 24 16:25:10 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Dec 24 16:25:10 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Dec 24 16:25:10 MainSwitch daemon.info switch: BOXSERV: Error 1 occurred reading thermal sensor 0 data
Dec 24 16:25:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Dec 24 16:25:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Dec 24 16:25:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Dec 24 16:25:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:10:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:10:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:10:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:10:12 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:10:14 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:10:14 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:10:14 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:10:14 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:10:14 MainSwitch daemon.info switch: UBNT_POE: PoE firmware check failed, reset the module. rc 0x000f
Jan 10 07:10:18 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:10:18 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:10:18 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:10:18 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:10:20 MainSwitch daemon.crit switch: UBNT_POE: Re-apply PoE config.
Jan 10 07:10:20 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:10:21 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:10:21 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:10:21 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:10:23 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:10:23 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #2, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:10:26 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:10:40 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:10:41 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:10:41 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #3, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:10:47 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:10:49 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:10:50 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:10:52 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:10:57 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:10:57 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #4, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:11:12 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:11:12 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #5, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:11:14 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:11:16 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:11:34 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Server Busy (http://192.168.1.9:8080/inform)
Jan 10 07:11:34 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #6, url=http://192.168.1.9:8080/inform, rc=7
Jan 10 07:12:01 MainSwitch authpriv.info dropbear[1384]: Child connection from 192.168.1.9:57562
Jan 10 07:12:06 MainSwitch authpriv.notice dropbear[1384]: Password auth succeeded for 'admin' from 192.168.1.9:57562
Jan 10 07:12:07 MainSwitch authpriv.info dropbear[1384]: Exit (admin): Disconnect received
Jan 10 07:12:07 MainSwitch user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Jan 10 07:14:16 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:14:17 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:14:20 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:20 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:20 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:20 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:22 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:22 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:22 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:22 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:24 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:24 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:24 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:24 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:26 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:26 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:26 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:26 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:28 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:28 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:28 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:28 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:30 MainSwitch daemon.info switch: UBNT_POE: PoE firmware check failed, reset the module. rc 0x000f
Jan 10 07:14:30 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:30 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:30 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:30 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:34 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:34 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:34 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:34 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:35 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:14:35 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #1 (last inform: 28 seconds ago), rc=11
Jan 10 07:14:36 MainSwitch daemon.crit switch: UBNT_POE: Re-apply PoE config.
Jan 10 07:14:36 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 2 data
Jan 10 07:14:36 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 3 data
Jan 10 07:14:36 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 4 data
Jan 10 07:14:36 MainSwitch daemon.info switch: BOXSERV: Error 17 occurred reading thermal sensor 5 data
Jan 10 07:14:42 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:14:53 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:14:53 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #2 (last inform: 46 seconds ago), rc=11
Jan 10 07:14:56 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:15:03 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:15:05 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:15:05 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:15:08 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:15:08 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:15:08 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #3 (last inform: 61 seconds ago), rc=11
Jan 10 07:15:08 MainSwitch user.err syslog: ace_reporter.reporter_fail(): [STATE] entering SELFRUN!!!!
Jan 10 07:15:24 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:15:24 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #4, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:15:30 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:15:32 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:15:40 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:15:40 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #5, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:15:55 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Server Busy (http://192.168.1.9:8080/inform)
Jan 10 07:15:55 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #6, url=http://192.168.1.9:8080/inform, rc=7
Jan 10 07:16:17 MainSwitch authpriv.info dropbear[1666]: Child connection from 192.168.1.9:58981
Jan 10 07:16:22 MainSwitch authpriv.notice dropbear[1666]: Password auth succeeded for 'admin' from 192.168.1.9:58981
Jan 10 07:16:23 MainSwitch authpriv.info dropbear[1666]: Exit (admin): Disconnect received
Jan 10 07:16:23 MainSwitch user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Jan 10 07:20:18 MainSwitch daemon.info switch: BOXSERV: Error 1 occurred reading thermal sensor 0 data
Jan 10 07:20:19 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:20:19 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:20:20 MainSwitch daemon.info switch: UBNT_POE: PoE firmware check failed, reset the module. rc 0x000f
Jan 10 07:20:26 MainSwitch daemon.crit switch: UBNT_POE: Re-apply PoE config.
Jan 10 07:20:32 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:20:32 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #1 (last inform: 19 seconds ago), rc=11
Jan 10 07:20:33 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:20:46 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:20:50 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:20:50 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #2 (last inform: 37 seconds ago), rc=11
Jan 10 07:20:53 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:20:55 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:20:56 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/15
Jan 10 07:20:58 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:21:06 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:21:06 MainSwitch user.err syslog: ace_reporter.reporter_fail(): inform failed #3 (last inform: 53 seconds ago), rc=11
Jan 10 07:21:06 MainSwitch user.err syslog: ace_reporter.reporter_fail(): [STATE] entering SELFRUN!!!!
Jan 10 07:21:19 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
Jan 10 07:21:21 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Unknown[11] (http://192.168.1.9:8080/inform)
Jan 10 07:21:21 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #4, url=http://192.168.1.9:8080/inform, rc=11
Jan 10 07:21:22 MainSwitch daemon.notice switch: TRAPMGR: Link Up: 0/2
Jan 10 07:21:39 MainSwitch user.err syslog: ace_reporter.reporter_fail(): Server Busy (http://192.168.1.9:8080/inform)
Jan 10 07:21:39 MainSwitch user.err syslog: ace_reporter.reporter_fail(): initial contact failed #5, url=http://192.168.1.9:8080/inform, rc=7
Jan 10 07:22:11 MainSwitch authpriv.info dropbear[2022]: Child connection from 192.168.1.9:40249
Jan 10 07:22:15 MainSwitch authpriv.notice dropbear[2022]: Password auth succeeded for 'admin' from 192.168.1.9:40249
Jan 10 07:22:16 MainSwitch authpriv.info dropbear[2022]: Exit (admin): Disconnect received
Jan 10 07:22:16 MainSwitch user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
Jan 10 07:26:37 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/15
Jan 10 07:26:37 MainSwitch daemon.notice switch: TRAPMGR: Link Down: 0/2
New Member
Posts: 13
Registered: ‎10-17-2018
Kudos: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Well, at least it's good to know this isn't an isolated issue.

UBNT, you need to act on this. There are forum posts going back almost two years on this issue and you're still putting out defective units?
New Member
Posts: 6
Registered: ‎10-23-2018

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Great. 

 

I purchased mine on Oct27 2018 from Amazon. Not sure what to do about it.

New Member
Posts: 13
Registered: ‎10-17-2018
Kudos: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Open a support request: https://help.ubnt.com/hc/en-us/requests/new?ticket_form_id=360000076634#submitRequest. I'd say do the RMA request, but I just got through that. Received my new unit on Tuesday, spent extra time installing it during off hours that night, and the same problem started happening today.
New Member
Posts: 6
Registered: ‎10-23-2018

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

[ Edited ]

Well thats just fantastic. The whole reason I chose thise setup was because it was supposed to be rock solid. I picked the 16 port so I could hook up some unfi cameras around the house and the stupid thing wont even power one access point.

 

How does the RMA proccess work with this company? This is the only switch I have in the house so if I have to send it back before they send another then I have no internet at all for who knows how long. Mad2

 

I am in Florida and still have my receipt from amazon and all that stuff. 

 

BTW, All the stuff is in a rack enclosure with 4 fans. My house stays 74 deg so I cant see anyway that they could overheat. Powered through a UPS that shows zero power issues.

New Member
Posts: 13
Registered: ‎10-17-2018
Kudos: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

It's not a power or overheating issue. With my first RMA, UBNT said this error "means a potential hardware failure."

You should read the RMA/warranty info on the UBNT site. Normal process is you request RMA, you send back your unit (you are responsible for cost of freight for returning your unit), and then they send a new one to you. If you want advance RMA (where they ship before you send yours back,) you have to get special approval.

All this is if you want to stick with the hardware. If not, are you beyond your Amazon return window?
New Member
Posts: 6
Registered: ‎10-23-2018

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Thank you for all the info. 

 

I submitted a ticket to ubnt so we will see what they say. I really hate to switch everything out but I guess thats a option if they cant send a switch that works correctly. I just looked through this forum and it seem like this is a pretty big problem to me. Tons of reports about this happening.

 

Im pretty sure that im past the return period from amazon.  As i said before, im not a big network guy. Is there another company out there that compares to the UNFI stuff?

 

Jeremy

Established Member
Posts: 1,556
Registered: ‎01-29-2015
Kudos: 210
Solutions: 58

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Depends on how you look at it. Unifi stuff is so cheap that you can afford spares, or you can pay 2x+ for another brand, pay annual support fees, etc., then depend on their better service.

New Member
Posts: 24
Registered: 2 weeks ago
Kudos: 4

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Hi 

 

I am sorry to hear you also have a US-16-150W dropping PoE. I got the feeling we are alot with this issue. Right now I only had my switch for 4 days (PoE drops from day one) and now I am without a UBNT switch (But got an old HP PoE one)  and will have to wait weeks before I get it back. 

 

Other threads:

USW-16-POW-150W dropping POE but not overheating

UniFi Switch 16 POE-150W Overheat

Unifi Switch 16: Error 17 occurred reading poe thermal sensor data

 

New Member
Posts: 14
Registered: ‎02-16-2018
Kudos: 3

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

This problem needs to be acknowledge by UBNT.  I had opened a support case and now they are suggesting I RMA the switch.  I'm waiting for approval of the RMA request now.

 

There's been a number of people with multiple switches with the same problem.

 

It seems like it's either some software bug or a design failure of the switch.

 

My switch used to run just fine, so I'm hoping it's something that can be fixed with a SW update.

 

There are folks that have had the problem with different revisions of the HW as well.  Seems like it would be a pretty huge screw up if this was HW.

Member
Posts: 267
Registered: ‎12-30-2014
Kudos: 81
Solutions: 10

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

I had an Edgeswitch ES-16-150w that also gave the same errors...

Member
Posts: 241
Registered: ‎06-08-2015
Kudos: 117
Solutions: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Man the 16-150W switch is just turning into a giant s**t show what with the other thread, now going on a year old unsolved....

Highlighted
New Member
Posts: 16
Registered: 4 weeks ago
Kudos: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

@jgs348 Hello

 

Did your APs remain on (withut reebooting) as you connected them powering after the swithc port? UBNT told me to return the switch but I see a lott of users are facing the same issue (Error 17). So, maybe the olnly solution is to power on through the POE conversion but I am not sure it will remain stable. Thanks. 

New Member
Posts: 6
Registered: ‎10-23-2018

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Mine work fine if I’m using a poe injector for power. They do not work using the switch to power them. 

 

Im wondering if a exchange is worth the hassle myself. I’m looking into some comparable Cisco stuff now. 

 

Pretty irritating that a company just ignores a major defect in a product. I don’t care to pay shipping to RMA it, but with this being a very well documented problem, they should have sent out a switch that they tested to make sure it was good and include a label to send the old one back.  

 

I mean in order for me to return this and wait for another switch to arrive, I have to either have no internet or go buy a replacement switch for the time it takes for the whole RMA process. 

 

Just my opinion though. 

Established Member
Posts: 1,008
Registered: ‎02-18-2017
Kudos: 333
Solutions: 30

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Pay the extra and get the Cisco. If you need rock-solid uptime then spend the money and get the Cisco stuff. 

Member
Posts: 241
Registered: ‎06-08-2015
Kudos: 117
Solutions: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...


@wja96 wrote:

Pay the extra and get the Cisco. If you need rock-solid uptime then spend the money and get the Cisco stuff. 


Right, of course, because expecting a product to work and do what it's supposed to do is totally unreasonable.... Roll Eyes (Sarcastic)

Established Member
Posts: 1,008
Registered: ‎02-18-2017
Kudos: 333
Solutions: 30

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

If UBNT keep making UniFi switches that don’t do what you want and you keep buying them, who’s the idiot?

Member
Posts: 241
Registered: ‎06-08-2015
Kudos: 117
Solutions: 1

Re: US-16-150W restarting AP-AC-Pro every 5 minutes...

Why is it that you need to defend UBNT at all costs? No one said keep buying (they referenced for RMA purposes to get a quicker turn around) and it's UBNT that keeps offering RMAs when they 100% know it won't fix the problem.

 

Again, it's not unreasonable to expect a freaking answer from Ubiquiti on a year old problem with zero indication that they have a clue what's going on, that seemingly with the latest updates making things even worse.

 

If you're fed up with all the perfectly valid complaints, then just don't post in these threads, it's as simple as that.

Reply