Another me too... So I guess that update never saw the light of day? Because the last SwOS version 2.13 that i am running came out before the last comment on here so. I just relized after a year in production because nothing was ever rebooted but ended up with a firewall that can't talk to a switch...

Also keep in mind that if you have assigned a VLAN to the "Allow From VLAN" setting and you want the Switch obtaining an IP from some DHCP-Server, that server needs to be in the same VLAN.

Unfortunately, version 2.13 is still the latest SwOS version officially available.

Hi, your issue might be related to this thread: SwOS 2.15? Long story short, if it's true what has been said about SwOS-2.14 and SwOS-2.15 in that thread, then these new versions are for products with same name but different internal components... I'll keep my fingers crossed that you can recover yo...

Wow... that is really not what I was expecting from a new SwOS release.
Is it so hard to finally push out a bugfix release for existing devices?

Contact support@mikrotik.com instead of waiting for someone from Mikrotik to read here...

Do you really think I'd get something else than the usual "it's ready when it's ready" reply from Mikrotik support?

I'm also desperately waiting for a new SwOS release. Mikrotik, please hurry up

Mikrotik finally replied to the ticket I had filed back in 2021. It seems they were able to reproduce the issue in their labs and have prepared a fix for the next SwOS release which is unknown to when it will be released. They also mentioned that this issue does not happen in recent RouterOS release...

Unfortunately, Mikrotik devices with SFP+-ports only support NBase-T (2.5GBit/s and 5GBit/s) with their own 10GBase-T Transcievers: Mikrotik S+RJ10.

I’ve flashed the latest Intel firmware (i40e; fw 8.5.67516 api 1.15 nvm 8.50 0x8000b6c7 1.3082.0) on my XL710-QDA2 NIC but problem still persists. Another observation I’ve made is that in order to get the link connection back, unplugging and replugging the QSFP+ cable at the remote device does not h...

The CRS309-1G-8S+IN is quite small. You should see from its internal temperature sensor if one or more transceivers are running too hot. Ideally the switch should not exceed 60°C temperature during operation. But using it solely with 10GBase-T modules might be challenging

Any chance you have some VLAN settings in place that prevent access when your switch runs SwOS?

Well, that's a typical case of Transceiver vendor issue. Many Transceiver vendors don't care about correct reporting in 10GBase-T modules. Many vendors even don't bother about DDM temperature reporting although especially 10GBase-T modules tend to become very hot. 90°C+ in a passively cooled switch ...

Hi, I can confirm that the FS SFP-10G-T modules do not support NBase-T (2.5GBit/s and 5Gbit/s). The Mikrotik S+RJ10 module does support NBase-T but your transfer speed results will only improve after you have enabled Flow Control (for Rx and Tx traffic) on the corresponding SFP+ port in your switch.

I would also like to have this feature in SwOS. That should be common standard nowadays.

Out of curiosity, what NIC(s) do you connect to your QSFP+ port(s) at the switch?

I have that problem with two Intel XL710-QDA2 cards where even flashing the latest firmware (8.40 at the time of this writing) onto the NICs did not fix the issue.

Additional observation: it is not mandatory to reboot the switch in order to get the link connection back. What also helps is to either disable (set the connection to 40G link speed) or enable auto-negotiation at the corresponding QSFP+ port.

I've filed a support ticket but got no reply yet.

Hi there, just a "me too" for being affected by this problem. Same switch (CRS326-24S+2Q+) and same observation like the initial poster. Once I power cycle the QSFP+ remote station, there won't get any link connection being established. I can fix this by rebooting the switch but to be hone...