SX3008F not passing DHCP through switch

SX3008F not passing DHCP through switch

SX3008F not passing DHCP through switch
SX3008F not passing DHCP through switch
2026-03-22 03:16:02 - last edited Yesterday
Model: TL-SX3008F  
Hardware Version: V1
Firmware Version: 1.20.18 Build 20260310 Rel.15665

I have the following LAN setup at home

TP-Link BE24000 -> TP-Link TL-SX1008 -> TP-Link TL-SX3008F v1.2 -> clients

 

TL-SX3008F loaded with eight 10GE SFP+

TL-SX3008F Port 1 is connected to TL-SX1008 by cat 6a cable

Clients are connected to TL-SX3008F using cat 7 cables

DHCP is provided by the BE24000

LAN subnet 192.168.10.0/24

All devices on VLAN1

Devices connected to TL-SX1008 get DHCP from the BE24000 no problems

Devices connected to the TL-SX3008F do not get DHCP unless I reboot TL-SX3008F and this is hit and miss - some do and some don't

 

TL-SX3008F is fully patched with all ports enabled.

 

TL-SX3008F replaced QNAP 6 port 2.5GE unmanaged switch - no problems with DHCP when this switch was connected.

 

Guidance on how to get DHCP working appreciated.

  0      
  0      
#1
Options
1 Accepted Solution
Re:SX3008F not passing DHCP through switch-Solution
Yesterday - last edited Yesterday

  @MarkAGregory 

 

Its up to the modules to do the port speed conversion, not the switch ports.  If you change the switch ports to anything other than 10g (for 10g modules) the modules wont pass through any data, they NEED 10g on the SFP+ side to work, their internal chip negotiates the RJ45 side and handles the speed conversions

Im failing to understand why you are using a SFP+ only switch, with modules, for mostly 1g and 2.5g clients, when there are better options such as SG2210XMP-M2  (2.5g rj45 / SFP+)

 

 

Recommended Solution
  0  
  0  
#5
Options
12 Reply
Re:SX3008F not passing DHCP through switch
2026-03-23 08:00:09

Hi  @MarkAGregory 

Since this SX300F has 8 SFP+ ports, so may I know the model of the module you use for connection?

When some clients behind the SX3008F failed to get IP address, then what is the IP on the client? Is it 0.0.0.0 or 169.254.x.x?

By the way, you may try to switch the location of the TL-SX1008 and SX3008F to check the clients as the SX3008F is a managed switch.

 

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options
Re:SX3008F not passing DHCP through switch
2026-03-23 08:20:52

  @Hank21 thank you for your reply. 

 

I have the SM5310-T 10G BASE-T RJ45 SFP+ modules

 

There is only one LAN subnet 192.168.10.0/24 all set to VLAN1

 

So far, I've found that a small 6 port 1GE unmanaged cisco switch will only work when I set the connected port to 1000 Mbps - If I set the port to 10G the devices connected to the cisco switch do not get DHCP even though the NIC lights are green and yellow to indicate 1 Gbps.

 

I have a minipc with 2.5Gbps NIC and the only way I can get this connection to work is to go into the SX3008F to set the port speed to 1000 Mbps, then disable the port, enable the port then change the port speed to 10G and finally the minipc will get DHCP and work at 2.5 Gbps

 

I disabled the four ports that are not being used in the switch.

 

I was hoping that TP-LINK would be reasonable products, but I'm amazed at how badly this is going.

 

so what is the current status when I boot switch.

Port 0 10Gbps - upstream ok

Port 1 10Gbps - HP Z6 G5 with 10 GE NIC ok

Port 2 1 Gbps - Cisco 6 port unmanaged 1GE switch with printer, etc connected ok

Port 3 10 Gbps - GMKTec minipc with 2.5 GE NIC fail

 

I have a second SX300F and 8 SFP+ 10G modules still in boxes - I'm worried that if I deploy them my home network will really screw up. I've ordered an OC220, but from what I read this won't fix the hardware failures / firmware problems.

 

