In the Adopt window that will appear, select the controller and the site that will be adopting the device and click Adopt.ġ. Go to and log in with your Ubiquiti SSO credentials.Ģ. Go to the Devices section and locate the model with the Pending Adoption status. To access the Controller remotely Remote Access will have to be enabled. UniFi APs have a default inform URL Thus, the purpose of using DHCP option 43 or DNS is to allow the AP to know the IP of the Controller.Īfter installing the Discovery tool plugin (freely available in Chrome Web Store) on a computer running Chrome browser, any locally-available, unmanaged UniFi Devices (i.e., same L2 network as your computer) will appear as “Pending Adoption” in the UniFi Cloud Access Portal as well as your UniFi Network Controller itself (in the Devices section in both cases). LAN port connected locally to access management features on the router (USG or third party). Also, remember that in order to adopt, the following conditions must be true in order to have internet access and also have access to the router from within the network (locally):Ģ. Please make sure you’re familiar with how a regular L2 adoption on UniFi works (where the devices and Controller are on the same network) before attempting 元 (remote) adoption. Either configure the DHCP server, DNS server or simply use the UniFi Discovery Utility to make all local access points (APs) inform back to the controller.Create a virtual controller instance on Amazon EC2.When you’re at the site, open a browser and navigate to Cloud: either the UniFi Cloud Access Portal or the UniFi Network Controller (when launched using Cloud).Take a laptop to the device’s site to perform adoption via Chrome Browser (easiest method).In many deployments where it’s not possible to have the UniFi Network Controller running on-premise, you can run the controller in the Cloud or your NOC. For example, for a large-scale project with many devices there are a few possible methods for adoption of devices: Encrypted FireFighter™ Listener-Transmitter.Encrypted Outdoor Wireless Contact Sensor.Syncing Teams document libraries to your desktop.Since your post is the only feedback one receives for this issue I am at a complete loss as to why this is the way it is. Until the device looses connection to the Controller due to the Controller being upgraded, restarted or the AP/Switch having been upgraded/restarted. I shall note that everything is in the local LAN and the set-inform does indeed change the inform IP. If I issue the command right after having issued it for the first time (like within less than a second) then I can tell that it briefly hangs in the CLI before showing the prompt line again. It also doesn't have any actual affect when I issue it. Therefore the second set-inform command is then too late. So by the time I am in fact back at the CLI it might still show "Provisioning" but certainly no longer "Adopting". It's simply not possible to log back in during that short period and reissue the command, especially as I need to also enter the password. There is now way for me to SSH back in during the very short phase it shows "Adopting" because it will switch to "Provisioning" very quickly (I have maybe 5 seconds). It then switches to "Adopting" and at that point I loose the SSH connection. When I do the set-inform the device will, in the Controller, briefly show "Inform error" (after it was initially "Disconnected"). This will permanently save the inform address, and the device will start provisioning.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |