MikroTik

SwOS version 2.16 released
http://www.mikrotik.com/download

What's new in v2.16:

*) added support for CRS310-1G-5S-4S+IN/OUT; CRS310-8G+2S+IN
*) added notification when Primary backup firmware is in use
and encourage moving to Secondary regular firmware;
*) added confirmation dialog before resetting configuration;
*) added support for board-specific backup filename generation;
*) added SNMP serial number and version OIDs;
*) added option to disable IGMP querier;
*) added option to specify IGMP version;
*) added support for host table sorting;
*) added Clear All/Set Default buttons in the Port Isolation menu;
*) added options to set forced 2.5G or forced 10G for SFP+ ports;
*) added support for SFP rate select;
*) added support for pages in the host table;
*) css106: fixed Ethernet disable;
*) css106: fixed BPDU receive on only-tagged VLAN ports;
*) css106: fixed "Lock On First" setting;
*) css106: fixed RSTP port blocking;
*) css106: improved system stability;
*) crs312: fixed linking after changing auto-negotiation setting for combo ports;
*) crs354: added missing health readouts;
*) crs3xx: improved packet buffer resource allocation;
*) fixed duplicate IGMP query packets when IGMP snooping is enabled;
*) fixed multicast forwarding after disabling IGMP snooping;
*) fixed non-DHCP packet forwarding when Option82 is enabled;
*) fixed neighbor discovery from WinBox;
*) fixed port numbering in BPDU packets;
*) fixed packet forwarding after disabling RSTP on blocked port;
*) fixed IGMP group removal on link down;
*) fixed DHCP packet bypass on LAG by "Add Information Option";
*) fixed fragmented packet drops by "Add Information Option";
*) fixed DHCP request duplication when using DHCP Snooping;
*) fixed DHCP packet forwarding to untrusted ports;
*) fixed forbidden deletion of Default VLAN ID;
*) fixed SNMP ifSpeed OID reporting in certain cases;
*) fixed incorrectly restored backup configuration in some cases;
*) fixed S-RJ01 false detection as multi-mode fiber;
*) fixed SFP+ interface linking after enabling autonegotiation;
*) fixed QSFP+ interface linking after re-enabling it;
*) improved SwOS web interface stability and responsiveness;
*) increased up to 64 byte SNMP Community/Contact/Info/Location;

What's new in v2.15:

*) factory only release

What's new in v2.14:

*) factory only release

To install SwOS v2.16 on CRS310 family devices, upgrade RouterOS to the latest stable version and use "/system swos upgrade" command.

Thanks Mikrotik!

Hello guys, i have one CSS610 and two CRS310 devices. Because i already have the CSS610 with SwitchOS Lite and i found it very easy to use i wanted to use the 310's with SwitchOS. So i upgraded SwitchOS 2.16 on my 310's and rebootet both devices.
so i have flashed one passive CRS310-1G-5S-4S+OUT and one CRS310-1G-5S-4S+IN (active cooling with that small fan).
On the passive Outdoor its working fine but the CRS310-1G-5S-4S+IN is really noisy now because with SwitchOS the fan always turns at max speed (see attachment). So i had to revert it back to Routeros and it get's quiet after the booting again. How can i use SwitchOS and have the fan controlled autmoatic - is it a bug that it turns max Speed with SwitchOS? Its not even running hot with ~33°C Board and 42°C CPU temps but fans run at maximum level.

Upgraded my CSS106-5G-1S and CSS106-1G-4P-1S without issue. Both are fairly non-critical. I will wait a while and then update the three CSS326-24G-2S+ and the CRS326-24G-2S+.

Thanks team for the upgrade! Working fine for ~ 4 hours on CSS610, CSS326, CRS328, CRS317 and CRS318.
My only issue is about snmp and signals from sfp ports. What's the oid to get them? I need check this to detect fiber attenuations and another problems.
I don't need the heavy routeros because my topology is very simple and swos is so easy and clear.

Hello guys, i have one CSS610 and two CRS310 devices. Because i already have the CSS610 with SwitchOS i wanted to use the 310's with it too.

Hahaha...for a moment you had me there...CSS610 is running SOS-lite, not SWOS.

...but wait, what is that?...witchcraft, but non quite so (from my CSS610 on SWOS 2.17lite, showing the latest v2.16 of SWOS in the changelog ;-)

*) fixed non-DHCP packet forwarding when Option82 is enabled;

lets go! better late than never.

Hello guys, i have one CSS610 and two CRS310 devices. Because i already have the CSS610 with SwitchOS i wanted to use the 310's with it too.

