Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc

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

Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 20:39:52 - last edited 2023-01-04 23:34:03
Tags: #Configuration #Adoption
Model: TL-SG2428P  
Hardware Version: V1
Firmware Version: 1.1.6

Omada adoption of this TL-SG2428P switch is a real issue...I've configured this switch with a Static IP so that it properly works on my LAN. I've also set up LACP LAG between this switch and my OPNsense router. I have to do this in the switch's local UI config or there's no other way to get it onto my network. Omada insists on resetting everything to 192.168.0.1 which is odd because normally only a router/gateway on the LAN would have that IP. I don't use that IP address scheme anyway.

 

When I attempt to adopt this Switch, Omada COMPLETELY wipes the conifg, sets the IP to 192.168.0.1, and breaks my entire network. It erases ALL of my EXTREMELY basic configuration, which only includes a LACP LAG group in order to communicate properly with my router, and date/time settings adjusted for my time zone. Adoption completely and miserably fails.

 

How am I supposed to adopt this Switch to Omada if it blows away the entire switch's configuration and sets the IP to 192.168.0.1, essentially cutting it off from my network as well as my Omada Software Controller which resides on local LAN??? This is a major issue that needs to be addressed asap.

 

Switch updated to latest firmware, running Omada software controller v5.7.4. I have 6 other devices already adopted into Omada, including a TL-SG2210P v5.0 PoE+ switch, and 4 EAP's (EAP670 and EAP610-Outdoor). Note that 2 of the EAP's are connected directly to this switch via wire and powered by PoE, 1000Mbps full duplex. 

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
  0      
  0      
#1
Options
1 Accepted Solution
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc-Solution
2023-01-04 22:38:43 - last edited 2023-01-04 23:34:03

Figured it out... To anyone else that runs into this issue...don't configure LAG LACP until the switch is fully adopted. Once I disabled LACP LAGG on the switch and router, the adoption FINALLY worked. What a hassle.

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
Recommended Solution
  2  
  2  
#6
Options
7 Reply
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 21:48:33 - last edited 2023-01-04 21:49:31

The only relevant post I've found so far seems to be this one: https://community.tp-link.com/en/business/forum/topic/583776

 

I had my SSH port set to a non-standard port when I tried to adopt this switch the first time around, when it kept getting reset to 192.168.0.1.

 

The question I have is this - is the switch configuration supposed to be carried into Omada during the adoption process? If the IP is reset or the LAG LACP config is lost I'll lose the connection to my router. I need someone to verify whether or not the switch's LOCAL UI configuration will be carried into Omada. I believe setting my SSH port to something other than port 22 might've caused this problem.

 

Am I on track here?

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
  0  
  0  
#2
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 22:11:16

That didn't work...Switch still reverting to 192.168.0.1 during the Omada adoption process...

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
  0  
  0  
#3
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 22:24:06

  @Shoresy 

 

Hi, as far as I know, there is no way you migrate the configuration of the switch to the controller as the management process is different. Everything you want to achieve should be configured in the controller, otherwise, the troubleshooting becomes very complex.

  0  
  0  
#4
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 22:25:25 - last edited 2023-01-04 22:31:16

  @RamtinR So how can the switch be configured within the controller if it's resetting the IP to 192.168.0.1? Why would the adoption place the switch on a network it can't communicate with? I'm fine with configuring in the Omada controller, but can't even get to that point if Omada cuts the switch off from the rest of the network? How do I ensure it gets adopted with an IP that can be accessed from my network?? The adoption into Omada doesn't even work because the switch gets cut off from the network before it can be adopted by the controller...this is a huge bug in my opinion. The switch's local LAN IP should NEVER be changed during the adoption process, or it would be impossible to adopt it. 

 

How was anyone able to get this switch adopted if they're on something other than a 192.168.0.x network?? I had zero issues getting a TL-SG2210P adopted properly into Omada, should be the same process for all these switches. 

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
  0  
  0  
#5
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc-Solution
2023-01-04 22:38:43 - last edited 2023-01-04 23:34:03

Figured it out... To anyone else that runs into this issue...don't configure LAG LACP until the switch is fully adopted. Once I disabled LACP LAGG on the switch and router, the adoption FINALLY worked. What a hassle.

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
Recommended Solution
  2  
  2  
#6
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 23:08:56

  @Shoresy 

 

Well, I assume that when you configured the LAG, you connected two cables from the router to the switch, then when you adopted it,the switch reset and you have a loop in your network. So the other way around is to disconnect the additional cables to avoid the loop, and after configuration in the controller, connect the extra cable again.

  1  
  1  
#7
Options
Re:Omada adoption of TL-SG2428P Switch completely broken, wreaks havoc
2023-01-04 23:14:06 - last edited 2023-01-04 23:19:33

The switch has loop prevention built-in, so loops probably weren't the issue. The OPNsense router, on the other hand, was configured to communicate via LACP LAG to the Switch over 3 ports, so I believe when the switch was resetting, communication between the router and the switch was gone, meaning the switch wasn't getting an IP or connection over the WAN (from the router), breaking the adoption process. The entire LAN interface (plus all VLAN's) go over the LAG group on the router, so LAN <-> WAN was breaking during the adoption process, because the switch config was being reset entirely. From my understanding, when LACP is enabled between two devices, it has to go through a LAG negotiation process or things won't work at all. Hopefully in the future *some* basic configs, such as IP and LAG, can be migrated during the adoption process. I hadn't configured anything on that switch beyond LACP LAG to the router.

 

I should've just connected the cables and waited to do the LACP LAG configuration in OPNsense until AFTER the adoption process had completed. Lesson learned.

Hybrid OPNsense/Omada EAP Cat6 backhaul 4 x EAP670 1 x EAP610-Outdoor Omada Controller v5.15.6.4 Win 11x64 Router: OPNsense Intel N5105 quad-core I226V 2.5Gbe w/16GB RAM Dual WAN Fios/Spectrum 1Gbps
  0  
  0  
#8
Options