ubiquiti:access_point_not_showing_up_in_pending_devices
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| ubiquiti:access_point_not_showing_up_in_pending_devices [2020/10/19 09:20] – [Inform Cloudkey to Adopt] 192.168.1.1 | ubiquiti:access_point_not_showing_up_in_pending_devices [2020/10/22 22:24] (current) – removed 192.168.1.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Ubiquiti - Access Point not showing up in pending devices ====== | ||
| - | |||
| - | ===== SSH into AP ===== | ||
| - | |||
| - | Run: | ||
| - | |||
| - | < | ||
| - | ssh admin@192.168.1.18 | ||
| - | admin@192.168.1.18' | ||
| - | </ | ||
| - | |||
| - | returns | ||
| - | |||
| - | < | ||
| - | BusyBox v1.25.1 () built-in shell (ash) | ||
| - | |||
| - | |||
| - | ___ ___ .__________.__ | ||
| - | | ||
| - | | ||
| - | | ||
| - | | ||
| - | |_/ https:// | ||
| - | |||
| - | Welcome to UniFi UAP-AC-Mesh-Pro! | ||
| - | |||
| - | ACMeshPro1-BZ.v4.3.20# | ||
| - | </ | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Get Information about the AP ===== | ||
| - | |||
| - | < | ||
| - | info | ||
| - | </ | ||
| - | |||
| - | returns: | ||
| - | |||
| - | < | ||
| - | Model: | ||
| - | Version: | ||
| - | MAC Address: 78: | ||
| - | IP Address: | ||
| - | Hostname: | ||
| - | Uptime: | ||
| - | |||
| - | Status: | ||
| - | </ | ||
| - | |||
| - | <WRAP info> | ||
| - | **NOTE: | ||
| - | |||
| - | Status: | ||
| - | |||
| - | In this case, you may want to try the options below. | ||
| - | |||
| - | </ | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Inform Cloudkey to Adopt ===== | ||
| - | |||
| - | < | ||
| - | set-inform http:// | ||
| - | </ | ||
| - | |||
| - | * Where the **ip.address.of.cloudkey** is either a private address if it is local or the public address if it is remote. | ||
| - | |||
| - | returns: | ||
| - | |||
| - | < | ||
| - | Adoption request sent to ' | ||
| - | </ | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Get Information Again ===== | ||
| - | |||
| - | < | ||
| - | info | ||
| - | </ | ||
| - | |||
| - | and check if the Status line shows this is adopted. | ||
| - | |||
| - | If adopted then all done, otherwise try the rest of the statements below... | ||
| - | |||
| - | ---- | ||
| - | |||
| - | ===== Reset AP and try to Re-Adopt ===== | ||
| - | |||
| - | - Disconnect the AP from the network. Wait about 5 minutes but no more than 10. | ||
| - | - Log into the Controller on the Cloud Key and ensure that the AP is not present in any state. | ||
| - | - Power up the AP but leave it disconnected from the network for now, wait until the AP LED is solid. | ||
| - | - Power down the AP and then connect it back into your network and power up. Do not attempt to adopt it yet. | ||
| - | - Once it is powered up and has a solid white LED, ssh into it using the username ubnt and password ubnt and then issue the command: < | ||
| - | upgrade https:// | ||
| - | - The AP will then upgrade and you should be able to adopt it. | ||
| - | - Once it is adopted then you will need to enable the Uplink Connectivity Monitor on the Controller and allow the AP to mesh with other Unifi APs | ||
| - | |||
| - | If that does not work then try plugging the AP into a different port of the switch, or trying a different switch or using a power adapter. | ||
| - | |||
| - | ---- | ||
ubiquiti/access_point_not_showing_up_in_pending_devices.1603099208.txt.gz · Last modified: 2020/10/19 09:20 by 192.168.1.1