Tech Support Forum banner
Status
Not open for further replies.

Unifi AP troubleshooting

12K views 2 replies 2 participants last post by  duvnull  
#1 ·
I could really use some help with some Ubiquiti UniFi APs that are giving me some trouble.

I have a UniFi controller on a Win2008 server with multiple APs placed around an office. For the most part, it works - however, there are a couple of APs that go offline in the mornings and come back up on their own a few hours later. When they go down, their status is listed as "disconnected" on the web GUI and I am unable to ping or otherwise communicate with them - I am also unable to discover them using the discovery utility with the OS firewall and antivirus disabled.

I am not aware of any hardware or software changes that were made. My understanding is that everything was working just fine up until a few weeks ago.

When the APs come back up, they take clients right away and I'm able to SSH into them. Here's what stands out to me in the AP logs that I see for today - at the end of this section is where you see the correct date and time and the client association messages. That last line in the below quote is when this particular AP came back up.

Dec 31 18:00:29 [AP name] user.notice syswrapper: current time is not set yet
Dec 31 18:00:29 [AP name] user.notice syswrapper: current time is not set yet
Dec 31 18:00:29 [AP name] user.notice syswrapper: current time is not set yet
Dec 31 18:00:29 [AP name] user.notice syswrapper: current time is not set yet
Dec 31 18:00:29 [AP name] user.err syslog: ace_reporter.reporter_fail(): Waiting for IP (http://[Controller IP]:8080/inform)
Dec 31 18:00:29 [AP name] user.err syslog: ace_reporter.reporter_fail(): initial contact failed #1, url=http://[Controller IP]:8080/inform, rc=2
Dec 31 18:00:31 [AP name] user.notice syswrapper: ipready.br0 = [AP IP]
Dec 31 18:00:31 [AP name] daemon.info init: process '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org' (pid 798) exited. Scheduling for restart.
Dec 31 18:00:31 [AP name] daemon.info init: starting pid 868, tty '/dev/null': '/sbin/ntpclient -i 86400 -n -s -c 0 -l -h 0.ubnt.pool.ntp.org'
Dec 9 09:53:19 [AP name] user.info syslog: ace_reporter.reporter_set_managed(): [STATE] enter MANAGED
This kind of fell into my lap and I am not familiar with Unifi products. I haven't found much through Google, so I'm hoping that someone will have some ideas.
 
#2 ·
I think I managed to fix this. For anyone else who may run into the same problem, disabling the Uplink Connectivity Monitor appears to be done it for me.

As far as I can tell, what this does is monitor the gateway IP - if contact with that IP is lost, it puts the AP into isolation mode, which effectively downs the unit. This feature is only required for wireless uplinks, so if the APs are cabled then it can be safely disabled.
 
Status
Not open for further replies.
You have insufficient privileges to reply here.