Hahaha...for a moment you had me there...CSS610 is running SOS-lite, not SWOS.

...but wait, what is that?...witchcraft, but non quite so (from my CSS610 on SWOS 2.17lite, showing the latest v2.16 of SWOS in the changelog ;-)

yeah i should have pointed that out. I find them both very clean:

A little bit off-topic to the particular release, but - do we really need to be punished by looking into such an old, 30+ years old Unix / Amiga like designs?

And before someone jumps here as being irrelevant - design sells, period. Presenting those terrible screenshots in ones presentation to the client, is really embarassing.

MT can do nice designs - new logotype, website, mobile apps, but not the product web config UI. Please Mikrotik, put it somewhere onto your roadmap.

I attempted to update two CSS106-5G-1S switches from 2.13.
The first took it without any issue, as expected.
The second consistently dies after clicking the upgrade button and must be power cycled to "get it back". After it comes back up, and it takes several seconds to come back; it's back to 2.13.
The only real difference between the two is that the switch which is having problems upgrading is powered via PoE but the one that worked is using its standard power adapter.

As a follow up, I disabled the POE feed and temporarily used its wall-wart as the power source to see if that made a difference, for science.
I didn't expect it to, and my expectations were quite met.
It still refuses to upgrade and sits there like a brick until it's power cycled.

As a followup, I upgraded all three CSS326-24G-2S switches from 2.13 to 2.16 about 14 hours ago and the upgrades went smooth and no issues seen since. I am holding off on updating the CRS326-24G-2S for a while because it's at a remote radio site that I can't physically get to because I recently had knee surgery and I can't drive (and besides, I put my 4x4 truck in the shop since I could not drive for a while). I don't expect a problem, but I would hate to brick it and be unable to get there to fix it. So the CRS326 will wait a few more weeks.

I attempted to update two CSS106-5G-1S switches from 2.13.
The first took it without any issue, as expected.
The second consistently dies after clicking the upgrade button and must be power cycled to "get it back". After it comes back up, and it takes several seconds to come back; it's back to 2.13.
The only real difference between the two is that the switch which is having problems upgrading is powered via PoE but the one that worked is using its standard power adapter.

Same happened to me. Switch locked up after starting the update.
The solution was to temporary enable RSTP on all ports. After doing this, the update succeeded. Afterwards I disabled RTSP again.
I hope this helps.

I attempted to update two CSS106-5G-1S switches from 2.13.
The first took it without any issue, as expected.
The second consistently dies after clicking the upgrade button and must be power cycled to "get it back". After it comes back up, and it takes several seconds to come back; it's back to 2.13.
The only real difference between the two is that the switch which is having problems upgrading is powered via PoE but the one that worked is using its standard power adapter.

Same happened to me. Switch locked up after starting the update.
The solution was to temporary enable RSTP on all ports. After doing this, the update succeeded. Afterwards I disabled RTSP again.
I hope this helps.

Great catch!
That's not really "a good idea" in every environment, but it'll help many!

For some reason SwOS 2.16 is offered also for CSS610-1Gi-7R-2S+ which should be using SwOS Lite 2.17?

Is this an error or is CSS610 really supported on full SwOS 2.16?

After doing this, the update succeeded. Afterwards I disabled RTSP again.

Why do you have RSTP disabled?

[quote=Cray post_id=1058649 time=1708849804 user_id=64450]
For some reason SwOS 2.16 is offered also for CSS610-1Gi-7R-2S+ which should be using SwOS Lite 2.17?

Is this an error or is CSS610 really supported on full SwOS 2.16?

swosforcss610.png
[/quote]

It's an error and is not the first time. Go to download page and check. There are no 2.16 version to CSS610.

Hi, thanks for informing us. The issue with versions for SwOS Lite devices has been resolved.

I tried to upgrade a CSS106-5G-1S withou succes ....

the webinterface says upgrade availiable.
I enter upgrade, it says wait and than "ERROR: Upgrade failed"
webinterface is unreachable, all traffic seems to be working.
powercycling brings the device back the device in its original state ...

manually uploading the swos-css106-2.16.bin file gives the same result


upgrading my CSS326-24G-2S+ went without issues

I tried to upgrade a CSS106-5G-1S withou succes ....

the webinterface says upgrade availiable.
I enter upgrade, it says wait and than "ERROR: Upgrade failed"
webinterface is unreachable, all traffic seems to be working.
powercycling brings the device back the device in its original state ...