Any guidance appreciated.

  0  
  0  
#3
Options
Re:SX3008F not passing DHCP through switch
Yesterday - last edited Yesterday

Hi  @MarkAGregory 

 

Sorry for the late reply.

Why did you choose to purchase an SFP-port switch to connect RJ45 clients? Are you trying to provide 10G speed for the clients? This is not a recommended installation.

The process of converting optical signals to electrical signals generates significant heat.

May I ask how many SM5310-T modules are connected to your SX3008F? If you plug more than 2 of them into the switch, it will significantly affect network performance.

I believe this is the reason.

Below is the compatibility page of SM5310-T:

https://www.tp-link.com/hk/tl-sm5310-t/product-list/

 

You may give us more details about your installation and the bandwidth provided by your ISP, and I will suggest accordingly.

 

  0  
  0  
#4
Options
Re:SX3008F not passing DHCP through switch-Solution
Yesterday - last edited Yesterday

  @MarkAGregory 

 

Its up to the modules to do the port speed conversion, not the switch ports.  If you change the switch ports to anything other than 10g (for 10g modules) the modules wont pass through any data, they NEED 10g on the SFP+ side to work, their internal chip negotiates the RJ45 side and handles the speed conversions

Im failing to understand why you are using a SFP+ only switch, with modules, for mostly 1g and 2.5g clients, when there are better options such as SG2210XMP-M2  (2.5g rj45 / SFP+)

 

 

Recommended Solution
  0  
  0  
#5
Options
Re:SX3008F not passing DHCP through switch
Yesterday

  @Hank21 thank you for your comments. I've worked around this matter quite a bit. The problem is with the negotiation that occurs when the switch is started or when computers are added. I've discovered the switch is not what I was hoping for, so I'm moving to another solution. Yes, I thought I could put 8 SFP+ 10 GE devices into the switch and it would work. But it does not. The excuse that TP-Link spins is that the device gets hot. Well it is not hot and it fails until you take out 6 or 7 of the SFP+. Also the speed negotiation is a mess, particularly with 2.5 GE devices. I found that connecting legacy 1 GE devices required setting the ports to 1 gbps mode. I can't spend more time on this, I don't have hours to go through all of the trouble shooting that TP-Link has asked for. So the root cause may not be identified. I'm currently using a 5 port TL-SX105 and a QNAP QSW-2104-2T to overcome my lack of a working switch.

 

People might ask why did I buy two of these switches and 16 SFP+ 10GE modules from TP-Link? I had already purchased two TL-SX1008 and the fan noise is horrendous. I was looking for a fanless alternative. Then I saw people talking about swapping out the noisy fans for quiet fans. So many problems with TP-Link. TP-Link are now stating that if you change the fans you void warranty. Not in Australia TP-Link! And yes, I also purchased an omada gateway and OC220. It all goes into the bin.

 

I'm waiting for new supplies of fanless switches to become available from another vendor. I've read positive reports on their fanless switches that have 8 10GE RJ45 and 8 SFP+ ports. And don't have heat problems -> hint hint TP-Link.

  0  
  0  
#6
Options
Re:SX3008F not passing DHCP through switch
Yesterday

  @GRL I found that the only way to get 1GE devices to work with this switch was to change the port to 1Gbps. You might think that the SFP+ RJ45 10GE module negotiates in the correct order but it does not from my research. And it totally craps out when you try to connect QNAP boxes with 2.5 GE even though the SFP+ RJ45 10Ge modules state that they handle 1GE, 2.5GE, 5GE, 10GE. And yes the ports are set to 10GE for the 2.5 GE QNAP devices. I've tried so many devices and switch combinations that I've run out of time and patience with TP-Link. There is a problem with the SX3008F, it is not syncing as it should with the TP-Link SFP+ RJ45 10GE modules (the modules get a good rating from people using the modules with other vendor switches) when 2.5GE boxes are connected, and yes, I tried boxes other than QNAP to check.

 

