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
- Copy Link
- Report Inappropriate Content
I'm in the same boat, my second one just failed after a brief power outage, switch was behind a surge protector. It lasted about 2.5 months. The one before that also lasted about 2.5 months.
Support basicaly just went the replacement route immediately, implying that whatever the issue is, is some sort of hardware problem that cant be remedied by software.
IDK If I can even get a refund from the distributor i bought it from at this point so I'm stuck in this cycle. Also the options for 2.5GBE are limited, especially with PoE+ support.
- Copy Link
- Report Inappropriate Content
This is absolutely not a "business-grade" product. I emailed TP-Link, not that I am expecting much, I'd at the very least appreciate if they could elaborate on what is happening and what they're planning to do to fix it. I bought their Wi-fi AP that is POE+ and 2.5G, I don't think they have another product that does all that in a 10 port switch. Does any one know of any cases where this is happening on the larger switches like the TL-SG3428XMP?
- Copy Link
- Report Inappropriate Content
Just RMA'd my second TL-SG3210XHP-M2. First one died December 7, 2021 so with Christmas break and global shipping delays we didn't get a replacement (under warranty) until January 31, 2020!
Second one failed last Friday afternoon (13/05/2020) so only three and a half months of service.
First I noticed one of our EAP660HDs had lost connectivity. I noticed the port it was connected to on the TL-SG3210XHP-M2 had POE power but no link lights. Testing the EAP in various scenarios and reseting to factory didn't bring the EAP back to life so I opened a support ticket with TP-Link for the EAP (that was on the 12/05/2020).
The next day the switch started spitting out the below messages on the serial console:
1/0/1, PHY FW RELOAD.
1/0/1, PHY RESET.
So I rebooted the switch in the hopes that I might clear the port state. On reboot all the 2.5GB ports failed!
I tried various tricks with firmware versions that other community members in this thread have tried but nothing will bring back the dead 2.5GB ports. The SFP+ Ports both function normally, BTW.
I got onto TP-Link Support again and they more or less RMA'd it immediately. Then (quite confusingly and somewhat unprofessionally in my mind) they swapped the open ticket for the EAP to cover the switch instead!
I've since had another EAP fail. Not sure if it was related to the dying switch ports but now I have to open another case with TP-Link support for the two dead EAPs.
The remaining two EAPs have been powered up with the power adaptors. I configured a TP-Link SG108E with VLAN trunks to handle the WiFi SSIDs and the Omada controller software picked up both the live units. At least we have some limited coverage while all the hardware is RMA'd! And I will give a little credit to TP-Link for making the Omada controller software resilient enough to pick up the live EAPs through a low end switch.
- Copy Link
- Report Inappropriate Content
@vGeek79 Surprisingly, TP-Link already responded to my email. However, they claim that firmware 1.0.6 resolves the issue. Hmm...
Doesn't make sense as I was using 1.0.6 for most of the time. Unless the previous firmware release set it on a path to failure and the firmware update can't fix it once the damage is done?
I'm assuming everyone that went through RMA had to update their switch to 1.0.6, it didn't arrive with this firmware?
- Copy Link
- Report Inappropriate Content
@Utmstgsn I had a total of 3 of these exchanged (all at the same time). The newly received switches have firmware version 1.0.6.
- Copy Link
- Report Inappropriate Content
Replying to myself here.
The two EAPs that I thought were faulty were actually OK once I connected them to a network with a DHCP server. I thought that EAP660HDs had a fallback address configured as 192.168.0.1 but I think it's actually at the other end of the subnet at 192.168.0.254. In any case I couldn't get onto the EAP until after I did a factory reset and got a DHCP assignment.
I finally got all my EAPs back in operation which is a great relief. All working through the TL-SG108E (with three SSIDs on three VLANs) and so much faster than our old WiFi setup.
Sadly, though one EAP has failed Adoption in Omada after a (Omada recommended) firmware upgrade. It just keeps failing the adoption with something like 'Failed to respond to adoption commands'... So now I'm back to three EAPs and will be calling support again!
- Copy Link
- Report Inappropriate Content
I got my replacement. A few things I noticed, although I don't know if they are things I just didn't notice before:
- The fans now run quieter. Pretty sure they ran almost full-blast.
- The link lights actually flicker now, pretty sure they were just stuck on before they failed entirely.
Anyway, so far so good. It came with 1.0.6 - hopefully that'll be the end of it.
To TP-Links credit, they processed the RMA quickly and Amazon sent me the replacement before I even had to send the broken one back - so I ended up getting it ahead of schedule.
- Copy Link
- Report Inappropriate Content
udp UNCONN 0 0 [::]:27001 [::]:* users:(("jsvc",pid=3442,fd=431))
udp UNCONN 0 0 [::]:29810 [::]:* users:(("jsvc",pid=3442,fd=456))
tcp LISTEN 0 128 127.0.0.1:27017 *:* users:(("mongod",pid=2095,fd=11))
tcp LISTEN 0 128 127.0.0.1:27217 *:* users:(("mongod",pid=3485,fd=11))
tcp LISTEN 0 100 [::]:8843 [::]:* users:(("jsvc",pid=3442,fd=363))
tcp LISTEN 0 100 [::]:8043 [::]:* users:(("jsvc",pid=3442,fd=362))
tcp LISTEN 0 128 [::]:29811 [::]:* users:(("jsvc",pid=3442,fd=512))
tcp LISTEN 0 128 [::]:29812 [::]:* users:(("jsvc",pid=3442,fd=484))
tcp LISTEN 0 128 [::]:29813 [::]:* users:(("jsvc",pid=3442,fd=540))
tcp LISTEN 0 128 [::]:29814 [::]:* users:(("jsvc",pid=3442,fd=568))
tcp LISTEN 0 100 [::]:8088 [::]:* users:(("jsvc",pid=3442,fd=365))
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 14742
Replies: 80