Summary
SwOS Lite is an operating system designed specifically for the administration of MikroTik CSS610 series switch products. CSS610 series switches support only SwOS Lite operating system.
The main differences compared to CSS3xx series switches are:
No serial port AFAIK. And no USB for Woobm serial.
Device is more than 1200km from here. (There are 21 of those there.)
I know that RB260 cannot make an IP outgoing connection (it does not do any IP routing, only responding on the same interface to the connecting MAC address).
So what you see about upgrade in the web server of the RB260GSP is actually your PC collecting it from the internet, and framing it in that web-page.
Once it worked (2.12->2.13) this year, then later it did not anymore. Now it failed again and the 2.17 is missing on the MT download website, but the upgrade page talked about 2.17.
The unresponsive “CSS106-1G-4P-1S” is on version “SwOS 2.7” coming from 2.12, according to the “IP Neighbors Discovery” of RouterOS, the only responding request.
Somebody local cut and restored the power on the network for me.
Will not try this again, until the power supply is on an IP controlled power plug (Sonoff style - Switch ON and OFF)
DHCP snooping with Allow from VLAN has a bug on CRS328-24P-4S+ When I want to manage the switch from a tagged VLAN, it’s not working. Everything works fine until I set the trusted ports in DHCP snooping, then connection lost and not able to access the switch anymore.
Please add port names or numbers in the web interface. It’s hard to find the needed port when you have 26 of them. You need to hover a mouse in approximate location first to see a popup with port name and only then you can move to the port more precisely. Very inconvenient and unproductive. I don’t see any problem to add port numbers, there is enough space for that
.
SwOS is rock solid as is, I have some CRS317’s with over 500 days of uptime running on our ISP. The only request that many of us have, is to implement basic security prompts. You can easily press a button on the GUI by accident and bring down an entire network. I had an incident with a tech were he pressed the Boot RouterOS button by accident, and it will just do that without a prompt confirming if you are sure. Also the reboot button won’t ask, and will go for it from a single press. With these basic safeguards in place, and some form of auto backup scheme as well, would make these some VERY reliable switches for large production networks where L3 capabilities are not required.
I have filed this as a feature request, please do so you too so Mikrotik will see that there is a public interest to make their products better with small and easy changes.
Having SWOS switching to RouterOS without asking is just a nightmare for a remotely deployed device.
I’ll take a SwOS MikroTik over any other manufacturer’s “managed” switch any day, but I hope I am not the only one who thinks the slight cost saving for a device that only runs SwOS instead of ROS isn’t worth the limitations. With ROS I can:
Sniff and capture any port
Manage the device via MAC layer and RoMON
Connect to far away ports as if I was locally there, using EoIP (including Netinstall)
Have extensive monitoring and administration via ROS, TheDude and SNMP
