@TOmega 

I my personal experience I have found this to be a major problem with Omada, particularlly when adopting/changing the router.

If you create a management VLAN and place all Omada devices and the controller on this network, then you will have problems. In the router configuration you can set DHCP option 138 to tell devices where the Omada Controller is, but this (obviously) will not work if you are attempting to adopt/replace the router itself.

eg. When you replace/reset your router it will have a default IP of 192.168.0.1. If you have a management VLAN on 192.168.50.x then nothing is going to work.

I messed around with various configurations over the last couple of years and came to the conclusion that the _only_ way to configure the network that is consistently reliable is to make the factory default LAN (192.168.0.1/24) the "management" LAN. I have several VLANS for client devices and keep all the Omada devices on this default LAN.

Make sense ?