If it doesn’t work… it doesn’t mater what it costs.
Also… they finally admitted there is “just nothing they can do about” busy airtime. So I stopped using their wireless radios.
Routing… Love THEM. ANYTHING ELSE… going to a different vendor.
If it doesn’t work… it doesn’t mater what it costs.
Also… they finally admitted there is “just nothing they can do about” busy airtime. So I stopped using their wireless radios.
Routing… Love THEM. ANYTHING ELSE… going to a different vendor.
Just logging in to say I have the same issues. It caused me 11 hours of downtime for 500 customers when I went out of cell range this last weekend… I guess I will go move the switches off of ports 1-8 until they can fix this.
It’s pretty annoying because I also had issues with the 24 port 10 Gig switch that was just released. That switch would quit working once you put in the 18th SFP module while in SWOS…
I have the same problem. Is the issue resolved in new versions RouterOS?
Wish I had checked this thread before I bought. Running 6.47. The ports 1-8 thing has been a tranwreck for me. Not having SWOS is also a PITA. Takes something that should be beyond simple and turns it into a mistake prone mess. Not being able to see everything laid out in a GUI is far from ideal. Ports 1 thru eight drop at random times. I thought I had a bad switch, got it replaced and same issue on the replacement. So now I had to buy a dfferent brand switch which I did not want because they did not sell anything else I really wanted and I had to use the credit, never mind the hassle of swappint out 3 switches. I started out saving a few bucks and ended up spening more than the SG3xx series switches which I should have stuck with. Tried to register for support and the website never worked. They are cheap but they do not have support either which can cost you. Not sure what support would have done in any case. Ugh… As others have noted, great for routers but not so much for switches, at least this model.
6.48beta5 - 4 days - no problem
agreed, although I moved more critical stuff off those ports I havent seen the issue with 6.48B5.
email support@mikrotik if you want to test the file.
What do you mean by that? To improve stability in a high noise environment you can enable RTS/CTS. You can always fine-tune the wireless interface by adjusting hw-retries, disconnect-timeout, preamble, etc. Additionally, if your board uses Atheros wireless chip, adaptive-noise-immunity is also an option.
If for some reason support form is not working, you can always write an e-mail to support@mikrotik.com
@Reinis thank you for your reply, but that’s kind of off-topic.
Is there some qualified news on the port problem of the CRS354? Because this really gets a problem for me.
We have added a fix for this problem in 6.48beta5, it hasn’t been released to the web yet, if you are experiencing this issue and want to test this version, please contact us at https://help.mikrotik.com/servicedesk/ or via e-mail support@mikrotik.com
update: 6.48beta5 - problem 1-8 port exists ![]()
Oh no… ![]()
Then I can’t install this beta for my customers. I can’t use my productive customers for beta testing.
I get into big trouble with this.
I need a stable fix for this issues asap ![]()
I was going to build a small dataroom with some CRS326-24S+2Q+RM as backbone and CRS354-48G-4S+2Q+RM as access switches for servers…But taking into account the instability, some incompatibility between mikrotik devices, slow support, very slow issues fix, I am thinking to go with other vendor !
I strongly believe that for critical envoronments like datacenters, where uptime is very important, Mikrotik is NO GOOD !
For home users and amateurs, i think their items are great
Support just wrote me:
We also received feedbacks from customers that the problem disappeared with beta versions.
Perhaps these people are encountered with a problem that relates specifically to the 6.48beta5 version.
In version 6.48beta7 added new improvements that also related to CRS354.
+1
i have about 15 pcs of crs354 (with / without POE - both variant ) and one of them have also this issue
no some special setting, just bridge all over interfaces and dhcp-client on that bridge
ros 6.47
+2
another switch started doing that thing
OMG
I am running whole network on these switches, I will kill my self… ![]()
I feel you
I have not that much switches of that type, but the problem is very big ![]()
I was going to build my network with CRS354…but seeing this issues, I am going for other vendor.
Arista refurbished, same price, 10 times better.
no biggie, on many units I can move client to ether 9 or higher
i will wait for fix and if sometime some unit fail again on ports 1-8, just will do restart and show must go on…
my trust on mikrotik is no broken, everyone make mistakes
There is more than a month since clients reported the issue and still no fix. They do not care about the switches. Routers are their priority.
The old series of switches still have issues, that were reported and no fix. Mikrotik decided to take the next step with the new generation.
Reboots are permited once in a while. On of my clients run a hosting business. How can I tell him to reboot every time the switch goes nuts ? ![]()
Yes, for offices and home users, reboots are not a problem.
Update;
routeros-mipsbe-6.48beta5 does not fix issue
while ports are affected per controller (8 sequential ports), its not always ports 1-8, can be 9-16 or 16-24, etc
latest test beta routeros-mipsbe-6.48beta7 was handed out this morning.. will implement and test this evening