@PROXYTEC 

So, the last reply in that post, you mentioned that you used 10G with a 3210XHP and it worked okay when the firmware is below 2.20.3.

That is to say:

(regardless of the firmware version) SG3210XHP-M2_10G SFP_SM5310-T------SM5310-T_10G SFP_3452XP HW v2.20 with FW 2.20.1 or (2.20.3 below firmware). 

Questions:

• This does not appear to experience any issue with the 10G link with the same module SM5310T. That's right?
• So, if you upgrade the firmware to 2.20.3 or later, same setup but simply change the firmware of the 3452XP, what's the result?
• Now you've changed to a new client, and its 10G NIC, RJ45 ETH, is connected to the 3452XP with the SM5310T, 10G port on the 3452XP is going up and down?
• What's the model and drive version of the NIC? 
• Cable length in this context is the same cable? For two different test results. CAT degree?
• Results of commands while it is "unstable": show ddm status and show fiber-port
• And you experience the up and down issue while there is zero traffic or load? 

I look forward to the answers to these questions. I recall I filed a report last time to the test team. But I want to make sure everything is understood before we continue further diagnosis. 

  @Clive_A 

Hi,

• If the swithe has firmware 2.20.3 an lower. Everything works fine with this module. If I upgrade to 2.20.4 and higher, prolems begin.
• Not only this one port is going up and down! All SFP+ Ports are goging up and down!
• The Cable from Switch to Server is a different one now. I tested with another one and same Result. Cable lenght is 2 meter and CAT 6a.

I will do some tests with another module and answer the rest of your questions afer my holiday in two weeks.

  @PROXYTEC 

PROXYTEC wrote

  @Clive_A 

Hi,

 

• If the swithe has firmware 2.20.3 an lower. Everything works fine with this module. If I upgrade to 2.20.4 and higher, prolems begin.
• Not only this one port is going up and down! All SFP+ Ports are goging up and down!
• The Cable from Switch to Server is a different one now. I tested with another one and same Result. Cable lenght is 2 meter and CAT 6a.

 

I will do some tests with another module and answer the rest of your questions afer my holiday in two weeks.

 

Are all SFP ports going up and down, with or without a connection? Like 49 is used, but 50 51 52 are not. And all 4 SFP+ experience the up and down? Or it's a different way?

It would be more helpful if you specified that. 

The rest of the questions, please answer once you have made some tests. 

  @Clive_A 

Did some Tests on the weekend.

1. I changed the Module TL-SM5310-T (UN) Version 1.0 with a new one. Problem persists.

2. The SFP+ Links are goging down and up. Omada is not showing that the ports are down! I can see it on the Firewall logs because the Firewall is also connected to one of the SFP+ Ports.

My Ping tool is also recognicing some packet loss.

3. Module and Drive Version on the NIC: TL-SM5310-T (UN) Version 1.0. Partnumber 135501078

4. Tried another LAN cable. -Y Problem persists

5. There was no traffic load on weekend and the Problem occured.

6. I Updated the switch to version 2.20.11 also. And the Problem is still there.

Since I have now ruled out that the module is NOT the problem. I will change the switch and hope that this is an hardware issue. 

I will come back when the problem is still there with the new switch. Then it has to be somthing with the firmware since. version 2.20.4 an higher.

  @PROXYTEC 

PROXYTEC wrote

  @Clive_A 

Did some Tests on the weekend.

 

1. I changed the Module TL-SM5310-T (UN) Version 1.0 with a new one. Problem persists.

2. The SFP+ Links are goging down and up. Omada is not showing that the ports are down! I can see it on the Firewall logs because the Firewall is also connected to one of the SFP+ Ports.

 

2025-08-04 12:00:49

FWStatus, [eth9] Sending interface status event for link DOWN, pri=6, proc_id=networkd, msg_id=3100-0031

 

2025-08-04 12:01:02

FWStatus, [eth9] Sending interface status event for link UP, pri=6, proc_id=networkd, msg_id=3100-0031

 

My Ping tool is also recognicing some packet loss.

 

3. Module and Drive Version on the NIC: TL-SM5310-T (UN) Version 1.0. Partnumber 135501078

4. Tried another LAN cable. -Y Problem persists

5. There was no traffic load on weekend and the Problem occured.

6. I Updated the switch to version 2.20.11 also. And the Problem is still there.

 

Since I have now ruled out that the module is NOT the problem. I will change the switch and hope that this is an hardware issue. 

I will come back when the problem is still there with the new switch. Then it has to be somthing with the firmware since. version 2.20.4 an higher.

Result of the two TP-Link switches, and test results? 

If you go with the RMA, that'll be fine. Let's see. 

  @Clive_A 

Hi,

I changed the switch SG3452XP with a complete new one. Installed the same Firmware 2.20.11.

