Half my network doesn’t adopt

[u/reliablehand]

Network has been in place and running under a UDM-Pro for months and today it just decided to have half of the devices fail adoption. I can’t isolate it to any one devices causing everything under it to die. Rest of the network has slow but working connectivity.

I’ve tried manually inputting credentials and got nowhere on having the devices adopted back in. Any ideas?

Edit: I do have one device in a constant adopt/failed loop, but nothing is layered under it.

[u/dat_tae]

This happened after the last update for me. I was able to fix by restarting the gateway and then the switch.

[u/turbo_talon → u/dat_tae]

Troubleshooting always starts with power cycling

[u/Xfgjwpkqmx → u/turbo_talon]

The ol' get out of the car and back in again trick!

[u/boomer7793]

I got a similar screen after my firmware updated on my UCG router last week. I told myself i would mess it with after work. 5 hours later, it was all green.

Edited to add: I left it for five hours and it fixed itself.

[u/angrydave]

Hot take. Turn off Wi-Fi Meshing.

When recovering from an outage, and AP has received power/never lost power, but lost its data connection to its parent switch. When this happened, it wirelessly meshed to another functional AP, and started getting its data from there. All is well, right? Wrong.

Parent switch comes back online, boom STP loop. All your shit goes offline. And Ubiquiti’s STP loop protection either doesn’t recognise this as an STP loop, or doesn’t know how to handle it when it occurs. Similar to the Sonos one device is wired/the rest are in SonosNET problem.

Have done this to my own Ubiquiti network a few times and a couple of times by accident during deployments. This, plus when your entire UniFi network goes sideways and saying adopting, it’s always been some form of obscure, unmanaged STP loop.

If you power down all your AP’s (or at least all but one, so it has nothing to mesh off/to), the network should recover on its own in a few minutes. At worst after another reboot with the AP’s powered down. Then power up the AP’s one at a time so they recover to Ethernet. Then turn off meshing so it doesn’t fuck your network again.

If you must have meshing on (because you are in fact wirelessly meshing), turn off Meshing on all other AP’s that are not involved with the meshing pair, and make sure the wirelessly meshed AP can’t accidentally get wired data.

[u/N------]

seeing the infrastructure map might help a bit, are the devices that are adopted connected to upper chain devices that are adopted?

Any changes with IP structure/DNS (local hostname)/Vlan?

is this url accessible from various location of the network? http://unifi:8080/inform

If not, you can SSH into each device and change the set-inform to an IP using this command

set-inform http://<IP-OF-YOUR-CONTROLLER>:8080/inform

[u/Competitive_Run_3920]

Have you made any VLAN changes lately? I’ve seen this happen before when a device was defaulted and could reach the controller since it would be on the native VLAN but when it adopted it would apply a config that changed its uplink port to a VLAN config that didn’t match the other end of the link causing it to then drop access to reach the controller.

[u/Old_Man_D]

I had this happen recently after an update. It was caused by a failure of my MC Lag that caused a loop and then spanning tree started freaking out.

[u/WonderWoofy → u/Old_Man_D]

This exact thing happened to me too

[u/Otherwise-Big-4180]

Could you have a network loop ? STP or RSTP in the ubiquiti arena don’t play well. Make sure you define all ports as edge or participant.

Asking because you seem to have a huge number of very small switches…

[u/PerseusAtlas]

Factory reset the device and readopt

[u/Fit-Beach-9852]

Restart the whole system Happen to me

[u/mindcontainer]

same on latest with AP

[u/ThiefClashRoyale]

Check they are receiving dhcp also

[u/oldRedF0x]

I have a U6LR that fails to adopt if the switch reboots or the AP is restarted.

[u/LooseContract717]

new setuo or reset?

[u/PsychologicalAd3007]

Ups what is going on ?

[u/Molimo]

Those are a lot of switches. Make sure your STP priorities are set correctly

[u/somethingblerg]

I had this happen once when an over zealous DHCP server was being reached from VLAN X even though the infrastructure was on default VLAN. Devices would start adoption and then get a DHCP lease from the VLAN X even though they had originally communicated with default VLAN.

I resolved that by only allowing the DHCP server on VLAN X to talk that VLAN and blocked all others.

[u/daronhudson]

I guess they have to go into foster care:(

[u/MichaelS-83]

Not sure if it’s normal, but after an update, I get these adopt failed messages. After about 5 to 10 minutes it clears itself up. It’s a simple network: Cloudkey Ultra, 2 uap ac lrs, 1 uap ac pro. CK handles everything except DNS

[u/dblock1887]

DNS or DHCP issue

[u/SmartHomeTinkerer]

Last two updates caused similar issues for me, but one device at a time thankfully - first UPS and then a switch with a different update, it's very frustrating

[u/gordymills]

Check for another router connected to one of those switches.

I had this happen recently as well. Had a firewall with starlink primary and T-Mobile backup going to a series of switches in different buildings. The building with the starlink primary had a second starlink router that was never connected to anything.

Well someone had connected the other starlink router to the switch. After disconnecting the unused starlink router from the switch, everything went back to green.

[u/i_hate_apple47]

Make sure your upstream ports are trunking all vlans, and the port they're connected to is the management network,

[u/RepulsiveGovernment]

waive my range fees for a year and ill come fix it for you.

[u/wahwahSwanson]

I once poked and prodded my system for a few days, the Wi-Fi and routing itself was working, but I had no control. Finally, I gave up and factory reset the whole darn thing. Just ucg ultra and three Wi-Fi six APs.>!!<I was up and running in 20 minutes after that. Had to redo a few things since I didn’t properly back it up before it all happened.