Moving from standalone to OMADA controller (with management VLAN)
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I have a working EAP660 HD running in standalone mode. I have Installed a OMADA controller and want to start managing my EAP using it and unfortunately I'm facing some issues. Maybe you can help me.
The context:
- the (software) controller is connected to a (non TP-Link) switch which is connected to a (non TP-Link) router which is connected to the EAP
- the controller is connected to the switch through an access port which is tagged with management VLAN id
- the EAP is connected to the router through a trunk port, which carries VLANs required for the different SSIDs and the management VLAN
- "management VLAN" setting is activated on the EAP with the correct VLAN id
- the EAP gets an IP address from a DHCP server dedicated to management VLAN
- Layer 3 accessibility is activated on the EAP (so I can reach the management web page)
- the controller and the EAP are on the same (management) VLAN
- prior to "adoption" the controller sees the EAP (it's in the list of "pending" APs)
- prior to "adoption" the controller can ping the EAP
- As said above, the EAP is working perfectly in standalone mode.
What I'm experiencing:
When I click on "adopt" on the controller:
- the EAP status moves from "pending" to "configuring" then after a while to "disconnected".
- on the controller's logs there is only a single line stating that the EAP was disconnected
- The EAP is then unreachable using ping(nor web interface) be it from the controller, nor directly from the router or any device on the managment VLAN.
- On the DHCP servers, I see no lease for the EAP.
- On EAP side the blue led is turned on and blinks (off-on) once every now and then.
- On firewall logs I see nothing wrong
My guess is that "adopting" disables the management VLAN setting on the EAP and in turn the EAP cannot get an IP address from the DHCP server.
To have access to the EAP again, I have then to reset it, reconnect it to a non trunk port... already tried twice and lost lots of time.
I must be doing something wrong.
My request:
Can you please help ? How do I have to proceed to make it work (i.e. to make the EAP use the management VLAN once "adopted") ?
Thanks in advance
So, through a combination of laziness and lack of service windows and the HUGE PITA it is to climb up and reach my EAP225-outdoors to reset them (like when I bobbled the transition from Laptop controller to OC200), I have not yet enabled my mVLAN. However, it would seem to me that you could pre-configure the AP prior to adoption with a management VLAN (and all the other bits like SSID profiles) even if it's not plugged in. That way, when the initial Configuring push happens, it should also push the mVLAN and avoid isolating your AP.
Here's an AP that's in my spares box, it's already 'known' by the system, but definitely offline. I can adjust the Config settings prior to (re)deploying it.
