Business Community > Switches > SG2210P V5.0 not detected at all by omada controller 5.0.9
< Switches

SG2210P V5.0 not detected at all by omada controller 5.0.9

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
123

SG2210P V5.0 not detected at all by omada controller 5.0.9

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
SG2210P V5.0 not detected at all by omada controller 5.0.9
SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-02 14:23:42 - last edited 2023-12-21 16:10:10
Tags: #Configuration #Omada Controller
Model: SG2210P  
Hardware Version: V5
Firmware Version: 5.0.6 Build 20230602 Rel.73473

Hi,

 

I am using SG2210P V5. The interface configuration on switch looks like this

 

 

Omada controller is at 10.0.99.16. This switch's IP address is 10.0.99.11. They are both in the same layer 2 network and I can reach it from the omada controller without any problems.

 

 

The problem is, Omada controller fails to find it on the devices list. I tried the omada discover utility and it also can not find the switch. Both of these, The controller and the discover utility see my other switch SG2210MP v1that's also in the same L2 network.

 

I have tried resetting SG2210P in the past and it has not helped at all, I still can not adopt it.

 

Please let me know how to debug this ?

 

  0      
 
  0      
 
#1
Options
24 Reply
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-02 18:06:13

I found this post https://community.tp-link.com/en/business/forum/topic/591272

 

and no answers.

 

 

  0  
  0  
#2
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-02 18:20:36

Every thing here is just so confusing.

 

Omada controller can't find this one switch even though there is literally no reason for the switch to not be able to talk to the controller.

 

Another option is using omad cloud controller and adding with serial number but there is no UI for adding devices with serial numbers any more! I followed this, https://www.tp-link.com/baltic/support/faq/3387/

 

Then, There is the option to add with inform urls and there is no inform url in that section anymore

 

 

 

  0  
  0  
#3
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-03 02:29:18

Hi @ishanjain28 

Thanks for posting in our business forum.

First, I think you need to get this straight. Understand how the device works and think where could be wrong: Which ports do Omada Controller and EAP Discovery Utility use?

The device is actively broadcasting the discover packet. Not the controller. Then have you considered that there is a problem with your setup? Is the device to controller pingable to one another?

 

On the switch, you can input the inform URL on the switch admin web to let the switch talk to the controller directly. Try that one.

You posted a link FAQ3387. It is only available for Cloud-based Controller(annual paid service). If you carefully check your controller type, you are not using that.

Since you have configured VLAN, I cannot rule out that you misconfig something. But try the ping which is helpful to verify if the access is through.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#4
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-03 06:32:32 - last edited 2023-08-03 06:33:41

1. Omada controller is at 10.0.99.16 and the switch is at 10.0.99.11. I can reach the switch from omada controller and I can reach the omada controller from the switch. There is no connectivity problem here. The omada controller is listening on the discovery/connection ports and I can reach these ports from the switch.

 

jsvc 203 0 434u IPv4 184310429 0t0 UDP *:27001

jsvc 203 0 459u IPv4 184307091 0t0 UDP *:29810

jsvc 203 0 487u IPv4 184307092 0t0 TCP *:29812 (LISTEN)

jsvc 203 0 515u IPv4 184307093 0t0 TCP *:29811 (LISTEN)

jsvc 203 0 543u IPv4 184307094 0t0 TCP *:29813 (LISTEN)

jsvc 203 0 571u IPv4 184307095 0t0 TCP *:29814 (LISTEN)

jsvc 203 0 599u IPv4 184313633 0t0 TCP *:29815 (LISTEN)

jsvc 203 0 627u IPv4 184310434 0t0 TCP *:29816 (LISTEN)

 

 In packet captures, I do not see any broadcast/discovery related packets from the switch.

  0  
  0  
#5
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-04 09:36:33

  @ishanjain28 

If you put the inform URL, does it find the controller? Strange. How do you wireshark it? Specify your steps.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#6
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-05 06:52:57
If you put the inform URL, does it find the controller? No, It does not find the controller. I added the url 10.0.99.16 and it changed the url to include a dPort field and a key. It still did not connect to the omada controller. How do you wireshark it? Specify your steps. On my router, I enabled packet capture for all traffic on the ethernet interface the switch is connected to. I do not see any broadcast traffic or any sign it's even trying to talk to the controller.
  0  
  0  
#7
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-05 07:19:35

One of my other switches is SG2210MP v1.0 running firmware version 1.3

 

This was detected in omada controller and I adopted it. Then I found this issue https://community.tp-link.com/en/business/forum/topic/585454 and I removed the switch from the controller and set it up again.

 

