Unable to adopt from anything but vlan1
I can get the controller on VLAN 2 to see the devices interfaces on VLAN 1 by plugging the controller IP into the switches. The adoption process fails due to communication timeouts, I assume the switches are trying to report home to an IP address and being routed correctly there, and then the adoption process is trying to communicate with the controller as if it were on vlan 1
If I delete the VLAN one interface from the switch in standalone mode so that the only interface that is left is VLAN 2, the controller on VLAN 2 cannot see it. If I make it all samesies in terms of interface and VLANs it doesn't work, except if everything is the same and on VLAN I.
Using the discovery tool has the exact same results. The adoption process starts and times out
It appears the controller has to live on VLAN 1 to adopt devices, and I have not been able to find anywhere to set the management VLAN ID in the switches in standalone mode.
Any way to do this without hopping my controller between vlan 1 and vlan 2 every time i buy an omada tplink device?
Hi @Challpesa
Thanks for posting in our business forum.
There is no management VLAN in standalone mode.
Either follow this guide step by step:
Or try this article:
But, I think you might need to follow the first one and follow the steps. It is clearly written that you should be doing the port config prior to the discovery utility.
Before you figure out the key steps, try something new.
This is not helpful as the second step is go to devices and click switch A
These guides are about how to remotely push management VLAN changes to edge devices from the controller. The problem is I can't even adopt them without using vlan 1/untagged
I can't remotely configure things I can't adopt.
Hi @Challpesa
Thanks for posting in our business forum.
Challpesa wrote
This is not helpful as the second step is go to devices and click switch A
These guides are about how to remotely push management VLAN changes to edge devices from the controller. The problem is I can't even adopt them without using vlan 1/untagged
I can't remotely configure things I can't adopt.
Diagram and your current setup. With the IP marked up.