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.

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.
80 Reply
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-17 15:10:56
Pretty much exactly what happened to mine as well minus the power outage. I picked these after having issues in the past with Ubiquity products and the consumer TP-Link products being pretty solid just lacking some features. This device is a real disappointment. They have a smaller 10G switch coming out that I was going to pick up but now Im second guessing that. My plan was to run 10G fiber to it from this one but if this one will continue to be an issue that would be pretty pointless.
  0  
  0  
#42
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-17 17:00:04

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. 

  1  
  1  
#43
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-17 23:16:52

  @vGeek79

 

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?

  0  
  0  
#44
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-17 23:52:55

  @vGeek79 

 

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.

  0  
  0  
#45
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-18 06:55:01

  @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?

  0  
  0  
#46
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-18 07:00:20

  @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.

  1  
  1  
#47
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-19 22:21:55

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!

  0  
  0  
#48
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-22 04:20:06

  @yzenezy 

 

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. 

  0  
  0  
#49
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-23 05:54:32
We are running Omanda SDN Controller Software v5.3.1 on CentOS Linux release 7.9.2009 (Core).
 
Upgrading to Firmware 1.1.0 or 1.1.1 will cause issues if you don't open up port 29814 on the Omada SDN Controller Software host!
 
TP-Link support have helped resolve this but the Release Notes and Upgrade documentation don't indicate any changes in listening ports for the Controller Software!
 
I had issues with EAP adoption after upgrading the EAP Firmware to 1.1.0 and also 1.1.1.
 
So I turned off the firewall and  monitored the wired connection during the Firmware upgrade. I noticed that the EAP was using port 29814 to communicate with the Omada SDN Controller Software during adoption. This must be a new port number for the latest SDN Controller Software (v5.3.1) and was hence not open on the firewall.
 
I had originally configure the Controller host's firewall for version 4.2.11. We recently upgraded to v5.3.1 via the following path v4.2.11 -> v5.1.7 -> v5.3.1. I checked the Release Notes and followed the upgrade reference: https://www.tp-link.com/au/omada-sdn/controller-upgrade/ which does not have any steps to indicate the firewall ports are different or to adjust the firewall during upgrade.
 
These references are available, however:
 
 
The above two references are helpful; and confusing at the same time.
 
Both list the mongo db ports (27017 and 27217) for the firewall but these ports are running on the local loopback address (127.0.0.1) on Linux and shouldn't be opened on the firewall. I've asked TP-Link for clarification as I don't think those ports need to be opened on the firewall.
 
Here are the listening ports on our Linux server that runs the Omada Controller SDN Software:
 
# ss -tulnp | grep -e jsvc -e mongo
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))
 
  0  
  0  
#50
Options
Re:TL-SG3210XHP-M2 - [Port]/6/Reload port Tw1/0/x phy firmware.
2022-05-29 15:56:12

  @KrisG Are the new switches still hw version v1 or higher

KrisG wrote

  @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.

 

  0  
  0  
#51
Options