I got a new Omada switch to replace my old one which was a very old cisco switch which stopped working. I already had a controller set up for my APs, but I cannot get my controller to adopt the switch. This is the only switch on my network.

The Omada Controller is on VLAN10, and it is on a hosted server that is on VLAN11. They both tag their traffic with these VLANs. I am trying to get my new switch to change its management to VLAN10. However I have not been successful.

I have gone into the switch on the default IP and gone into Layer3 Interfaces and added one on VLAN10 with a static IP within the VLAN and set it as administration enabled. Once I go this I am able to access the switch management on that new IP and the old one as well. However The controller only sees it as the old IP. I have tried to disable the VLAN1 interface and even just disable the administration on it but doing so also makes the VLAN10 interface stop working as well. Only way to restore it is to re-enable to the VLAN1 interface from the console.

I have set the ports PVIDs and tagged and untagged in many different combinations to no avail.

The error I get from the controller is error code 39002, Result=AdoptOneDeviceStatusResultv0(mac=***, status=22, status category=2) I have completely opened my firewall between the 2 and still same error.

For good measure I reset one of my APs and it started on VLAN1 with some address given by DHCP, my controller was able to see it and adopt it. Once adopted I was able to change the Management VLAN for it to VLAN10 and had zero issues.

My thought was I just needed to have the VLANs created on the switch, update the ports the controller is on and the router to see these VLANs, and create the new interface then deactivate the old interface and I would be good to go? Is this not right?