TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
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
I am having the same exact problem everyone here is describing with ports shutting down but still providing power, CPU usage spikes, and the log noting to reload firmware for those ports. I'm also running the latest firmware 1.0.6.
Is this confirmed to be a firmware bug and not a hardware issue?
@Fae any suggestions or info?
- Copy Link
- Report Inappropriate Content
I can confirm another case. All Ethernet ports are dead. I don't have an SFP adapter to try. Console works. Somehow both my primary and backup firmware is at 1.0.3 so I can't even switch. Hope there is some way to fix this.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I am experiencing the same problem. Power loss bricked 4 ports. Then the firmware upgrade bricked the whole box. Reverting to 1.0.0 fixed 4 ports. What's going on with these boxes?
- Copy Link
- Report Inappropriate Content
@vGeek79 Experiencing the same problem here. No matter which firmware version I use, the poe+ ports no longer connect (still provide power) and the sfp+ ports are working fine. I have a spare unit on hand and will check that out next.
Update: My 2nd switch on firmware 1.0.3 still seems to be running ok so far. Will move it to our client's location and hope it keeps working ok. Have contacted TP-Link Japan to request for the broken one to be replaced. Let's see where it goes.
Update (March 22, 2022): TP-Link Japan has requested that I send the switch to their service center for testing. If they can confirm the malfunction on their end, they will send me a new switch.
Update (March 25, 2022): TP-Link Japan will replace all 3 switches. Hopefully the new ones remain error free.
Update (April 15, 2022): Replacement switch arrived and has been up and running for 10 days so far without problems powering my OC-200 and 7 EAP660 HD. One thing I noticed is that it is noticeably quieter than the one I had installed previously. The fan properly spins down after boot as compared to the original which seemed to spin at full speed constantly.
- Copy Link
- Report Inappropriate Content
TP-link indicated it's a device failure and suggested a warranty claim. I now have a new switch with the same firmware version. It's working as expected without any of those errors. It does NOT sound like they expect the issue to be resolved solely with a future firmware update.
- Copy Link
- Report Inappropriate Content
@vGeek79 I have the same problem, twice. I RMA'd the original, got the new one working.
FWIW I was skeptical with the replacement as well, today we had a power outage and the port my Ubiquti Wifi6 was plugged into went down like how the original switch is.
Original switch was purchased less than a year ago. Would TP honor another RMA for an RMA they just replaced.
Like you all I see this spewing from the console. Prior to the power outage, I have this spit out as well. So I think any power off would have triggered this problem.
1/0/2, PHY FW RELOAD. 1/0/2, PHY RESET. 1/0/3, PHY FW RELOAD. 1/0/3, PHY RESET. 1/0/4, PHY FW RELOAD. 1/0/4, PHY RESET. #2006-01-01 08:09:48,[Monitor]/4/CPU RISING THRESHOLD: Total CPU Utilization is 90%.
- Copy Link
- Report Inappropriate Content
This is not 'damage'. I have now had two of these switches fail in exactly the same way, One died while still running 1.0.3, and the second one just died today running 1.06.
The switches last a few months and then die. I got the fan fault on the second one as well.
I'll contact support, but this is pretty awful reliability.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 14924
Replies: 80