Issue with changing Management Vlan
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I recently bought an entire Omada Network including the OC200 hardware controller, the R605 Security Gateway, 3 Jetstream switches and 3 EAP access points.
From the first moment I tried to configure a management vlan different from the default one I ran into issues. At some point I found this article: https://www.tp-link.com/nl/support/faq/2814/. In different threads I see forum user (and TP-link employee?) @Fae referencing this article. Looking at the article I should follow Scenario 1, but no matter what I do, it does not work. To my opinion some key steps are missing, which aren't in scenario 2. Let's break it down.
Before starting the procedure, there is only one vlan: the default vlan. All switch ports have the profile 'all'. All devices are discovered and adopted into the Omada controller.
According to the steps in scenario 1, I made a new vlan (and interface on the R605, with DHCP) and configured it for the switches and EAPs as the management vlan. After a few minutes being in the 'configuring' state they all go into the 'disconnected' state and stay there.
This makes sense to me, because the Controller is stil in the default vlan. As far as I understand, the controller can only manage devices in the same vlan/subnet as it is itself.
As soon as I configure one switch interface with the management vlan untagged (did that before the steps of scenario 1 so I was still able to manage the switches) and plug the controller into that port after the steps and give it an IP address in the management vlan, all switches and EAPs get connected again. Only problem: the R605 Security Gateway now has the 'disconnected' state and is no longer manageable.
So my conclusion: scenario 1 is not a viable option. Although I have an Omada manageable router, in this case you have to tread it as a random router and follow scenario 2.
What do I miss here? I hope I overlook something and scenario 1 is possible indeed, but I doubt it.
Update:
I reached out to TP-Link support and they acknowledge the issue. It is under review at the moment. To be continued.
