When I read: “fully functional Layer 3 switch” and “full wire speed smart switch” I assumed that I could use the CS125 to link, at full wire speed, via 802.3ad to another device (perhaps an RB951G-2HnD), assuming the linked device supports 802.3ad. I have yet to find a way of doing this without bridging which sends all packets to RouterOS (CPU) for processing effectively nullifying the increased throughput benefits of 802.3ad. I don’t intend on using the CRS125 for DHCP, Firewall, NAT or anything other than switching at this point in time. This is for a home setup and I have no intended use VLANs, unless what I want to accomplish can’t be done without VLANs. Any suggestions are more than welcome.
I’ve reset to a blank config on the CRS125 and configured things as seen below, where ether1 is my uplink from a Ubiquiti EdgeRouter, and then the rest of the ports are all switched. In other words ether2-ether24 are slaves to ether1, and ether1 and wlan1 are bridged.
The issues I’m struggling with are that I cannot bond ports while they are slaves, but I want all ports to be switched except the main uplink from the EdgeRouter (ether1) and the wireless (wlan1) which are bridged. I’m mainly wanting to keep everything on the same broadcast domain instead of segmenting it with VLANs. I am totally open to what suggestions you might have. Please see the diagram I’ve drawn to see what I’m trying to accomplish, although I don’t know if it is plausible. Also feel free to educate me on anything I seem to be doing wrong or could be doing better a different way.
This device is very new and most of us have not had time to play with it yet. I’ve ordered two for a project I’m working on but I won’t have access to them for maybe a week or more.
Perhaps I’m missing something here. Doesn’t that defeat the purpose of having a wirespeed switch that’s capable of 802.3ad? Won’t all packets get processed by the CPU then? This would defeat the purpose of using 802.3ad because now the CPU has to process everything. At best the CPU can probably handle 1Gbps and then what happens to the remainder of the bandwidth I need?
Oh well at least I’m not crazy, although that would have been nice to know a week ago Thank you for the fast response!
Is there any ETA on when 802.3ad will be working as it should with the CRS switch chip? I assume that this is a RouterOS wide issue because it is the same implementation on the RB951G-2HnD, with the exception of the switch chip being different.
Are we able to ask please for you to add notes as you add basic implementations / improve implementations / think they are finished for all these switch chip features (and future new features on MikroTik products.
This would probably be best suited to the Pre Release download pages so we can see the things you have added in or have improved so we can test them in our labs (or our live networks if we are very gutsy) and provide additional feedback.
Would also be great on these pre release pages if a new build fixes any regressions / other glitches from pre release builds as its helpful for me when looking over as sometimes the new build times on the site don’t actually have any new changes in them, I don’t mind at all having short things or oddities that I may not experience as I run the pre release builds in my home network, on my test builds etc and only occasionally try them in the field so it would also help me out with focussing testing on things that have moved since the last build so I can do extra testing for production.
Regards
Alexander
p.s. I have submitted this as a bug in the sense of “enhancement” bugs in open source software
Mikrotik, FYI - I am having issues with the CRS I have been testing. The issue started after upgrading to routerOS 6.7
I have lost ethernet links on all interfaces 3 times. Each time, the router will not get a link on any interface. Once, this happened immediately after upgrading software. Once it happened immediately after disabling an interface. If, while logged in through serial, I type /interface print, it just hangs on that command.
When this happens, I login to the router through the serial port and reset. When it resets, it takes a long time and shows these errors:
[admin@MikroTik] /system> reset
Dangerous! Reset anyway? [y/N]:
y
system configuration will be reset
Rebooting…
Stopping services…
failed to stop racoon: std failure: timeout (13)
failed to stop ppp: std failure: timeout (13)
ar7100_wdt_disable
failed to stop route: std failure: timeout (13)
I’m still experiencing the same problem as others after upgrading to this version. The router works, then all of the Ethernet ports stop working. Sometimes it will work for a week and other times for a day. I have eliminated all of the configuration using it only as a dumb switch as well as running it with the default configuration. Results are always the same; it works, then it doesn’t. Doing a factory reset always resolves the problem, however the switch is useless because it is only a matter of time before it stops working.
I deployed a CRS125 and I’m afraid I’m going to have to pull it out. It’s behaving extremely erratically. Not all ports will negotiate. A second IP address assigned to the switch group does not respond to pings. I’ve reset the software once and it’s still acting unlike a RouterOS device should.
Any update on the hardware LACP/port aggregation on the CRS125? Any approximates/timeframes?
I was thinking of it as an inexpensive alternative to other wirespeed L2 GigE switches and potentially as an all-in-one hardware L2/software L3 swouter but it is disappointingly not fit yet.
Thank you for the fast response! 