phaZed
Well-Known Member
- Reaction score
- 3,045
- Location
- Richmond, VA
I'm hoping someone can help me here.. I'm hoping it's not time to blow away the controller software(Win Server 2012R2). I have backups if need be.
I have swapped out the AP itself and the POE injector for a known good unit, with the same effect.
This is a UAP model from 4-5 years ago and has been working for that entire time.
It is hardwired but is wireless isolated from other APs - no wireless uplink; building construction prevents it.
It connects to the same physical switch as 5 other AP's that are working without issue.
What it does:
The unit will power on and blink yellow/orange for about 1-2 minutes then will connect to the Unifi controller. During this 2 minutes all WIFI is down.
During the 1.5 minutes it is up, the internet works, clients can connect, and the controller sees it and I even had it do a firmware update (albeit it took a few tries due to the restarting).
After 1min 35seconds to approx 2 minutes the unit will disconnect and start the yellow "connecting" light all over again.
At the point of restart, the network switch's 'link light' goes out - signaling to me that the unit is truly doing a full power reset.
I have "Forget this AP" and adopted it again numerous times, even giving it a new Alias in case the controller had an issue with ID's/Database or something like that. Same issue. Adoption works fine.
It's important to note that the AP seems to stay on indefinitely when it has not been adopted yet (at least 10-15 minutes; longest I waited).
Bringing a "new" AP onsite with "new" POE injector produces the same result which is what has me stumped. So it would seem the hardware is working?
To add to the confusion, the "bad" AP and POE injector works fine on my controller here at the shop.
I can remove any of the other 5 AP's that are on site and re-adopt them without issue.
I have "hard reset" the unit via the pin-hole.
I physically took the "bad AP" and the "new AP" to the networking equipment and hooked it up with 6ft patch cables at the switch - on yet another, different POE injector.... the same behavior. So, very doubtful it's a power or wiring issue.
Some of the Googling suggests that the unit isn't getting DNS or STUN server access, but the rest of the network seems to be in order (evidenced by the others not rebooting and the fact the unit does in fact work for a short period of time).
I'm leaning towards something wrong with the Unifi controller but I wanted to see if any of our resident Unifi guys have seen this before, and if you have, any ideas to fix it? Thanks!
I have swapped out the AP itself and the POE injector for a known good unit, with the same effect.
This is a UAP model from 4-5 years ago and has been working for that entire time.
It is hardwired but is wireless isolated from other APs - no wireless uplink; building construction prevents it.
It connects to the same physical switch as 5 other AP's that are working without issue.
What it does:
The unit will power on and blink yellow/orange for about 1-2 minutes then will connect to the Unifi controller. During this 2 minutes all WIFI is down.
During the 1.5 minutes it is up, the internet works, clients can connect, and the controller sees it and I even had it do a firmware update (albeit it took a few tries due to the restarting).
After 1min 35seconds to approx 2 minutes the unit will disconnect and start the yellow "connecting" light all over again.
At the point of restart, the network switch's 'link light' goes out - signaling to me that the unit is truly doing a full power reset.
I have "Forget this AP" and adopted it again numerous times, even giving it a new Alias in case the controller had an issue with ID's/Database or something like that. Same issue. Adoption works fine.
It's important to note that the AP seems to stay on indefinitely when it has not been adopted yet (at least 10-15 minutes; longest I waited).
Bringing a "new" AP onsite with "new" POE injector produces the same result which is what has me stumped. So it would seem the hardware is working?
To add to the confusion, the "bad" AP and POE injector works fine on my controller here at the shop.
I can remove any of the other 5 AP's that are on site and re-adopt them without issue.
I have "hard reset" the unit via the pin-hole.
I physically took the "bad AP" and the "new AP" to the networking equipment and hooked it up with 6ft patch cables at the switch - on yet another, different POE injector.... the same behavior. So, very doubtful it's a power or wiring issue.
Some of the Googling suggests that the unit isn't getting DNS or STUN server access, but the rest of the network seems to be in order (evidenced by the others not rebooting and the fact the unit does in fact work for a short period of time).
I'm leaning towards something wrong with the Unifi controller but I wanted to see if any of our resident Unifi guys have seen this before, and if you have, any ideas to fix it? Thanks!