Now, I want to add that switch again in omada controller but omada controller can not find this switch either! Omada controller can not find it and I don't see it in the omada discover utility.

 

 

I do see the omada controller with an arp scan on the switch and I can ping omada controller from the switch so there is no issue at layer 2 or layer 3.

 

10.0.99.7 is this switch and the omada controller is running at 10.0.99.11

 

  0  
  0  
#8
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-07 09:37:10

  @ishanjain28 

i don't wanna argue and don't wanna agree with what was said in your pasted link. 

so what's the point in removing the native vlan or default vlan? leaving a port completely unfunctional is your goal? obliterate it from osi layer 2 is a wise idea? in what kind of scenario do you need that?

 

when you say that they cannot find each other, that's most absurd thing I ever see. how do you make it happen?

if you just set up 802.1q vlan, that should not be like that. 

do you have the backup? export it here.

wireshark result, and how did you do that? 

 

i cannot believe what's happening here. how do you disable switch broadcast? 

ScReW yOu gUyS. I aM GOinG hoMe. —————————————————————— For heaven's sake, can you write and describe your issue based on plain fact, common logic and a methodologic approach? Appreciate it.
  0  
  0  
#9
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-07 17:05:30

The config from both switches is

 

 

SG2210MP

!TL-SG2210MP
#
vlan 10
 name "sjhome"
#
vlan 20
 name ""
#
vlan 30
 name ""
#
vlan 40
 name ""
#
vlan 50
 name "lab"
#
vlan 60
 name "guest"
#
vlan 70
 name "lab no internet"
#
vlan 99
 name "mgmt"
#
vlan 140
 name "wan1"
#
vlan 150
 name "wan2"
#
vlan 160
 name "wan3"
