Gateway (ER605) IP Address with Management VLAN
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
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.
Thank you for taking time to reply.
Our LAN is set to VLAN 99 (192.168.199.1/24) and we created MGMT VLAN 237 (10.0.237.1/24).
All of the hardware, except the ER605, was moved to the MGMT VLAN for IP addressing by following the guide: "How to configure Management VLAN in Omada SDN Controller (4.4.4 or above)" from this link "https://www.tp-link.com/us/support/faq/2814/". The last step in the process for the ER605 was to use the Omada Discovery Utility to inform the Omada gateway of the new IP address of the Omada Controller and this was successfully performed.
The devices page from the PC/software controller is below. The two SG2008 switches are connected to the ER605 and the PC/software controller is connected to one of the ports on an SG2008 which in configured in the MGMT VLAN and is therefore in 10.0.237.X subnet. The state of ER605 shows "CONNECTED" only when the PC/software controller has its wireless interface connected to the LAN VLAN which gives it a second IP address in the 192.168.199.X subnet. When the PC/software controller is connected solely to the 10.0.237.X subnet, the ER605 goes to "DISCONNECTED". Even though the ER605 goes to "DISCONNECTED" in Omada, we can still successfully ping the ER605 from the PC/software controller. Of course, once the ER605 is "DISCONNECTED" any configuration becomes a bit of a pain.....
From my limiited perspective, it would seem the fix would be to move the ER605's IP address into the MGMT VLAN so it gets a 10.0.237.X address. In theory the ER605 has an IP in every configured VLAN, but we don't see where the VLAN Interface can be configured for the ER605.
Thanks very much for any input!
