Business Community > Switches > APs can adopt but not omada switch
< Switches

APs can adopt but not omada switch

APs can adopt but not omada switch

APs can adopt but not omada switch
APs can adopt but not omada switch
Sunday - last edited Monday
Tags: #VLAN & Multi-Networks #Configuration #Controller
Model: SG2008P  
Hardware Version: V1
Firmware Version: 1.0.13 Build 20250117 Rel.60471

Hi,


currently I am running 1 omada switch (TL-SG2008P, 192.168.5.201) and 2 omada APs (EAP610, 192.168.5.202-203) in standalone mode and I want to add them to an omada software controller. 
I can adopt my 2 Omada APs but somehow I cannot see the switch. I set them all up in static mode. On the APs I activated management vlan 5 and also Layer 3 Accessability. I couldn't find these options on the switch unfortunately.
I have a static interface entry in the switch with 192.168.5.201 and vlan 5, i deleted the vlan1 entry. Also set up a static routing with hostname and destination to 0.0.0.0 and next hop to my opnsense gateway at 192.168.5.1

My controller is installed on unraid as docker on IP 192.168.5.200 on the interface br0. It is bound to Port 8 on my omada switch which is untagged vlan5, PVID vlan 5.
I really don't know what the problem is now. There should be no firewall problems because it's all in the same subnet?! My APs get found immediately but not the switch. Is there a vlan problem? I tried also to activate via online controller via s/n and it worked with the switch but with the local controller it's not working.


p.s. more info: vlan1 is untagged on port 1-8

 

  0      
 
  0      
 
#1
Options
2 Accepted Solutions
Re:APs can adopt but not omada switch-Solution
Monday - last edited Monday

  @muffin44 

Thank you for your post.
First, please try to ping the Controller host IP directly from the switch.
Additionally, access the switch’s management interface and locate the following page; use the Inform URL to help the switch discover the Controller.

You can also try some other methods—see below:

How to discover Omada devices via Software Controller and Hardware Controller

Wishing you a joyful life and smooth internet! Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Recommended Solution
  0  
  0  
#4
Options
Re:APs can adopt but not omada switch-Solution
Monday - last edited Monday

  @muffin44 

ok I found the solution, I had to activate "Host access to custom networks" on Unraid Docker settings, I also resettet the switch in the meantime but I think that was not the solution... So go to the docker settings and activate this on unraid! 

Recommended Solution
  2  
  2  
#6
Options
5 Reply
Re:APs can adopt but not omada switch
Monday

  @muffin44 

 

Need to make sure the switch has that vlan set as its management vlan and has an interface on it

Main: ER8411 x1, SG3428X x1, SG3452 x1, SG2428LP x1, SG3210 x1, SG2218P x1, SG2008P x3, ES208G x1, EAP650 x6 Remote: ER7206 v2 x1, ER605 v2 x3, SG2008P x2, EAP650 x2, ES205G x1 Controller: OC300
  0  
  0  
#2
Options
Re:APs can adopt but not omada switch
Monday - last edited Monday

  @GRL 

I cannot find the management vlan settings on the switch. My interface setting is like this:

 

and

 

 

  0  
  0  
#3
Options
Re:APs can adopt but not omada switch-Solution
Monday - last edited Monday

  @muffin44 

Thank you for your post.
First, please try to ping the Controller host IP directly from the switch.
Additionally, access the switch’s management interface and locate the following page; use the Inform URL to help the switch discover the Controller.

You can also try some other methods—see below:

How to discover Omada devices via Software Controller and Hardware Controller

Wishing you a joyful life and smooth internet! Get the Latest Firmware Releases for Omada Routers Here - Subscribe for Updates
Recommended Solution
  0  
  0  
#4
Options
Re:APs can adopt but not omada switch
Monday

  @Ethan-TP 

This is really strange, I can ping from the standalone switch (192.168.5.201) the controller (192.168.5.200), my phone (192.168.5.10) but not my APs (192.168.5.202, 192.168.5.203).

And from the controller (192.168.5.200, where I adopted the 2 APs) I can ping both of the APs (192.168.5.202, 192.168.5.203) but not my standalone omada switch (192.168.5.201) and not my phone (192.168.5.10). 

Is there a VLAN problem? Like I said I configured my unraid at static 192.168.5.5 (br0) on Port 8 of the switch and made it untagged vlan5, PVID vlan5. On unraid I added at network settings vlan10 and 20, they have the interfaces br0.10 and br0.20. But I installed omada controller on br0 at 192.168.5.200

Why can my controller at 192.168.5.200 not see my phone? And funnily when I only had 1 AP added to controller I could not ping the other standalone AP...


To the thing with Controller Inform URL. I already added the IP of the controller, at the moment it says: 192.168.5.200?dPort=29810&mPort=0&omadacId=c21f969b (shortened the ID)

I think I first have to solve the problem with pinging from the controller to my phone or the standalone switch, I think there is some vlan mismatch?

  0  
  0  
#5
Options
Re:APs can adopt but not omada switch-Solution
Monday - last edited Monday

  @muffin44 

ok I found the solution, I had to activate "Host access to custom networks" on Unraid Docker settings, I also resettet the switch in the meantime but I think that was not the solution... So go to the docker settings and activate this on unraid! 

Recommended Solution
  2  
  2  
#6
Options

Information

Helpful: 0

Views: 407

Replies: 5

Tags

VLAN & Multi-Networks Configuration Controller
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.