TP-Link state that the switches should have only one SFP+ RJ45 10GE module - this is a copout and written in a location that the average person looking for a fanless switch is not going to notice -> I didn't. I can't fathom the thinking at TP-Link. I have so many SFP+ switches of different sizes, right up to 48 port, and never run into this problem before.

 

I'm changing vendors, and if you look at the previous post you'll see that I've wasted more than $8K on TP-Link that I'll never get back. All TP-Link support did was put the problem onto me and ask me to diagnose the problem for them with an ever increasing list of questions. I don't have time nor the energy for this. Switches are not meant to be this hard.

 

And I cannot stress how loud the fans are in the TL-SX1008. I'm amazed at how loud and noisy the TP-Link products are. So never again.

  0  
  0  
#7
Options
Re:SX3008F not passing DHCP through switch
Yesterday

  @Vincent-TP yes, I missed the fine print. I've used other vendor products for many years, and never run into this 'limit' on SFP+ RJ45 modules before, so did not go looking. How hard is it to make a switch that works without the problems I've found with this switch. I've now found a product from another vendor that does not have the TP-Link problems, so I'm moving in that direction. thx for responding, it is appreciated.

  0  
  0  
#8
Options
Re:SX3008F not passing DHCP through switch
Yesterday

  @GRL I'm looking for 8 port 10GE switches to simplify my network. I have a lot of devices, they move around, I don't want to have to move switches as well. I don't want to think about switches. I want to purchase, plug in and use without all of the mucking around that I've experienced in the past month.

 

As I mentioned in another post, I purchased two of the 8 port 10GE RJ45 TL-SX1008 and found they were so noisy that I could not think. I can hear the one in the hall closet when I walk past. The one in my office lasted an hour, I could not put up with it.

 

I should have moved to another vendor then, but doubled down -> my mistake. I purchased two of the fanless TL-SX3008F, 16 SFP+ RJ45 10GE modules, an omada gateway and OC220. All of the TP-Link is going into the bin. I could not give it away with the problems I've found. $8K+ down the drain.

 

And yes, I've subsequently read about people changing the fans in the TL-SX1008 and how TP-Link has responded by saying this will void warranty. In the USA maybe, not here.

 

I don't have the time nor energy to waste on this. Switches are not rocket science, they should work out of the box without all of this nonsense and noise.

 

TPLink support gave me a very long list of things to do and to report to them. I don't have the time nor the energy. They must know there are problems, now that I've googled, I've found a lot of complaints about noise, etc.

 

I do wish that my TP-Link experience was better. Hopefully they will improve their products over time. But for now, another vendor beckons.

 

thank you for responding, it is appreciated.

  0  
  0  
#9
Options
Re:SX3008F not passing DHCP through switch
15 hours ago

  @MarkAGregory 

 

SFP+ ports dont support auto negotiation, and this is the same with any vendor.  If you use DAC cables, you must specify the port speed manually, if you use modules, you leave the ports at 10g and let the module do the conversion.

 

TPlink arent designing and making their own switch chips - they use the same ones all the other vendors do and the limitations are across the board, not limited to one vendor.

 

If you want better auto negotiation you will have to use RJ45 port based switches (with SFP+ uplink if you need that), SFP isnt for you - its designed for infrastructure as its primary purpose

  0  
  0  
#10
Options
Re:SX3008F not passing DHCP through switch
15 hours ago

  @GRL I don't agree with your statement. There are two negotiations that occur. The first is the port and the module, then the module negotiates with the device. I was able to get the 2.5GE devices connected to the SX3008F so any suggestion that this will not work is not correct. There is, in my view, a change needed in the SX3008F firmware to ensure that when the device is started or when a new device is connected the negotiation process proceeds correctly, without hanging. It is not the chips, it is the firmware that is the issue from what I can see, and the problem should be able to be fixed.

 

I have worked with many hundreds of switches from many vendors in my career, and never seen anything like this before.

 

I do agree that I need to look for another vendor, one that provides a solution that works, and I've found one thank you.

  0  
  0  
#11
Options