TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I'm a new owner of a TL-SG3210XHP-M2 for about a month now, all looked good until today the switch had to be fully powered off and back on, upon powering back up, my sfp+ ports came back on but none of my POE+ ports, that was on FW 1.0.3, tried to unplug/replugged/change ports, force interface up by CLI or GUI... to no avail...Link was always down. All seemed to be working in the last few days, but don't think I tried to fully unplugged the switch and back on, on reboot by CLI or GUI.
My OC200 and AP's are still getting POE+ power but no link on FW 1.0.3.
On FW 1.0.3 after restoring power to the switch
#show interface status
Port Status Speed Duplex FlowCtrl Active-Medium
---- ------ ----- ------ -------- -------------
Tw1/0/1 LinkDown N/A N/A N/A Copper ------> OC200
Tw1/0/2 LinkDown N/A N/A N/A Copper ------> AP1
Tw1/0/3 LinkDown N/A N/A N/A Copper ------> AP2
Tw1/0/4 LinkDown N/A N/A N/A Copper ------> PC for testing
Tw1/0/5 LinkDown N/A N/A N/A Copper
Tw1/0/6 LinkDown N/A N/A N/A Copper
Tw1/0/7 LinkDown N/A N/A N/A Copper
Tw1/0/8 LinkDown N/A N/A N/A Copper
Te1/0/9 LinkUp 10G Full Disable Fiber
Te1/0/10 LinkUp 10G Full Disable Fiber
Only thing that seemed to work was to restore FW 1.0.2, weird?
System Description - JetStream 8-Port 2.5GBASE-T and 2-Port 10GE SFP+ L2+ Managed Switch with 8-Port PoE+
Hardware Version - TL-SG3210XHP-M2 1.0
Software Version - 1.0.2 Build 20210201 Rel.60966
Bootloader Version - TP-LINK BOOTUTIL(v1.0.0)
TL-SG3210XHP-M2#show image-info
Image Info:
Current Startup Image - Exist & OK
Image Name - image1.bin
Flash Version - 1.3.0
Software Version - 1.0.2
Next Startup Image - Exist & OK
Image Name - image1.bin
Flash Version - 1.3.0
Software Version - 1.0.2
Backup Image - Exist & OK
Image Name - image2.bin
Flash Version - 1.3.0
Software Version - 1.0.3
POE+ works on FW 1.0.2 but getting these logs repeatably, ports 6 to 8 have nothing plugged in.
I've opened a SR with TP-Link, awaiting a response.
show logging buffer
#2021-12-06 20:30:22,[Port]/6/Reload port Tw1/0/6 phy firmware.
#2021-12-06 20:30:08,[Port]/6/Reload port Tw1/0/8 phy firmware.
#2021-12-06 20:29:54,[Port]/6/Reload port Tw1/0/7 phy firmware.
#2021-12-06 20:29:40,[Port]/6/Reload port Tw1/0/6 phy firmware.
#2006-01-01 08:03:21,[Port]/6/Reload port Tw1/0/7 phy firmware.
#2006-01-01 08:03:08,[Port]/6/Reload port Tw1/0/6 phy firmware.
#2006-01-01 08:02:57,[Port]/6/Reload port Tw1/0/5 phy firmware.
#2006-01-01 08:02:49,[Link]/5/Tw1/0/4 changed state to up.
#2006-01-01 08:02:46,[Port]/6/Reload port Tw1/0/4 phy firmware.
#2006-01-01 08:02:40,[Link]/5/Tw1/0/3 changed state to up.
#2006-01-01 08:02:35,[Port]/6/Reload port Tw1/0/3 phy firmware.
#2006-01-01 08:02:29,[Link]/5/Tw1/0/2 changed state to up.
#2006-01-01 08:02:24,[Port]/6/Reload port Tw1/0/2 phy firmware.
#2006-01-01 08:02:15,[Link]/5/Tw1/0/1 changed state to up.
#2006-01-01 08:02:13,[Port]/6/Reload port Tw1/0/1 phy firmware.
#2006-01-01 08:01:58,[Port]/6/Reload port Tw1/0/8 phy firmware.
#2006-01-01 08:01:45,[Port]/6/Reload port Tw1/0/7 phy firmware.
#2006-01-01 08:01:32,[Port]/6/Reload port Tw1/0/6 phy firmware.
#2006-01-01 08:01:05,[Port]/6/Reload port Tw1/0/8 phy firmware.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Received my 2nd replacement today and it is also v1.0 and came with Firmware Version: 1.0.6 Build 20211202 Rel.66032
- Copy Link
- Report Inappropriate Content
How is everyone doing with these? Just had a unit with port 1 and 3 not work, power cycled and now no ports work (POE but no data). Well, sometimes port 8 works, go figure.
The unit in question is a V1.6, tried every type of downgrade and upgrade (even to the V2 firmware, which I promptly downgraded from). Nothing works.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Have a 2.6 model now, hoping that one stays stable.
Still have a 1.6 in the basement I expect to fail one day on a power cycle.
- Copy Link
- Report Inappropriate Content
Maybe a bit late to the discussion ...
One of these switches in operation since may 2022.
After power outage behind an older UPS in september 2022, nearly every port was malfunctioning.
It took a while to convince my supplier that it was not a configuration issue, got a replacement unit.
New unit was placed behind a new UPS. Unfortunately, while being away for some days around New Year, a new power event took place, and completely drained the UPS, resulting in TL's power being cut off at the end. Took several hours to figure out what was wrong, but in the end it was clear several ports were malfunctioning again.
Some ports would provide POE, but no network. Other ports would not work at all. Indicator lights were - similar to the first time - not reflecting actual situation !
Of course I can get a replacement, but I'm really starting to think going TP-Link - advised by the vendor - was a bad decision.
Unfortunately also invested in a sizeable amount of AP's, OC300, etc , so there's three (& halve) options :
1) sell everything and move to different brand
2) find a good alternative switch from TP-Link
3) a non-POE switch from TP-Link + POE injectors (not very elegant in my opinion)
3.5) a non-TP-link switch , forgoing Omada and moving to generic snmp control software
Solution 2 would "cause the lease pain", but can't see any real TP-Link alternative at the moment : a (not-so-delicate) POE+(+) switch with 2,5gbps or higher ethernet ports ... :(
Any suggestions for al alternative TP-Link switch ?
(or advise on other solutions ...)
- Copy Link
- Report Inappropriate Content
@IctEss What version switch? I have one V1.6 still and expecting it to break one day, but have a V2.6 and hoping that doesn't ever have this issue. Maybe once we get these all cycled out to V2.6+ we will all forget about this? MAYBE...
- Copy Link
- Report Inappropriate Content
@IctEss My first TL-SG3210XHP-M2 on fw version. 1.6 hours 1.0 worked until the end of December 2022, between Christmas and the new year it was damaged.. just like a few other people.. I am not a supporter of conspiracy theories, but ... a new device returned to me around May 2023 but in the old version 1.0. This time, just in case, I cut all traffic between the controller and the Omada cloud, leaving only local service (I use a VPN). Christmas has passed, and the new year (the period when the first device stopped working). It's January - it's working for now. But in the meantime, after 3-4 months of operation, I sent back two other small unmanaged 5-port 2.5G TL-SG105-M2 for warranty ... could it be a problem with the chipset that supports these 2.5G ports? Any faulty batch since it affects devices with 2.5G ports? Regarding the question of an alternative, there is not much of it - I used a Zyxel 8x1G + 2x2.5G + 2xSFP+ switch for the time of the TL-SG3210XHP-M2 failure.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 11808
Replies: 80
Voters 1