I changed the Module TL-SM5310-T (UN) Version 1.0 with a complete new one.

Guess what.

Still the same Problem.

Since the Module is connected to the switch with an attached device. The pings on the network look like this.

08.08.2025 20:39:44   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (1ms) - Ping
08.08.2025 21:01:08   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 21:01:45   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 21:21:45   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 21:22:30   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 21:25:54   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 21:26:02   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 21:26:11   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 21:26:15   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 21:48:02   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 21:48:14   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 22:22:35   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 22:22:52   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 22:23:17   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 22:23:21   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 22:31:48   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 22:31:56   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
08.08.2025 22:35:11   - 10.0.2.243 (AP Pool) [10.0.2.243] keine Antwort - Ping
08.08.2025 22:35:48   + 10.0.2.243 (AP Pool) [10.0.2.243] antwortet (<1ms) - Ping
 

06.08.2025 19:13:54   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
06.08.2025 19:16:20   - 192.168.13.60 (Telefon) [192.168.13.60] keine Antwort - Ping
06.08.2025 19:23:48   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
07.08.2025 17:40:19   - 192.168.13.60 (Telefon) [192.168.13.60] keine Antwort - Ping
07.08.2025 17:41:52   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (1ms) - Ping
07.08.2025 21:31:47   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
08.08.2025 20:27:14   - 192.168.13.60 (Telefon) [192.168.13.60] keine Antwort - Ping
08.08.2025 20:27:18   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
08.08.2025 21:59:49   - 192.168.13.60 (Telefon) [192.168.13.60] keine Antwort - Ping
08.08.2025 22:00:18   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
08.08.2025 22:22:47   - 192.168.13.60 (Telefon) [192.168.13.60] keine Antwort - Ping
08.08.2025 22:22:52   + 192.168.13.60 (Telefon) [192.168.13.60] antwortet (<1ms) - Ping
 

I will now try to connect the server with a SFP+ direct-attached-cable. If this works,

then there is a Problem with the Module TL-SM5310-T (UN) Version 1.0 and the SG3452XP since Firmware 2.20.3!

  @Clive_A 

so after 24 hours since I changed the connection from Module TL-SM5310-T (UN) Version 1.0 to Direct Attached Cable SM5220-1M (TL-SM5220-1M).

There no NO paket loss and no port connections are dropping. 

Summary:

- Switch and Module was change with new one. -> No Hardware issue

- When using Direct Attached Cable there are no problems

Problem with SG3452XP v2.20 AND Module TL-SM5310-T (UN) Version 1.0 are present since Firmware Version 2.20.3 and newer.

So there has to be a Firmware Problem at this Switch working with this Module!!!!!

TP-Link you have to check this now!

  @PROXYTEC 

PROXYTEC wrote

  @Clive_A 

so after 24 hours since I changed the connection from Module TL-SM5310-T (UN) Version 1.0 to Direct Attached Cable SM5220-1M (TL-SM5220-1M).

There no NO paket loss and no port connections are dropping. 

 

Summary:

- Switch and Module was change with new one. -> No Hardware issue

- When using Direct Attached Cable there are no problems

 

Problem with SG3452XP v2.20 AND Module TL-SM5310-T (UN) Version 1.0 are present since Firmware Version 2.20.3 and newer.

So there has to be a Firmware Problem at this Switch working with this Module!!!!!

 

TP-Link you have to check this now!

That's to say, with our DAC, that works fine.

So, what's the fiber you used in this context when you are not using the DAC? Length of it.

This has also been sent to the team. 

  @Clive_A 
When unsing Module TL-SM5310-T (UN) Version 1.0
we use CAT 6A cabels. In this case 2 meter.

When we use the DAC, we tested 

SM5220-3M (TL-SM5220-3M)

SM5220-1M (TL-SM5220-1M)

both are working fine

  @PROXYTEC 

PROXYTEC wrote

  @Clive_A 
When unsing Module TL-SM5310-T (UN) Version 1.0
we use CAT 6A cabels. In this case 2 meter.

 

When we use the DAC, we tested 

 

SM5220-3M (TL-SM5220-3M)

SM5220-1M (TL-SM5220-1M)

 

both are working fine

The case has been returned. 

As I requested, the information was not provided. We are not able to judge based on the given information so far.

I specifically requested you to use the CLI to output the results. 

show logging buffer, show fiber port, and show ddm status 

Also, we need a backup. Is this a standalone mode? If it is, you can export the backup and upload it here. Otherwise, we will need a private ticket. 

Since the beginning of 2025, we no longer create the email tickets for the user. To assist and figure it out efficiently, we recommend submitting a support ticket via email.

Please include:

1. Your Forum ID;

2. Your community nickname;

3. A detailed description of the issue and result if I have suggested anything on the thread, and the troubleshooting steps you've taken in the subject line or body of your email.