Just got a Ubiquiti Uni-Fi AP and can't get the #@$&? thing on my network.
-
@Dashrender said:
@thecreativeone91 said:
Yeah you can't just use a new controller with one that had been setup. It need to be factory reset the tied to the new controller.
This is about the most frustrating thing of these APs. I guess it's a security thing, but really seems more like a poor implementation.
You could always manage them from the CLI on the device haha. Most controller based APs I've used require this, for security. Granted Ubquiti is much less of a controller and more of central configuration.
-
@thecreativeone91 said:
@Dashrender said:
@thecreativeone91 said:
Yeah you can't just use a new controller with one that had been setup. It need to be factory reset the tied to the new controller.
This is about the most frustrating thing of these APs. I guess it's a security thing, but really seems more like a poor implementation.
You could always manage them from the CLI on the device haha. Most controller based APs I've used require this, for security. Granted Ubquiti is much less of a controller and more of central configuration.
I guess you're right, I'm kinda barking up the wrong tree.
Like the OP I had to deal with this when moving an AP from one location to a new one recently. Took me the better part of 3 hours to figure it out.. wasn't simple to say the least!
Though in the end, hard resetting the AP, then ensuring the AP and controller software were on the same subnet for configuration did solve my problem.
-
@Dashrender said:
@thecreativeone91 said:
@Dashrender said:
@thecreativeone91 said:
Yeah you can't just use a new controller with one that had been setup. It need to be factory reset the tied to the new controller.
This is about the most frustrating thing of these APs. I guess it's a security thing, but really seems more like a poor implementation.
You could always manage them from the CLI on the device haha. Most controller based APs I've used require this, for security. Granted Ubquiti is much less of a controller and more of central configuration.
I guess you're right, I'm kinda barking up the wrong tree.
Like the OP I had to deal with this when moving an AP from one location to a new one recently. Took me the better part of 3 hours to figure it out.. wasn't simple to say the least!
Though in the end, hard resetting the AP, then ensuring the AP and controller software were on the same subnet for configuration did solve my problem.
You can also tell it to re-initialize it's controller relationship via the cli... but it is much easier to just do a hard reset.
-
using a laptop or desktop to install the controller is mistake number one.
Take the time to find a permanent location to run the controller.
Once this is done, simply add a DNS entry to the local DNS server that directs the DNS name "unifi" to the IPof the controller.
Plug in the brand new UAP or default the existing one.
It will then use that DNS name to send the handshake to the controller and be ready to be adopted and set up.
Doing this with any controller that is not permanent will mean you will be resetting the unit the next time you want to make a change because your controller will not likely be the same.
-
I haven't looked - do I assume correctly that there's a way to migrate the controller? Say server migration?
-
I hope so, as I installed the controller on my desktop without really thinking about it. I'm worried now!
Surely nothing is ever "permanent" and there must be a way of backing up and/or migrating?
-
OK looks like it's pretty easy.
If you're staying local, you just backup the controller, turn it off, install on the new location, restore and you're done.
But if you are moving to a different subnet with the controller, you'll have to follow the layer-3 setup.
https://community.ubnt.com/t5/UniFi-Controller-Installation/UniFi-Layer-3-methods-for-UAP-adoption-and-management/ta-p/455643 -
@JaredBusch said:
using a laptop or desktop to install the controller is mistake number one.
Take the time to find a permanent location to run the controller.
Once this is done, simply add a DNS entry to the local DNS server that directs the DNS name "unifi" to the IPof the controller.
Plug in the brand new UAP or default the existing one.
It will then use that DNS name to send the handshake to the controller and be ready to be adopted and set up.
Doing this with any controller that is not permanent will mean you will be resetting the unit the next time you want to make a change because your controller will not likely be the same.
Yeah, cause that's so much simpler than hitting the reset button.
-
Thanks for the help, especially Chad. I doesn't seem very intuitive that you can take a brand new device out of the box, install it, connect it to the (very basic) network, download the controller, see that the controller sees it on the network, see the solid LED display on the device that says it's working properly on the network, and then be required to reset it to factory settings to get it to automatically work perfectly. What about the settings was not "factory" when I took it out of the box 5 minutes ago???
-
@art_of_shred said:
Thanks for the help, especially Chad. I doesn't seem very intuitive that you can take a brand new device out of the box, install it, connect it to the (very basic) network, download the controller, see that the controller sees it on the network, see the solid LED display on the device that says it's working properly on the network, and then be required to reset it to factory settings to get it to automatically work perfectly. What about the settings was not "factory" when I took it out of the box 5 minutes ago???
LOL you're kidding right? I know many people around here dislike SonicWall, but I'll tell you my story anyhow. Several years ago, picked up a few Brand new SWs, attached them to my network. The default status of their firmware caused my AIX server to freakout and drop all connections. Only after reflashing the device with the exact same firmware was the problem resolved.
While it's nice to think that from the factory is in a pristine condition, that's not always the case, and a reset immediately is sometimes required.
-
@art_of_shred said:
Thanks for the help, especially Chad. I doesn't seem very intuitive that you can take a brand new device out of the box, install it, connect it to the (very basic) network, download the controller, see that the controller sees it on the network, see the solid LED display on the device that says it's working properly on the network, and then be required to reset it to factory settings to get it to automatically work perfectly. What about the settings was not "factory" when I took it out of the box 5 minutes ago???
Likely a returned unit.. Maybe a QC unit that didn't get reset after testing.
