I have been experiencing a new problem I believe since upgrading to routeros 7.23 that still occurs after the latest upgrade to 7.24.
Specifically, I have a hAP ax S router with a SFP fiber module (Leox LXT-010S-H) that I use to connect to the Internet. The problem I experience is that after rebooting the router, the fiber module is not accessible over its private LAN and also its internet connection fails to start up.
The only way to get my internet connection running again, or even to make the module's private LAN/telnet/web-ui accessible, is to physically unplug the fiber cable from my module, then remove the fiber module from the router, then reverse those steps to restore the functionality.
Is this something anyone else has experienced since the last 2-4 months using RouterOS?
A similar problem on 5009 and GPON SFP modules from ODI, Dlink, and Huawei. The only way to fix it is to completely - cut off the power to the module, turn off the router’s power, or remove the module.
As far as I can see, MikroTik cannot cut off power to the SFP module, and the request to add this functionality has received no response. However, for example, we can turn on and off the single small USR LED in the AX2’s ass side..
Yeah, it's weird. I never had the thought I would need such a feature until recently. In my memory of having this setup since the beginning of 2026, the module worked perfectly with the router across reboots/upgrades but it has become a problem recently, and I doubt it is the fiber module because I have not touched that since the initial setup. I've seen those forum posts as well asking for the feature. There are definitely a few controls in routeros for power cycling that I've seen such as for power over ethernet and USB ports but it seems like the sfp would also be pretty good.
I assume it's possible to cut the SFP's power because there is a tunable sfp-shutdown-temperature property on the SFP interface. I guess next time I need to, I'll try setting that to a value below the normal running temperature and hopefully it will power off the SFP module until I restore the original value.
I tested the sfp-shutdown-temperatureapproach. It turns out that when the shutdown temperature is breached for long enough, the corrective action of RouterOS is to disable the interface, which does not power it off so that will not be a workable option.
Buy a new/other one and test it. If its a simple swap then the problem was in the module.
Steps to troubleshoot in general:
1. Check the cable (plugged in, plugged in correctly, damaged?)
2. Check for damage on the unit, see if it turns on
3. check the medium that you're plugging into, fiber ferrules and modules can be dirty from the factory, clean them
4. if its none of that, look at configuration, if its not configuration
5. buy a new module and see what happens when you swap the module
6. last resort is swapping the device.
It's definitely not 1-3. The thing works fine in general and has worked fine for over 6 months. I actually did some more tests and the connection will actually restart successfully if I run /system/shutdown and then re-plug the power so that is a simpler option for restoring the connectivity without disassembling anything. I really feel like this problem can be solved inside if there were a power control capability on the sfp interface and if there were an option to use it to cycle the power during the reboot process.
For #4, it's hard to say whether it's a configuration problem. As far as I can remember, everything was working fine until 7.23 but I haven't downgraded or anything to confirm this.
For 5-6, I'm not going to spend all that cash just to figure out whether my setup is broken or there's a new bug.
This has been a request that is long standing (rebooting the SFP) I have been asking for a solution for years now.
From my Experience - SFP module IS generally the issue - not the router. I have one CCR2004-12s+blablah the the 850nm MM 10G SFPs that had issues when testing - but needed deploy.
I did not confirm which SFPs had the issue initially (just ports) and when re-installing onsite - ports with issues changed - so i suspect i just swapped the modules around.
I have yet to get back to site and swp out SFPs - in my instance - only and issue after power outage (very rare - 2nd time in 1.5 years)
Site removes the SFP and reseats - issue resolved.
So yeah, a powercycle on SFP would be great - but I suspect this will be a hardware limitation, and not possible in software.
In the meantime - get different Modules and try them - it may fix your issue.
I did just find a solution that works for my hardware, specifically just setting:
auto-negotiation=no
speed=1G-baseT-full
on the sfp interface makes the router capable of successfully rebooting with access to the module again. As I suspected, the module does not reboot when the router reboots since the SFP module's embedded web server reports its uptime and it's not interrupted across reboots.
Edit: Checking the 7.24 changelog, I have seen the following line, so maybe this is related:
*) sfp - fixed linking for hAP ax S and hEX S (2025) with "1G-baseX" link-mode;
Either way I've tested 1G-baseT-full and 2.5G-baseT which both work with my SFP module.