manually uploading the swos-css106-2.16.bin file gives the same result

Temporary enable RSTP on all ports. This worked for me.

I tried to upgrade a CSS106-5G-1S withou succes ....

the webinterface says upgrade availiable.
I enter upgrade, it says wait and than "ERROR: Upgrade failed"
webinterface is unreachable, all traffic seems to be working.
powercycling brings the device back the device in its original state ...

manually uploading the swos-css106-2.16.bin file gives the same result

Temporary enable RSTP on all ports. This worked for me.

careful here - double-check which bridge has the highest priority
and if all have the same priority, check the highest MAC address of the bridges communicating in the (R)STP election process
(consider configuring a dedicated mgmt port on your devices if possible)

I tried to upgrade a CSS106-5G-1S withou succes ....

the webinterface says upgrade availiable.
I enter upgrade, it says wait and than "ERROR: Upgrade failed"
webinterface is unreachable, all traffic seems to be working.
powercycling brings the device back the device in its original state ...

manually uploading the swos-css106-2.16.bin file gives the same result

Temporary enable RSTP on all ports. This worked for me.

No luck, still unable to upgrade with RSTP enabled

The day of release, I upgraded my CSS106-5G-1S without any problem.

What if you try the following, will you be able to upgrade successfully?
Or is this too simplistic?

1. Create a backup of the existing settings,
2. Reset the switch to factory settings,
3. Run the upgrade,
4. Restore the backup.

tried resetting the switch to default and then update?

tried resetting the switch to default and then update?

Just tried that, that works.
But not really an option for remote switches.
I got this one to the lab because it did not succeed, there is a spare on the actual location now ...
Have a couple of others remote ..

tried resetting the switch to default and then update?

Just tried that, that works.
But not really an option for remote switches.
I got this one to the lab because it did not succeed, there is a spare on the actual location now ...
Have a couple of others remote ..

I upgraded dozens of switches, CSS106-1G-4P-1S among them which should be pretty much identical except for poe, with and without RSTP without any issues... would be interesting to find out what setting is causing upgrade to fail... or maybe your switches are powered over poe which may be causing upgrade to fail?

these switches are pretty "standard" as the all have vlan99 added for maintenance and access to the switch only from vlan99.
RSTP disabled and all ports allowing all vlans ...
Not to special

- created backup
- reset to default
switch came back on a dhcp in the generic vlan
- upgrade
- restore backup
and everything back to normal ...

One of my css106 have a problem to upgrade hmm …
It is 2.13 on it.

*) added support for CRS310-1G-5S-4S+IN/OUT; CRS310-8G+2S+IN
...
To install SwOS v2.16 on CRS310 family devices, upgrade RouterOS to the latest stable version and use "/system swos upgrade" command.

I tried to install it on my CRS310-8G+2S+IN, using the latest stable (7.13.5), but after getting success with the command /system swos upgrade and saving the swos config, the switch does not boot up.
it does boot up, just the SFP+ ports does not work, see my next post

One of my css106 have a problem to upgrade hmm …
It is 2.13 on it.

I also had 2.13 on them.
Needed to follow the procedure as I described earlier in this thread

these switches are pretty "standard" as the all have vlan99 added for maintenance and access to the switch only from vlan99.
RSTP disabled and all ports allowing all vlans ...
Not to special

- created backup
- reset to default
switch came back on a dhcp in the generic vlan
- upgrade
- restore backup
and everything back to normal ...

I was able to recreate the issue by just adding the management vlan, that is if I try the upgrade from vlan tagged network it will fail...

I was able to recreate the issue by just adding the management vlan, that is if I try the upgrade from vlan tagged network it will fail...

That's interesting. All five of my switches are accessed via a Management VLAN that is one of the VLANs on a trunk port. All originally were 2.13 and upgraded without any issues.
3 x CSS326-24G-2S+
1 x CSS106-5G-1S
1 x CSS106-1G-4P-1S

The only one I have not updated yet is the one CRS326-24G-2S+ because it is at a mountaintop radio site that I can't drive to for another week or two. Although I will update it remotely, I don't want to be in a situation where I can't get to it if there is an upgrade issue.

SUP-145280
SFP+ ports on CRS310-8G+2S+IN does not work or detect modules plugged in

these switches are pretty "standard" as the all have vlan99 added for maintenance and access to the switch only from vlan99.
RSTP disabled and all ports allowing all vlans ...
Not to special

- created backup
- reset to default
switch came back on a dhcp in the generic vlan
- upgrade
- restore backup
and everything back to normal ...

