Configuring Management VLAN in Omada
I've set up a Management VLAN (ID 69) across my network. Devices in this VLAN have IP addresses in the 10.0.69.x range, and my Omada Controller is on 10.0.69.20 and communicates fine. However, my router remains on the default VLAN with IP 192.168.0.1 and I can't seem to move it to the Management VLAN. Does my setup sound correct?
How can I connect my router to the Management VLAN? When I attempt to update the PVID on the Router Trunk port from the default setting of 1 to the new management setting of 69, the router begins the configuration process but then disconnects.
Additionally, I am currently running the controller from my desktop PC, and I used a different computer to update the router with the new controller IP. I haven't set up my Access Point yet, as I am focusing on establishing this new Management VLAN using the ER605 Router and SG2008P switch for simplicity.
I've followed this multiple times with no success: https://www.tp-link.com/us/support/faq/2814/
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
It's painful but doable, the key part of the process being the following:
So you create a switch port profile which is native to the new VLAN management ID (PVID) and connect the controller
You've created a fixed IP reservation in the management subnet for the controller, and verified that the controller is active on that IP
The real magic comes when you are using the TPlink ODU utility..that's what allows you to move the gateway to the new VLAN/subnet.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Did you plug the controller into a switch port that was configured with the Management VLAN as the PVID (native VLAN)?
- Copy Link
- Report Inappropriate Content
and did you configure the LAN (first subnet defintion under Wired Connections) with the new VLAN id?
that should get pushed as part of the new config from the controller once the router can 'see' the controller thanks to the ODU.
You may wish to try factory defaulting the router, then using the ODU, then adopting.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I think you were being too logical :). There is one LAN setting that can only be edited and never deleted, to me that is the one that becomes the management VLAN. By default it comes up as 192.168.0.0/24 on VLAN1, but you can change that. I think the reason is that VLAN is always the native one on an Omada gateway's ports be default.
Not 100% sure on this, the docs are a bit sketchy in this area, but it has typically worked for me. (so think of it as Newtonian and not Einsteinian physics).
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@skeller Did this work for you in the end? Asking cause I have gone through this a few times and just like you the router never worked. I know the last step I never did but never realized that it could be changed.
- Copy Link
- Report Inappropriate Content
Hi @stevenchi
The router will keep using it's default LAN to communicate with the controller. On the controller if you want to put the router into "management VLAN", currently the only solution is to use the default "LAN” as your management VLAN.
And default "LAN" is untag, so you don't need to enable "management VLAN" on switches/APs, you can just use ACL to limit access from other VLANs.
stevenchi wrote
@skeller Did this work for you in the end? Asking cause I have gone through this a few times and just like you the router never worked. I know the last step I never did but never realized that it could be changed.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 1705
Replies: 10