Gateway (ER605) IP Address with Management VLAN
Our network has several VLANs and a management VLAN for all the Omada devices. We are using V5.1.7 of the software controller with two SG2008 switches and three EAPs. The management VLAN is working and the switches and EAPs have IP addresses in the management subnet. However, the gateway (ER605) still has an IP address on the main LAN, i.e. in a different subnet.
I have read / reviewed the following posts related to this question or how to setup the management VLAN:
https://www.tp-link.com/us/support/faq/2814/
https://community.tp-link.com/en/business/forum/topic/276582
https://community.tp-link.com/en/home/forum/topic/505062
We're running the software controller on an Intel NUC which has two network interfaces. The wired interface is on the management subnet. When we have only the wired interface connected (to the management subnet) we can ping the IP address of the ER605 which is on the LAN, however, the ER605 shows as Disconnected in Omada.
If we bring up the wireless interface of the NUC and connect it to the LAN, the adapter successfully acquires an IP address in the LAN subnet, and the ER605 then goes to a Connected state in Omada.
We have tried adding Switch ACLs to resolve this, but they do not. Given that we can ping the ER605 but it's disconnected we're not sure what to try next.
It would be preferred to have only the wired interface up and connected and be able to manage the network. Is there a way to put the ER605 on the management subnet? Or is there any recommended configuration to check so the ER605 stays in a Connected state with only the wired connection?
Thanks for your assistance.