for a long time I am using the setup with many brances and one central (public) EAP Controller successfully.
But somehow adopting new EAPs ist not possible anymore. I tried booth using the new Omada Discovery Tool as well als the old EAP Discover.
Omada Discovery Tool: I have both the Discovey Tool and the EAP in my local network. The tool shows the correct EAP and I try to manage it. After typing all the data (the public hostname, user and password) the tool says "Setting Succeed". But even after refresh the EAP don't show up in the default-Site.
The same with the EAP Discover.
I thought that maybe there is a problem with my controller so first I did an update to the latest 3.2.10 - but no success with adopting. Checked for firewall and stuff but everything seems OK.
To verify the setup I also used an old computer and installed the EAP Controller in my local network. The Controller has the build-in discovery-function and adopting with that would be successful (it lists the EAP as "managed by others". But that doesn't help with my setup. Using the Discovery Tool after resetting the EAP it shortly disappears in the controller after Discovery Tools says "successfull".
Don't have any ideas anymore...
By the way: What is the difference between the new Omada Discovery Tool and the old EAP Discover?