Hi,
first time with Mikrotik hardware and RouterOS. I cannot get SFP port up. I have Mikrotik SFP module installaed (https://mikrotik.com/product/S-3553LC20D) and did not work. I have also tried another vendor SFP module with the same results. Status is No Link Connected. I have tried manually configure speed and duplex but no help.
Currently running software version is 7.18.2
Any ideas what to try nex?
Try to connect port eth1 to any device (have it active) and then try SFP. I do not say that it’s any kind of a “solution” but it’s worth to check if SFP works at all.
You are not alone Problems with SFP link on Hex S 2025
@BartoszP
Tried that already. connected eth1 in both situations (as part of the bridge and as single port). not sure if it’s the same case here, but it didn’t work for me.
@suulperi - i’m having the same issue, with a different SFP module that is working great on my “old” Hex S . tried 7.18.2 to 7.20 beta5, no luck.
there is a ticket that is currently open in Mikrotik support, and when diagnosing the supout.rif file, they can see that the state of the link is up, no tx\rx or any other errors, but no traffic too.
Let’s hope it will be resolved soon.
I connected my laptop to port eth1. Got IP address from APIPA (169.254.x.x) and no changes to SFP. When turning hEX S on I can see SFP port light blinks once and after that it is turned off.
Have you got any new information about this issue? Do you happen to have any insight how long it usually takes that issues are fixed?
no, in both cases.
i have the hex S for 2 years, and luckily i didn’t need any support or had any issues.
As for the new Hex S, my support ticket is open for 3 weeks, I’ve added a comment there 2 days ago, but no response so far.
I’ll wait a day or two, see if Mikrotik has any insights or ideas for a solution, or at least a workaround.
Thanks! I bought Mikrotik hardware for my home lab but I guess I need to start considering other options if this will not be solved within next few days. Not the best experience so far but hopefully it will be solved soon.
HI, did you manage to solve your problem? have you reached out to Mikrotik support? my ticket has been open for more than a month, and the last response from them was more than 2 weeks ago. tried to contact them several times since, but no response.
Hi! Not yet. I have figured out that my ISP use some FTTH related SFPs so I have ordered a new one.m which would be suitable for that one. My current ones are not working with media converter either so when that is fixed then I can continue with hEX.
Just saw your reply (for some reason i didn’t get an email).
as for the SFP that you ordered, how can you tell if it will work? is it on mikrotik supported SFP list?
I’m still waiting for a solution from MT support, they are still investigating it.
Thanks
I have a TP-Link Media Converter and that does not work either with existing SFP module. I have found out that fiber to the home -solutions use GPON OLT -SFPs and have to have one which supports that.
Sorry to chip in with no new information, but this bears repeating.
Many of the ISP-supplied GPON units have a significant part of the PON logic integrated into the host device, and the (special) SFP modules only provide the optics.
There are devices from many suppliers who sell fully integrated GPON SFPs, where the module itdelf has a small processor, usually with a Linux running on it that handles everything. GPON also includes authentication and provisioning, so whether a given module works (or can be made to work) with your particular ISP is a fun little project.
Mikrotik doesn’t currently have devices that integrate this GPON logic, but some leaks were spotted at a trade show.
Full thread: https://www.reddit.com/r/mikrotik/comments/1j45fj4/mikrotik_mwc25/
If your lazy, the picture:
And the spec sheet: https://box.mikrotik.com/f/1f880747e77346a3bf7f/
i’m aware of this, and indeed this is the case with the Nokia GPON SFP G-010-A. the issue that i’m having is specific to Hex S 2025. same GPON works great on Hex S for over 2 years now, with no issues whatsoever.
MT support still trying to figure it out, but i suspect it got something to do with the Driver\FW for this specific SFP with this specific SoC (Hex S 2025 uses EN7562CT, whereas Hex S uses MT7621A).
In my case, the SFP also works great on any media converter and a ubiquiti EdgeRouter (which also use the MT7621A SoC).
@shrek3 Yeah, sorry. My answer wasn’t meant for your case. I’m aware that for the newer 8811 stuff, the calls normally used via ethtool are a bit “strange”.
Hopefully as things turn up, they will be debugged and hunted down… Every new platform is bound to have these.
… particularly those poorly tested …
If construction/building or mechanical engineering worked the same way we would have a much less populated world. 
Mistakes and accidents can always happen but in the case of these new Hex and Hex S it does seem like a systematic lack of proper testing of the devices.
Exactly. And since its the only router at the moment with this “new” SoC and with SFP port, this definitely can be related to a FW\Driver bug.
Let’s hope it will be fixed soon.
Once I found this 
If builders built their buildings the way programmers write their programs, the appearance of the first woodpecker would lead to the collapse of civilization.
It’s a fact that MediaTek and its subsidiaries make probably the best value-for-price SoCs at the consumer end of the spectrum for network devices, and we all want to have nice things for cheap. This is why every manufacturer wants to use their stuff, just look at the Banana Pi BPI-R4.
And unsurprisingly, everyone is having the same problems, including what is known here as the “slow ether1/sfp issue”, which is down to the 8801 and 8811 (and 8811S) driver support for the ethtool calls.
I don’t think Mikrotik deserves to be disparaged, because they are basically the only manufacturer that I know of that actually manages to get to the bottom of at least some of these issues and manages to get engineering support for these chips.
I say this of course recognizing that it’s a slow process, and that customers deserve stable/functional devices, and that waiting for such fixes can be frustrating.
Yep :), but my note was not particularly aimed at the good Mikrotik guys (or at least not particularly aimed to them).
It is the whole industry revolving around software and electronic hardware that is somehow allowed to have defective, underpowered or however not properly or fully functioning products in a way that would be not acceptable (and actually not accepted) in other fields of industry.
The whole concept of “OK, it is not working as it should, let’s market it as is, later we will find a software fix” is conceptually rotten.
The “Hey, but it costs only x$” is only a partial justification, of course we all want moore power/speed/whatever for the smaller possible cost, but that is the market, baby.
Honestly, if I had a 1 Gb connection and had just bought a new Hex S as my first Mikrotik device I would be really pissed off, and - no matter who is the culprit - it is the Mikrotik brand that suffers in terms of reputation.