I was able to recreate the issue by just adding the management vlan, that is if I try the upgrade from vlan tagged network it will fail...

Did you have the management interface to be accessible ONLY from VLAN99 ?
(that is what I had on my CSS106-5G-1S switches)

I was able to recreate the issue by just adding the management vlan, that is if I try the upgrade from vlan tagged network it will fail...

Did you have the management interface to be accessible ONLY from VLAN99 ?
(that is what I had on my CSS106-5G-1S switches)

It was VLAN 40 in my case and I didn't set "Allow From VLAN" but anyways the IP address given to the SW could have only been accessed from that VLAN...

no link on SFP+ interfaces on CRS310-8G+2S+IN (SwOS 2.16)!!!!! RouterOS all OK

no link on SFP+ interfaces on CRS310-8G+2S+IN (SwOS 2.16)!!!!! RouterOS all OK

Report with a support case, maybe they will see and solve faster, I also have the same problem.

I am confused by this update: See attached what the SwOS UI of a CRS354-48G-4S+2Q+ shows: System is up to date with 2.13, but also the Changelog of 2.16 is shown. Also 2.17rc2 is listed as the latest available version. If I click on download and upgrade, I get "ERROR: Could not retrieve firmware".

Any ideas what's going on here? The switch got an IP from dhcp, there is definitely a route to the public Internet.

I am confused by this update: See attached what the SwOS UI of a CRS354-48G-4S+2Q+ shows: System is up to date with 2.13, but also the Changelog of 2.16 is shown. Also 2.17rc2 is listed as the latest available version. If I click on download and upgrade, I get "ERROR: Could not retrieve firmware".
Any ideas what's going on here? The switch got an IP from dhcp, there is definitely a route to the public Internet.

2.17rc2 is a version that fixes the SFP+ issue on the CRS310-8G+2S+.
The SwOS updates via your browser, not directly from the swich as far that I'm aware

> The SwOS updates via your browser, not directly from the swich as far that I'm aware

Thanks for your answer! I updated a CRS328-24P-4S+ via Download & Upgrade, so this should actually work.

One POE port powering a third party wireless AP on my CSS106-1G-4P-1S has gone from working fine under 2.13 to reporting a "short circuit" under 2.16.

Nothing else changed in between.

Working -> update -> short circuit (15s later, after reboot)

Anyone else having similar issues? Any suggestions?

I've tried power cycling, but the issue remains the same when it comes back up.

Greetings, great work as always.

I have a problem,

From version 2.13 it wont upgrade on a CRS-317
It shows ...upgrading...rebooting...but it stays on 2.13<

I am confused by this update: See attached what the SwOS UI of a CRS354-48G-4S+2Q+ shows: System is up to date with 2.13, but also the Changelog of 2.16 is shown. Also 2.17rc2 is listed as the latest available version. If I click on download and upgrade, I get "ERROR: Could not retrieve firmware".
Any ideas what's going on here? The switch got an IP from dhcp, there is definitely a route to the public Internet.

2.17rc2 is a version that fixes the SFP+ issue on the CRS310-8G+2S+.
The SwOS updates via your browser, not directly from the swich as far that I'm aware

I would love to test this but unfortunately I am not able to find a download URL for CRS310/2.17rcx2

It automagically was fixed on my switch ;-) ... today it showed 2.16 rather than 2.17rc2 as latest avail version, and I upgraded from 2.13 w/o problems.

It automagically was fixed on my switch ;-) ... today it showed 2.16 rather than 2.17rc2 as latest avail version, and I upgraded from 2.13 w/o problems.

Today i freshly installed 2.16 and unfortunately the SFP+ ports of the CRS310-8G+2S+-IN don't work.

SUP-145280
SFP+ ports on CRS310-8G+2S+IN does not work or detect modules plugged in
Screenshot 2024-02-28 201424.png

What did you made to have a dark appearance?

snmp mib for signals rx power from sfp ports??????????

Version 2.16 has a serious DHCP bug that results in clients no longer connecting. See here: viewtopic.php?t=205504

I've had to roll back to 2.13. Can we get this fixed?

SUP-145280
SFP+ ports on CRS310-8G+2S+IN does not work or detect modules plugged in
Screenshot 2024-02-28 201424.png

What did you made to have a dark appearance?

https://github.com/darkreader/darkreader
darkreader browser plugin. got the same. works well also here in the forum and many other sites

Version 2.17 of SwOS has been released:
viewtopic.php?t=210646