Hi @HomeAssistant_1 

Thanks for posting in our business forum.

HomeAssistant_1 wrote

  @Clive_A 

is the recommendation to downgrade from firmware 1.0.5 is valid for SG2210XMP-M2(UN) V1.0 as well?

 

The switch stopped authenticating with radius server after the update. 
 

thanks!

The firmware was pulled off from the release and authentication. So if you are on the pulled-off firmware, you are likely to be not able to upgrade it online.

Downgrading to the previous release and try the online upgrade again.

This is a generic solution to most firmware issues. You can try it out. From what I read, I have seen at least 2 cases successfully upgrading to the latest one withi this method.

Hi @NeoMorpheus 

Thanks for posting in our business forum.

NeoMorpheus wrote

Hello,

maybe i have identified the problem. The SG3210X-M2 is connected to the SG3218XP-M2 via Trunk. Untagged-VLAN is the Management-LAN-Subnet, just like the SG3218XP-M2, tagged VLAN is the Non-Mangement-LAN-Subnet. If the SG3210X-M2 is connected only with Management-Profile, a reboot runs without errors. But with the Trunk-Profile (Untagged and Tagged VLAN), this timeout-error occours.

 

I hope the devs can do something with it and fix it if necessary.

 

 

Best regards

When you adopt it back, if they are not in the same subnet, you are required to do something to adjust the VLAN to make them communicate.

This has been explained in the Management VLAN FAQ. I don't think this is something we can change.

If you need to discuss this further, please provide more details on your config.

Hi @NeoMorpheus 

Thanks for posting in our business forum.

NeoMorpheus wrote

  @Clive_A 

 

Thank you for your reply, Clive!

 

My VLAN-Settings are fine and the following:

 

Management-VLAN: ID 100

LAN-VLAN: ID 110

 

Omada-Hardware:

 

SG3218XP-M2 UN 1.0, Firmware 1.0.6
SG3210X-M2 UN 1.0, Firmware 1.0.6
OC200-Controller UN 1.0, Firmware 1.34.2 Build 20250110

 

 

The OC200-Controller is connected to Access-Port 3 on the SG3218XP-M2 with the Management-VLAN Switch-Profile only. The connection between the SG3218XP-M2 and SG3210X-M2 is realized on Port 15 respectively Port 1. The Switch-Profile on both Ports is configured with Management-VLAN as untagged and Native Network as well as LAN-VLAN as tagged. On both Switches only the Management-VLAN is aktivivated as VLAN-Interface in the Switch Config.

 

I don't think, my VLAN-Configuration is wrong.

I am not saying the that VLAN config would be wrong. I mean when after the firmware upgrade, the port profile has been changed or set to a default value.

That is not gonna be working until it is adopted by the controller. Certain functions may be stored in the RAM cache and it would be gone after a reboot. It gotta wait for the readoption to reimplement the VLAN profiles again so it would be back to working state.

That's my suspicion over what you found.

Hi @NeoMorpheus 

Thanks for posting in our business forum.

NeoMorpheus wrote

  @Clive_A 

 

But the only solution after firmware update AND/OR reboot is, to plug in the LAN cable again. After that, the SG3210X-M2 will be readopted. Otherwise, the Switch is displayed as disconnected.

That's helpful info for someone who faces the same issue. Thanks.

Currently, the solution is to skip this version, downgrade, and upgrade again.

As 1.0.5 has been pulled off you cannot upgrade to 1.0.6 if you are on 1.0.5.