Challenges in implementing Unifi L3 Adoption difficulties and performance concerns
Challenges in implementing Unifi L3 Adoption difficulties and performance concerns
So I am working on moving 3 devices (2 150W 8 port Unifi Switches and 1 AP Pro) onto a off-site unifi controller. Two of the switches are currently being managed by an on-site controller, while the AP is unmanaged and waiting adoption. Right now I am focused on getting the AP Pro adopted, so lets start there. I cannot get it to show up on my off-site controller, however my on-site controller can see it. I can both SSH into it with putty, or using the Unifi Chrome extension I can view that it is there and then issue the L3 adoption command. What am I doing wrong here? My first thoughts are that A. its something weird with my IP addresses - The network here uses a 192.168.85.x/24 scheme and the AP defaults to 192.168.1.20 (I cannot SSH into it without changing my IP range to a 192.168.1.X), or B. there are more devices with the same IP and that is causing conflict (One of the 150W switches has decided not to reply to the controller and use the same IP (Ill reset it later today), and a AP-Lite that is also managed by that off-site controller has done the same thing. Thoughts? Am I issuing the set-inform command wrong? (I use set-inform http://myiphere:8080/inform) Thanks!
The AP requires internet connectivity to communicate with the offsite controller. The IP address 192.168.1.20 suggests it isn’t receiving an iP through DHCP. Consider updating its firmware manually and resetting it. Firmware upgrades can be performed on the onsite controller without needing to adopt them.
I quit the AP right now and switching over. The switch has an IP, but I’m still having trouble showing it on my controller. Got any ideas?
The switch might be able to communicate with the controller. I reached out to another user on the controller, and once they logged in, it appeared. My observation is that the main distinction between us is my role as a Super Admin versus just a regular admin (mentioning adoption privileges). Now I'm also trying to adopt that AP despite the same issue.