UniFi - Device Adoption Methods for Remote UniFi Controllers

Transcription

1 UBNT Support Search / UniFi Enterprise / UniFi Getting Started Follow UniFi - Device Adoption Methods for Remote UniFi Controllers April 02, :32 Was this useful? Help us identify your favorite articles by clicking on the thumbs up at the bottom of the page. And if you think this article is not useful, please let us know why by clicking on the feedback link below! Overview This article describes several different layer-3 methods for deploying UAPs. Our recommended methods are found below under the Chrome Web Browser and Mobile App sections. Table of Contents 1. Introduction 2. Initial Setup 3. Chrome Web Browser (recommended) 4. Mobile App (recommended) 5. Discovery Utility 6. DNS 7. DHCP Option SSH 9. User Notes & Tips

2 10. Related Articles Introduction In many deployments where it's not possible/desired to have the controller running at the premise, you can run the controller in the cloud or your NOC. Say we have a large-scale project with many Devices, we could: Take a laptop to the UAP Site to adopt devices via Chrome Browser (easiest method) On Amazon, create a virtual controller instance on EC2. Read this article on the subject. Configure/stage a few APs in our lab and customize the guest portals. When we're at the customer's site, open a browser to the cloud-based controller. Either configure DHCP server, DNS server, or simply use the UniFi Discovery Utility to make all local APs inform back to the controller. On-going management/monitoring can be done anywhere and Amazon would provide us with great firewall configurations. Initial Setup Can't find what you're looking for? Please make sure you're familiar with how UniFi works (e.g. where AP and Controller is in the same L2) before attempting L3 Management. 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. Chrome Web Browser After installing the Discovery tool plugin (freely available in Chrome Web Store) on

3 your desktop PC running Chrome browser, locally-available, unmanaged UniFi Devices (i.e., same L2 network as your desktop PC) will appear "Pending Adoption" for L3 management via either of two cloud-ready UniFi interfaces: A. UniFi SDN Cloud Dashboard (unifi.ubnt.com) - "Pending Adoption" B. UniFi Elite Controllers - "Pending Adoption - Locally Discovered"

4 1. To begin adoption, click on the device you wish to adopt. This will reveal the Properties Panel. 2. Within the Properties 3. While still under the 4. Optionally, you can

5 Panel navigate to the Adopt section, then select the UniFi Controller & Site, then click Adopt to adopt & manage the Device immediately. Adopt section, you can optionally set up Advanced Options relating to settings for the UniFi Controller & Site to which the Device will be adopted/managed. navigate to the Configure section to configure the Device with management settings (to be applied after adoption). Mobile App 1. After installing the UniFi Mobile App (freely available in ios App Store & Android Play Store), launch the app, and tap Direct Access (in ios, in Android you will see the Direct Access section on the screen once you launch the app, see images below). NOTE: Your mobile device must be connected to the same network as your devices, and must be able to access the controller directly (using HTTP). A public IP and/or port forwarding may be necessary. The inform port of the controller must be Select your controller from the list, or tap the "+" button to log in and add your controller. ios Android

6 3. For ios: Once logged in to the controller, tap More. Here you will see the Layer 3 Adoption option under Utilities. For Android: Tap the three-line "hamburger" menu and scroll down until you see L3 Adoption under Utilities. ios Android

7 3. Devices will be displayed on this screen. Tap on the device you wish to adopt and select Adopt. ios Android

8 4. After a few seconds (15-30 seconds, times will vary) the device will appear under the Devices section, which you can access by clicking on the Devices icon on the bottom menu bar. Discovery Utility Not many environments can have a DHCP server that's configurable, even less likely with a DNS server. That's where UniFi Discovery Utility comes in. It listens to the multicast/broadcast packets from UniFi APs and allow you to tell the AP to inform any URL you'd like. (only APs in default state or not in contact with any controller will be displayed) UniFi Discovery utility is installed along with your UniFi controller.

9 On Windows, it's in Start Menu->Ubiquiti UniFi->UniFi-Discover On Mac, /Applications/UniFi-Discover.app (or use Spotlight to find it) Run "java -jar <unifi_base>/lib/ace.jar discover" To perform L3 adoption with the discovery utility: 1. Wait until the AP shows up 2. If the AP is not in default state. click "reset", specify the SSH username/password and click "Apply" 3. Click on "manage", modify the inform URL and leave the SSH username/password as ubnt/ubnt and click "Apply" 4. Open a browser to your remote UniFi controller and you should see it being "Pending Approval" 5. Click on "adopt". You'll see it going to "Adopting" state, ignore it as it'll eventually become "Adoption Failed" or "Disconnected" 6. perform [step 3] again (no need to wait for [step 5] to finish) 7. AP is now managed by the controller Once adopted, the Controller will upgrade these units automatically. The option of the Ubiquiti Discovery Tool Chrome Extension is also available, downloadable directly from Google Chrome here, or from our UBNT download page. NOTE: If your L3 controller is available over the WAN then you need to make sure the necessary ports are open at the controller side (minimum port 8080 for inform). If you do not have a static IP then you may want to consider using a dynamic DNS service, and use the domain name instead of the IP for the inform address. If you're using a USG then you can use the DDNS client that is available on that device itself. DNS You'll need to configure your DNS server to resolve 'unifi' to your controller's IP

