@Babun-Sikder 

@Ethan-TP 

All of my switches that updated in the last few days via controller seem to have had that firmware version pulled from the controller, Ethan can you confirm and if we should roll back?

  @Babun-Sikder 

Thank you for your post. Please reconfirm that the issue you described occurs only on the SG2210P running firmware 5.20 and that no other switches managed by the Controller are affected. If possible, let us know roughly how many switches are impacted. Have you recently upgraded any other switch models? If so, do they exhibit the same behavior? After you restored connectivity by power-cycling, have you seen any further disconnections or instability?
The switch’s logging buffer and status-monitoring data are lost when power is removed; they are cleared on reboot, so no useful information can be retrieved afterward.If the problem can be reproduced reliably, please do not restart the switch when it occurs. Instead, access the CLI (via console or SSH) while the issue is present and collect the following commands for analysis:

- show logging buffer
- show running-config

Additionally, please observe the switch’s LED status during the outage. What state are the port LEDs and the SYS LED in when the switch goes offline?

  @Ethan-TP 

Dear TP-Link Omada Team,

Thank you for your prompt response. Please find my observations below:

1. Firmware Version & Affected Models:

   • The issue occurs on SG2210P switches running firmware v5.20.13 (currently in use).

   • No other switch models managed by the Controller (e.g., SG2428P) are affected.

2. Number of Switches Impacted:

   • All SG2210P switches across all sites where the firmware was applied are impacted.

   • Roughly X switches (replace X with the actual number) are experiencing this issue.

3. Other Switch Upgrades:

   • No other switch models were recently upgraded. Other switches continue to operate normally without any connectivity issues.

4. Post Power-Cycle Behavior:

   • After manually power-cycling the affected switch, connectivity is restored.

   • However, the disconnection issue recurs reliably whenever the switch is rebooted from the Omada Controller or after firmware application.

5. SSH / Ping / CLI Access:

   • During the outage, the switch becomes completely unreachable.

   • SSH and ping are not available until the switch is manually power-cycled.

6. Switch Logging and CLI Access:

   • I understand that logs are lost on power-cycling. I will reproduce the issue without restarting the switch and collect the following via CLI as requested:

     • show logging buffer

     • show running-config

7. LED Status During Outage:

   • During the outage, the SYS LED remains solid amber (or specify exact behavior).

   • The port LEDs of connected devices are flashing or off while the switch is offline.

Please let me know if you require the CLI output and LED behavior for multiple switches; I can collect and share them for analysis.

Looking forward to your guidance on resolving this firmware-related issue.