#
#
#
#
#
#
#
#
#
#
#
#
#
#
hostname "sw1"
ip management-vlan 99
#
#
system-time ntp UTC+05:30 133.100.9.2 139.78.100.163 12
no system-time dst
#
#
#
user name admin privilege admin secret 5 $1$H5A3G8K3J<M2O7O<H4K=I:C8H1L2I<O7*(.({
telnet disable
no service reset-disable
#
#
#
#
#
ip http secure-ciphersuite ecdhe-a128-g-s256 ecdhe-a256-g-s384  
ip ssh server  
no ip ssh algorithm Cast128-CBC
no ip ssh algorithm 3DES-CBC
#
#
snmp-server
#
#
lldp
lldp timer tx-interval 5
#
#
power inline consumption 150.0
#
 
#
#
#
#
#
#
#
no controller cloud-based
interface vlan 99
  ip address-alloc dhcp
  no ipv6 enable
#
interface gigabitEthernet 1/0/1
  description ""
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport acceptable frame tagged
  switchport pvid 99
   
#
interface gigabitEthernet 1/0/2
  description ""
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport acceptable frame tagged
  switchport pvid 99
   
#
interface gigabitEthernet 1/0/3
  description ""
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
#
interface gigabitEthernet 1/0/4
  description "Empty"
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
#
interface gigabitEthernet 1/0/5
  description "2f AP"
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport acceptable frame tagged
  switchport pvid 99
   
#
interface gigabitEthernet 1/0/6
  description "Camera1"
  switchport general allowed vlan 70 untagged
  switchport pvid 70
   
#
interface gigabitEthernet 1/0/7
  description "Camera2"
  switchport general allowed vlan 70 untagged
  switchport pvid 70
   
#
interface gigabitEthernet 1/0/8
  description "Camera3"
  switchport general allowed vlan 70 untagged
  switchport pvid 70
   
#
interface gigabitEthernet 1/0/9
   
#
interface gigabitEthernet 1/0/10
   
#
end

 

 

SG2210P

!TL-SG2210P
#
vlan 10
 name ""
#
vlan 20
 name ""
#
vlan 30
 name ""
#
vlan 40
 name ""
#
vlan 50
 name "lab"
#
vlan 60
 name "guest"
#
vlan 70
 name "lab-no-internet"
#
vlan 99
 name "mgmt"
#
vlan 140
#
vlan 150
 name "wan1 only"
#
vlan 160
 name "wan2 only"
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
hostname "sw2"
location "India"
#
logging host index 1 10.0.99.13 6
#
system-time ntp UTC+05:30 133.100.9.2 139.78.100.163 12     
no system-time dst
#
sdm prefer enterpriseV6
#
jumbo-size 9214
#
vlan_trunk
#
#
user name admin privilege admin secret 5 $1$H5A3G8K3J<M2O7O<H4K=I:C8H1L2I<O7*(.({
telnet disable
no service reset-disable
#
#
#
#
#
#
#
#
ip ssh server  
no ip ssh version v1
#
#
spanning-tree mode rstp
#
no snmp-server
#
#
lldp
#
ipv6 routing
#
#
power inline consumption 61.0
#
#
 
#
#
#
#
#
#
#
#
no controller cloud-based
no controller cloud-based privacy-policy
interface vlan 99
  ip address-alloc dhcp
  ipv6 enable
#
interface gigabitEthernet 1/0/1
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/2
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/3
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/4
  switchport general allowed vlan 10,20,30,40,50,60,70,99,140,150 tagged
  switchport general allowed vlan 160 tagged
  switchport pvid 99
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/5
  switchport general allowed vlan 99 untagged
  switchport pvid 99
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/6
  switchport general allowed vlan 140 untagged
  switchport general allowed vlan 150,160 tagged
  switchport pvid 140
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/7
  switchport general allowed vlan 10 untagged
  switchport pvid 10
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/8
  switchport general allowed vlan 70 untagged
  switchport pvid 70
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/9
   
  no ip igmp snooping
#
interface gigabitEthernet 1/0/10
   
  no ip igmp snooping
#
ip igmp snooping vlan-config 1
ip igmp snooping vlan-config 1 immediate-leave
ip igmp snooping vlan-config 1 rtime 300
ip igmp snooping vlan-config 1 mtime 260
ip igmp snooping vlan-config 1 ltime 1
end

 

 

 

Omada controller is running in proxmox in the same VLAN(vlan 99) as the switches and access points.

Omada controller can see the switches and reach them without any problems.

 

root@omada:~# arp-scan 10.0.99.0/24
Interface: eth0, type: EN10MB, MAC: 72:bc:48:bd:7f:cc, IPv4: 10.0.99.16
Starting arp-scan 1.9.7 with 256 hosts (https://github.com/royhills/arp-scan)
10.0.99.1    c4:ad:34:9a:95:75    Routerboard.com
10.0.99.2    60:a4:b7:47:8e:94    (Unknown)
10.0.99.11    b4:b0:24:98:0c:fa    (Unknown)
10.0.99.7    00:31:92:76:47:39    (Unknown)

 

 

root@omada:~# ping 10.0.99.7
PING 10.0.99.7 (10.0.99.7) 56(84) bytes of data.
64 bytes from 10.0.99.7: icmp_seq=1 ttl=64 time=2.88 ms
^C
--- 10.0.99.7 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.877/2.877/2.877/0.000 ms
root@omada:~# ping 10.0.99.11
PING 10.0.99.11 (10.0.99.11) 56(84) bytes of data.
64 bytes from 10.0.99.11: icmp_seq=1 ttl=64 time=2.03 ms
^C
--- 10.0.99.11 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 2.028/2.028/2.028/0.000 ms
root@omada:~# curl 10.0.99.7 --head > /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
root@omada:~# curl 10.0.99.11 --head > /dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
root@omada:~#

 

 

I captured packets on the router on ether1(SG2210MP) and ether2(SG2210P) interfaces and I do not see any broadcast packets from the switches. I do see broadcast packets from the access point(EAP245).

 

 

 

 
  0  
  0  
#10
Options
Re:SG2210P V5.0 not detected at all by omada controller 5.0.9
2023-08-09 09:22:23 - last edited 2023-08-09 09:37:52

  @ishanjain28 

this is where you connect 

 

your router is on 

interface gigabitEthernet 1/0/1


EAP is on 
interface gigabitEthernet 1/0/2
 

then where is the VM?

 

from the switch, can you use diagnostics to ping the controller IP? work?

 

have you tried to modify 1/0/1 to be 99 untagged pvid 99?

 

 

ScReW yOu gUyS. I aM GOinG hoMe. —————————————————————— For heaven's sake, can you write and describe your issue based on plain fact, common logic and a methodologic approach? Appreciate it.
  0  
  0  
#11
Options
123

Information

Helpful: 0

Views: 2536

Replies: 24

Tags

Configuration
Omada Controller
Related Articles
 High CPU Usage on TL-SG2210P v5.0
552 0
updated SG2210P?
334 0
How to reset TL-SG2210P v5 for re-adoption by Omada Controller
2584 0
SG2210P LAG LACP ?
796 0
TL-SG2210P despite Omada turned off, calls home every few seconds.
790 1
TL-SG2210P + Omada not reporting PoE port status, cannot do PoE Recovery
629 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.