Management VLAN setup question
I have read the FAQ at https://www.tp-link.com/us/support/faq/2814/
I have a few questions now.
I have an established non-Omada network on 192.168.1.x, which I wish to migrate to Omada (router, controller, switches, etc.).
I already have 3 EAP-225v3 on my existing network, that I will adopt in once I move over.
I started setting up the Omada gear (adopting, etc.) separately, on a bench, not connected into my existing LAN or the WAN.
I got everything (router, controller, 4 switches) adopted in, firmware updated, etc.
It is configured with LAN on 192.168.0.x as default.
I have not setup any VLANs yet.
My desired setup is:
Main LAN on 192.168.1.x
Management VLAN on 192.168.0.x
Other VLANs as I build out, not really germane to this discussion.
So the first thing I planned to do was move LAN to 192.168.1.x, which is where I want it to end up. Then I need create the management VLAN and move the Omada gear onto that.
I think I understand the FAQ, but since I'm setting up "fresh", could I disassociate & then factory-reset the router, then setup Mgmt VLAN on the controller & switches,
and then adopt the router again once I've setup the Management VLAN? Would that be easier than having to run the Discovery Tool? Since it comes up by default in 0.x, would it be "seen" by the controller (even though it doesn't have the mgmt vlan tag) and able to be adopted?
Then I could go enable management vlan on it?
Or is there a need to use the discovery utility anyway?
Or is it better to change the LAN IP range, go ahead and switch over my network, adopt my EAPs, and then go through the process to enable Mgmt VLAN?