After that, I went back in and reset the switch’s name and Static IP. Once the device had been removed from the controller, because its IP and set-inform were already correct, it immediately re-appeared in the controller as “Pending Adoption.” I just clicked the Adopt button in the controller and very soon saw the switch Connected in the new office. If you try to forget while the status is Adopting, it says that the device is busy. The only trick was hitting the Forget button in the one-second gap between adoption attempts, when the status showed Disconnected. The solution was fairly simple: I needed to fully forget the device in the controller. However, issuing a factory reset generated a new fingerprint the MAC for the device was known by the controller but the fingerprint was not, so it rejected the adoption. That could have been adopted if the device’s IP address had allowed talking to the new network. On the controller, I see hundreds of errors like this in C:\Users\\Ubiquiti UniFi\logs\server.log: ERROR inform - invalid fingerprint: expecting, payload=], discovery_response=false, dualboot=true, ever_crash=false, fingerprint=e6:87:89:c1:0f:8f:c6:54:b5:d1:a5:7b:6f:f1:f4:b3:74:c0:b1:4f, Īlthough not explained, the “invalid fingerprint” makes sense: before the factory reset, the device had a fingerprint corresponding to a configuration in the controller. Now, info shows that the server is rejecting the adoption: Using the new dynamic IP, I was able to SSH into the switch with the default username and password (ubnt / ubnt). After this, the switch appeared in the dashboard with a dynamic IP in the new office’s IP range and immediately launched into an endless Adopting… loop. Note that this loses all custom configuration, ports names, etc. I couldn’t find simple instructions to change the static IP of the switch, so I just did a restore-default to reset it to factory defaults. When I ran info, it showed the correct set-inform status but I think it said “Unreachable”, which makes sense, since its IP was still on a different network.Ĥ. I connected a laptop directly to the switch, set the NIC on the laptop to a fixed IP in the old office’s range, and connected to the switch via SSH. but in the dashboard, it still showed the old static IP and could not be managed. The switch started passing traffic on the new network. On site, connect the switch to the network in the new office. Under Config > Network, update the Static IP to use an IP Address and Gateway in the IP range in the new office.ģ. Under Config (gear icon) > Manage Device > Forget this device, do not click Forget but rather choose Move this device to… the new office.Ģ. It was already offline by the time I started this process.ġ. Here are the steps that led to that issue and the solution. I needed to move a switch to the new, consolidated site but wound up with a “Server Reject” adoption loop. Each office had its own USG and its own range of IP addresses. You can modify the post adoption Unifi SSH username and password in the controller software by enabling 'advanced features' and then configuring your desired credentials under Site -> Device Authentication.A customer was consolidating two offices into one. Note that after adoption the SSH password will be changed from ubnt/ubnt. Configuration for the site will be automatically applied. Once you've done this, the AP should show up almost immediately in the interface of your Unifi controller saying 'pending adoption'.Īdopt the AP and enjoy the rest of your day. Tell your AP where it can find the controller by running: # set-inform You'll then need your 'inform-url' which will look something like. Then use SSH to connect to the AP, the default user and password is ubnt. It's actually a relatively straightforward thing to solve but requires a few steps which I'll outline below.įirst, power up your AP and find its IP address. We need to tell the AP where the controller resides in order for the announcement to be successful. But what about when your controller isn't on the LAN? Mine is running on a DigitalOcean droplet, for example. It starts scanning the local LAN for any controllers to 'announce' that it is here and needs configuration. A fresh out of the box Unifi Access Point has no idea what to do with itself.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |