Business Community > All Threads > Omada S/W 5.7.4 Switch Drop Error
< All Threads

Omada S/W 5.7.4 Switch Drop Error

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

Omada S/W 5.7.4 Switch Drop Error

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Omada S/W 5.7.4 Switch Drop Error
Omada S/W 5.7.4 Switch Drop Error
2022-11-23 12:16:44 - last edited 2022-11-23 12:17:49
Model: Omada Software Controller (Linux)  
Hardware Version:
Firmware Version: 5.7.4

Hi. 

 

I have previously written the following thread. This issue was resolved by initializing the SG2210, but after the Omada 5.7.4 update a more fatal problem occurred.

(https://community.tp-link.com/en/business/forum/topic/587200?replyId=1146042)

 

After updating the Omada software to 5.7.4, the SG2210MP had the same drop behavior as before. It just looked like a drop and it actually worked fine.

Let's try to solve this problem like before I reset the SG2210 settings and as soon as I hooked up with Omada, all WAN/LAN ports of ER7206/SG2210MP went down.


I rebooted the Router/Switch to fix it, but the SG2210 Drop is the same.

Reinitialized as before.


But ER7206/SG2210MP down again and Drop problem persists.

Recently, I've been seeing unstable symptoms from the Omada version.
The switch community has solutions for such symptoms: SSH ON/OFF, port change, reboot SG2210MP, but this solution doesn't help.

 

Due to this problem, it is not possible to set SG2210 by Drop after initialization. It's too troublesome.

 

What's the problem?

 

--

I used google translator.
We ask for your understanding.

  1      
 
  1      
 
#1
Options
5 Reply
Re:Omada S/W 5.7.4 Switch Drop Error
2022-11-24 08:48:11

  @canopus 

 

canopus wrote

After updating the Omada software to 5.7.4, the SG2210MP had the same drop behavior as before. It just looked like a drop and it actually worked fine.

Reinitialized as before.

 

What is the exact phenomenon of the problem when the switch drops but works fine?

Does it mean that the switch shows Disconnected on the controller?

 

Does initialize mean hard reset switch or forget switch on controller?

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Omada S/W 5.7.4 Switch Drop Error
2022-11-24 08:51:44 - last edited 2022-11-24 08:52:39

  @처녀 자리 

 

That's right.

 

It appears as a Drop in the controller. No action is possible.
Initialization was reset through the Reset button on the switch.

 

And when the setting is finished again, the drop occurs again in the controller.

  0  
  0  
#3
Options
Re:Omada S/W 5.7.4 Switch Drop Error
2022-11-24 10:55:27

Dear @canopus ，

 

Thanks for your feedback about this issue in this community.

 

1. After upgrading the Controller to 5.7.4, does the switch shows Disconnected status after the ER7206 port is Down?
Only TL-SG2210MP's on the Controller will show Disconnected?

 

2. You mentioned in your previous post that the TL-SG2210MP would drop after you configured LACP.

Can you provide the relevant configuration including LACP?
Also, What's the physical connection(current topology) of your devices?

 

Best Regards！

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#4
Options
Re:Omada S/W 5.7.4 Switch Drop Error
2022-11-24 11:43:54

  @Hank21 

 

 

 

1. Yes. Only the SG2210MP appears to be disconnected from the controller.

 

2. The picture is the topology including LACP.
(By the way, LACP may not be the problem. It seemed to be a problem before LACP)

 

VLANs are composed of several.

 

The VLANs below can all communicate with each other.
(All are tagged VLANs)

 

VLAN1,VLAN10,VLAN100,VLAN1000
 - 192.168.10.0/24, 10.10.1.0/24, 10.1.1.0/24, 100.100.100.0/24

 

And ping from Omada SW Controller to SG2210MP fails.

 

 

  0  
  0  
#5
Options
Re:Omada S/W 5.7.4 Switch Drop Error
2022-11-30 08:25:04

Dear @canopus ，

 

Thanks for your reply.

 

Could you please tell us more details:

1. Is the Drop that occurred before you configured LACP recoverable, and if so, by what means (e.g. Reboot or Reset TL-SG2210MP)?


2. Is the Drop that occurred after you configured LACP recoverable, and if so, by what means?


3. After you configure LACP, the VM Host cannot ping the TL-SG2210MP, can you check if the VM Host side and the TL-SG2210MP side (via SSH) have learned the ARP address of the other side?
If the ARP is not learned, can you capture the packets to see if the ARP Request and Reply packets take which path (master or slave) of LACP?


4. Have you configured link aggregation for dual NICs on the VM Host side?
Is the same MAC and IP used for communication with the Switch after link aggregation of the dual NICs?
Is it possible to know the MAC address of VM Host, TL-SG2210MP in order to test whether it is related to the routing algorithm of LACP.

 

Best Regards！

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#6
Options

Information

Helpful: 1

Views: 786

Replies: 5

Related Articles
5.7.4 Auto Refresh
747 0
omada setup "general error"
1288 0
"log_limit_check doesn't exist" error on software controller 5.7.4
252 0
Optional field are required in Omada SDN 5.7.4
757 0
mDns Repeater not working on Controller Version 5.7.4 Linux
858 1
IP Group oddities in Software Controller 5.7.4 (bug?)
593 2
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.