hEX S (2025) SFP problem

RouterOS General
1

Here is the scenario. I don't get why it happens. It is not about the bandwidth or the link or something else. It is the BOOT (even I think POST) problem. I thought it is the problem of my hEX S, but it already happened with my 2nd hEX S device.

let's start from the scratch.

There is only the AC/DC adapter plugged in and a SFP inserted without optic cable. Mikrotik not coming UP. I'm plugging out the SFP, nothing happens, SFP led not blinking.

2. I'm unplugging both the AC/DC and the SFP. Plugging in the AC/DC SFP led blinking and all coming UP. Then I'm inserting the SFP and all works fine. BUT if the hEX S again restarts it won't come up again.

Does anyone know what is happening? chatgpt and gemini are blind about it.

I have 3 hEX S devices. 1 of them is the old one which is with 1G SFP port, 2 of them with 2.5G SFP port. I don't have problem with the old one. It works fine. I think the problem is with this 2.5G SFP port but I'm not sure.

2

This is usually about some sort of driver issue, e.g. some sort of enumeration not happening at the right time or some hot plug event emitted when the listener isn't ready, etc.

Write to MT Support directly with as much detail as you can. If this is an official sfp module, you have fairly good chances of it getting fixed...

3

it was before on this forum, same device (same problem)

OP was tried with better PSU to exclude PSU as problem, but nothing helped
theory is tha internal PSU in MT is too weak to handle cold BOOT process + cold BOOT SFP

but maybe we are all wrong :slight_smile:

if you have patience, you could boot openwrt on it, enable rs232 flag in boot config from openwrt, then solder some jump cables, attach serial to pc & try to debug boot process

4

Does flipping off//on the SFP when it doesn't come up work?

If yes, a script loosely like :

/system scheduler
add name=DelaySFPOnStartup start-time=startup on-event={
    /interface ethernet disable [find name="sfp-sfpplus1"]
    :delay 30s
    /interface ethernet enable [find name="sfp-sfpplus1"]
}

might be a temporary workaround.

But if the hex doesn't power at all with the SFP inserted it won't work.

Does powering it via PoE make any difference?

5

As an alternate to that (since I'm pretty sure it is completely down when thjs happens), how about getting it running via whatever means works, disabling the SFP port and then trying to boot? Not a solution, but might be insightful . . .

Also (maybe I missed it), but what is the make/model of the SFP?

6

yeah I got you, if it is a driver issue then all the hEX S 2025 models have to get new update. Coz I got this problem with both of my 2 hEX S 2025 models.

I have sent and e-mail to them, hope they even read it)

7

yeah tomorrow I'll check it. SFP vendor is Sopto which I use almost everywhere. I have used this SFP on another hEX S which's the SFP port is 1G, there is no problem with that. The problem started with hEX S 2005 which the SFP port 2.5G. They have changed almost everything in that model, cpu, ram, storage, sfp port capacity and etc.

8

TBH, I didn't check this method. Tomorrow I'll check it.

9

Personally i would recommend sending a jira ticket, i've had much faster response times with it.

10

Now as 7.24 released, try updating and see if it fixed your issues. @Fu_Ba

11

opened 7 hours ago and still no response )

12

I did, not helping

14

Which, considering timezones and such, is not unreasonable . . .