Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment

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

Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment
Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment
2021-02-28 22:17:39 - last edited 2021-03-05 18:50:50
Model: OC200  
Hardware Version: V1
Firmware Version: 4.2.11 (1.7.4 Build 20210118 Rel.72627)

Hello.  I am hoping that someone can help with an issue when integrating VLAN enabled TL-SG Easy Smart switches (TL-SG105E & TL-SG108E) with Omada SDN environment.

Overview:

I have an Omada SDN environment consisting of:

  • Two TL-SG2008P v1.0 switches (firmware 1.0.0 Build 20200608 Rel.76470)
  • TL-R605 v1.0 router (firmware 1.0.0 Build 20200930 Rel.36519, updated to 1.0.1)
  • Three (3) WAPs: EAP225-Outdoor(US) v1.0, EAP225(US) v3.0, EAP245(US) v3.0 (all on the latest firmware)
  • OC200 controller, running software v 4.2.8 4.2.11 (firmware 1.7.3 Build 20201119 Rel.63433, updated to 1.7.4)

 

Topology:

 I have the following interfaces configured, each with DHCP enabled:

  • Default (VLAN 1, 192.168.0.x)
  • PRIMARY (VLAN 10, 192.168.10.x)
  • IOT (VLAN 20, 192.168.20.x)
  • WORK( VLAN 30, 192.168.30.x)

Trunk ports, each set to profile “All”:  Port 8 of Switch A and Port 8 of Switch B (connected to LAN 1 and LAN2 of the TL-R605 respectively), Switch A Ports 1 (OC200), and Switch A Ports 2-4 (WAPs).  All other switch ports are assigned to “PRIMARY” .  The WAPs associate various SSIDs to corresponding VLANS.  In this configuration, all works well.

My Goal:  Add a number of TL-SG switches (ultimately one TL-SG108E 4.0, and two TL-SG105E 5.0) as VLAN-enabled “edge” switches to permit wired hosts to be assigned to VLANs other than “PRIMARY”.

For instance, configuring a TL-SG105E as:

PVIDs:  Port 1 = VLAN 1, Port 2 = VLAN 10, Port 3 – 5 = VLAN 20.

The Issue:

After connecting Port 1 of the TL-SG105E to a SDN-controlled TL-SG2008P (Port 5 of Switch A) and setting that port to profile “All”, strange things start to happen, most notably the “Uplink” assignment switches from the expected Port 8 to Port 5:

The controller thinks the TL-SG105E to be directly connected the router (it’s not):

None of the clients on the TL-SG105E seem to connect and the rest of the network gets unstable quick.  For instance, clients start to show up as directly connected to the TL-R605 and wireless clients appear as wired.

My questions:

  1. Am I missing something in my setup or making an error in configuring the VLANs on the OC200 or TL-SG?
  2. Is this behavior a result of a bug, possibly the one described here:  https://community.tp-link.com/en/business/forum/topic/246448?  (4.2.11 is not yet  available for the OC-200, so I can’t test if this is the case or not)

 

Happy to answer any clarifying questions about my setup. Thanks all!

  0      
  0      
#1
Options
4 Reply
Re:Issues integrating VLAN enabled TL-SG switches with Omada SDN environment
2021-03-02 20:12:55 - last edited 2021-03-03 15:47:47

An update for the benefit of anyone following:  I contacted support and they requested that I provide screenshots of VLAN configs

 

SDN VLAN config and Port Profile assgiments for the TL-SG2008P to which I'm attempting to connect a TL-SG105E (Port 5):

 

 

VLAN config for the TL-SG105E (Port 1 = Trunk):

 

 

Also of note:  Here is a copy of the log with frequent cycling after connecting the TL-SG105E.  When it thinks it is connected directly to the TL-605 ("Router") coinsides with the "uplink" port on Switch A moving erroniously from Port 8 to Port 5.

 

 

 

This "hopping" behavior is exhibited by the TL-SG105E switch when configured with VLANs.  It is always connected to Switch A Port 5, but the controller thinks it is jumping back and forth between the switch and direct connection to the router.  Also note that the VLAN assigned to the switch is seemingly random.

 

With one TL-SG configured and connected as I've outlined, I see the "hopping" behavior outlined above.  When I connect a second TL-SG, the entire network becomes unstable and I need to physically unplug one of the switches to successfully connect to the OC200 or any of the other network equipment.

  0  
  0  
#2
Options
Re:Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment
2021-03-04 21:15:55

I updated the OC200 controller to the latest version (4.2.11) and the R605 to the latest version (1.0.1).  Unfortunately I'm still seeing the same problems.

 

@Fae:  I've been in touch with support, but can you see that the broader development team is made aware of this issue and can work towards a solution.

  0  
  0  
#3
Options
Re:Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment
2021-03-05 01:58:17

Dear @TEDC,

 

I updated the OC200 controller to the latest version (4.2.11) and the R605 to the latest version (1.0.1).  Unfortunately I'm still seeing the same problems.

@Fae:  I've been in touch with support, but can you see that the broader development team is made aware of this issue and can work towards a solution.

 

Thank you for your valued feedback. This has been reported to the developer team who will do more investigation on the issue.

Happy New Year! Meet Us at CES 2023 | Featuring Wi-Fi 7, Omada Business Networking, VIGI Video Surveillance
  0  
  0  
#4
Options
Re:Issues integrating VLAN enabled TL-SG Easy Smart Switches with Omada SDN environment
2021-03-12 17:43:03

An update for the benefit of anyone experiecing similar issues:

 

I disabled VLAN 1 (and/or any other untagged VLAN intended to be the management VLAN) on the SG105E/108E completely.  This brought stability to the config, but is not ideal, as the IPs assigned to the switches are in the "user" network rather than the management LAN.  But  importantly, the uplink ports on the TL-SG2008P switches stay as they should.

 

The current issue I'm seeing is that several wired clients connected to the SG105E/108E switches do not appear in the client list.  The same problem as discussed here and here.  In addtion, I still see the issue I raised in this thread.

 

Also, Omada can't figure out what VLAN the SG105E/108E switches are connected to and hop constantly between VLANs.  Fortunately I can always reach them via their assigned static IPs.  This probably has to do with the fact that the Easy Smart switch management console is accessible via all VLANs - what I consider a bug, but TP-Link considers a "feature", discussed here.

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 1470

Replies: 4

Related Articles