SG3210X-M2 - After Firmware-Update to 1.0.5 (and Reboot), Switch is Disconnected
Hello,
today was the Firmware-Update-Day in my Omada-Network. For my SG3210X-M2 V1 Switch was the newest Firmware-Version 1.0.5 (previous Firmware was 1.0.3). The Firmware-Update Start was proceeded by me. After 5 Minutes the State on Omada-Hardware-Controller (OC200) was furthermore on "Upgrading". I received the Firmware-Upgrade-Failure-Message. Next step was the manual reboot of the Switch and the Device running great.
The SG3210X-M2 itself is connected via LAN-cable with the SG3218XP-M2 V1, which is my Main-Switch. In the Device list on Omada Controller the SG3210X-M2 is displayed with disconnected. The only Workaround is to unplug the LAN-Cable to the SG3210X-M2 und reinsert the LAN-cable. Then the SG3210X-M2 will be readopted.
Best regards
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
NeoMorpheus wrote
Yes, the OC200-Hardware-Controller and all the other Omada-Hardware are in the same subnet. The SG3210X-M2 has the correct configuration and working absolute fine. But the Omada-Controller shows the Switch as Disconnected after every Switch-reboot.
Every time it reboots, it will switch to "Disconnected" status.
Did you verify its static IP and web interface is accessible after the reboot while they are still in the "same subnet"? Screenshot?
Controller version?
If possible, Wireshark, remember to do the mirroring and see how the traffic goes on the uplink port to the controller.
BTW, set the correct model number and firmware in the post. Or the case cannot be properly reported.
Update:
Just got an email, we have noticed that there is an issue with the new release.
Please reset your switch, and revert it back to the previous firmware. We will address the issue soon before a new release.
- Copy Link
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
If it fails to get an IP, it displays as disconnected.
Reboot or replug the cable would fix it.
- Copy Link
- Report Inappropriate Content
The SG3210X-M.2 is configurated with a static IPv4-Address. On every reboot the Switch will be displayed with disconnected anyway. With Firmware-Version 1.0.3 this issue was not happen.
- Copy Link
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
NeoMorpheus wrote
The SG3210X-M.2 is configurated with a static IPv4-Address. On every reboot the Switch will be displayed with disconnected anyway. With Firmware-Version 1.0.3 this issue was not happen.
The controller is in the same subnet?
But if did not adopt it, the config does not sync to the switch. It might not properly work before being adopted and synced.
As you said it is on a static IP, you can still log in to it via CLI and recover the backup and see if it can work.
- Copy Link
- Report Inappropriate Content
Yes, the OC200-Hardware-Controller and all the other Omada-Hardware are in the same subnet. The SG3210X-M2 has the correct configuration and working absolute fine. But the Omada-Controller shows the Switch as Disconnected after every Switch-reboot.
- Copy Link
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
NeoMorpheus wrote
Yes, the OC200-Hardware-Controller and all the other Omada-Hardware are in the same subnet. The SG3210X-M2 has the correct configuration and working absolute fine. But the Omada-Controller shows the Switch as Disconnected after every Switch-reboot.
Every time it reboots, it will switch to "Disconnected" status.
Did you verify its static IP and web interface is accessible after the reboot while they are still in the "same subnet"? Screenshot?
Controller version?
If possible, Wireshark, remember to do the mirroring and see how the traffic goes on the uplink port to the controller.
BTW, set the correct model number and firmware in the post. Or the case cannot be properly reported.
Update:
Just got an email, we have noticed that there is an issue with the new release.
Please reset your switch, and revert it back to the previous firmware. We will address the issue soon before a new release.
- Copy Link
- Report Inappropriate Content
Thank you for your reply and for the information that die issue will be addressed. :) The previous firmware was version 1.0.3, but on your website is only version 1.0.2 available.
- Copy Link
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
NeoMorpheus wrote
Thank you for your reply and for the information that die issue will be addressed. :) The previous firmware was version 1.0.3, but on your website is only version 1.0.2 available.
Recommend the global site for a firmware check:
https://www.tp-link.com/en/support/download/sg3210x-m2/#Firmware
- Copy Link
- Report Inappropriate Content
Thank you very much! I have done a full-reset via USB-Serial-Connection (Omada-Controller couldn't resetting the switch after forget-command) and the Firmware 1.0.3 is now installed.
Is my SG3218XP-M2 V1 with Firmware 1.0.5 internally also affected by the issue?
- Copy Link
- Report Inappropriate Content
Hi @NeoMorpheus
Thanks for posting in our business forum.
NeoMorpheus wrote
Thank you very much! I have done a full-reset via USB-Serial-Connection (Omada-Controller couldn't resetting the switch after forget-command) and the Firmware 1.0.3 is now installed.
Is my SG3218XP-M2 V1 with Firmware 1.0.5 internally also affected by the issue?
If the firmware is adapting V5.14, it is affected. We have pulled them off.
- Copy Link
- Report Inappropriate Content
Ok, i have also resetted the SG3218XP-M2. Firmware 1.0.3 is now installed. Thank you for your help!
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 327
Replies: 10
Voters 0
No one has voted for it yet.