10 address. Make sure that AP can resolve controller's domain name. For example, if you are setting then ping from AP to determine if XYZ is resolvable/reachable. Or, using FQDN for the controller inform URL, Troubleshooting - AP (with static IP) fails to connect to the L3 controller when configured an AP from DHCP to static in the controller UI, make sure you have put the IP of DNS. If not, then the AP cannot contact DNS to resolve controller domain name. if the AP has been reset (by pushing reset button), make sure that you have informed AP twice (using discovery utility) about the controller's location (this will be improved in the coming release 2.3.0) DHCP Option 43 If using Ubiquiti's EdgeMax routers, then DHCP option 43 can be done by just entering the IP address of the UniFi controller in the "unifi" field on the dhcp-server. To use DHCP option 43 You'll need to configure your DHCP Server. For example: Linux's ISC DHCP server: dhcpd.conf #... option space ubnt; option ubnt.unifi-address code 1 = ip-address; class "ubnt" { match if substring (option vendor-class-identifier, 0, 4) = "ubnt"; option vendor-class-identifier "ubnt"; vendor-option-space ubnt; } subnet netmask { range ; option ubnt.unifi-address ; ### UniFi Controller IP ### option routers ; option broadcast-address ; option domain-name-servers , ; #...

11 } Cisco CLI # assuming your UniFi is at ip dhcp pool <pool name> network <ip network> <netmask> default-router <default-router IP address> dns-server <dns server IP address> option 43 hex 0104C0A8030A # > CO A8 03 0A # Why 0104C0A8030A? # # 01: suboption # 04: length of the payload (must be 4) # C0A8030A: Mikrotik CLI /ip dhcp-server option add code=43 name=unifi value=0x0104c0a8030a /ip dhcp-server network set 0 dhcp-option=unifi # Why 0104C0A8030A? # # 01: suboption # 04: length of the payload (must be 4) # C0A8030A: Cisco has a good write-up for DHCP option 43 setup. To use IP of controller You can also use the IP of the controller in the inform URL instead of the domain name. User Tip: Find more DHCP Option 43 instructions in the User Notes & Tips section. SSH If you can SSH into the AP, it's possible to do L3-adoption via CLI command:

12 1. Make sure the AP is running the same firmware as the controller. If it is not, see this guide: UniFi - Changing the Firmware of a UniFi Device. 2. Make sure the AP is in factory default state. If it's not, do: syswrapper.sh restore-default 3. SSH into the device and type the following and hit enter: set-inform 4. After issuing the set-inform, the UniFi device will show up for adoption. Once you click adopt, the device will appear to go offline. 5. Once the device goes offline, issue the set-inform command from step 3 again. This will permanently save the inform address, and the device will start provisioning. NOTE: The set-inform command must be issued twice. Otherwise the device will disconnect after appearing to adopt. The process to be followed is: 1. Issue the set-inform command from step 3 above. 2. The device will appear ready for adoption in the controller. Click Adopt. 3. Wait for the 'Adopting' status to appear on the UniFi controller, then issue the set-inform command again. 4. The device should now change to a 'Provisioning' status and then connect shortly thereafter. User Notes & Tips These notes have been added thanks to user collaboration. Have anything to contribute? Click on the Give Feedback button below! Using PFSense with DHCP Option 43 NOTE: As in all our examples, we are using a sample IP address, you would input your own.

13 1. Input your IP in 2. Click Convert to Hex! 3. Add 01:04 to the beginning of the converted IP, so it would look something like this: 01:04:ac:10:21:04 4. Insert this in the Value field. Using Palo Alto Networks with DHCP Option 43 (Pan OS 7.1)

14 Related Articles How to Establish a Connection Using SSH UniFi - Changing the Firmware of a UniFi Device. Was this article helpful?! " 12 out of 17 found this helpful

15 Let us know what we missed! Send L G Feedback Don t see what you are looking for? Get advice from our Community or Submit a Help Ticket. UNIFI COMMUNITY SUBMIT A REQUEST Ubiquiti Home Compliance Info Warranty & RMA Terms Of Service Privacy Policy 2018 Ubiquiti Networks, Inc. All rights reserved.