CSS610-8G-2S+ Management Access from SFP+ Port

MiseryOne · Wed Oct 21, 2020 6:21 pm

Hey everyone,

I recently got my CSS610-8G-2S+ switch and its running great so far.

Yesterday I connected my servers via SFP+ RJ45 modules and removed their 1G links but after doing that, I could no longer the management website of the switch from the servers. If I move the cable to a normal RJ45 Port it works again. I also checked port isolation, nothing configured there and the "Allow from Ports" setting in the general tab, but all is default there - access to management from every port. A reset to default etc. didn't change the problem. My CSS610-8G-2S+ is running 2.12rc2.

Can anyone of you, also owning that switch, try if you have the same issue?

thanks
MiseryOne

AvAxxCZ · Thu Oct 22, 2020 11:38 am

Hello
Same issue

I contacted technical support:
Description:

Problem: It is not possible comunicate with device CSS610-8G-2S+ through
SFP+ ports (I,II) [Mikrotik S+RJ10 /r2]. Web interface is inaccesible, PING to
device failed, (DHCP lease failed) and static IP on the device do the same.
Standard 1G ports 1-8 works correctly (DHCP/PING/WEB). Switching between
ports 1-8 / SFP+ I,II (vice versa) always working well.

Answer SUP-30842 :

Hello,

Thank you for the report!

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming SwOS versions, unfortunately, I cannot comment on the version availability.

wojrep · Thu Oct 22, 2020 3:49 pm

I have this problem too. It's good to know that Mikrotik Support will be working on it. I have yet seen that many people report a problem with the vlan configuration, I haven't tried it yet, I will wait for the new SwOS, maybe there will be less nerves.

MiseryOne · Thu Oct 22, 2020 6:16 pm

Hello
Same issue

I contacted technical support:
Description:

Problem: It is not possible comunicate with device CSS610-8G-2S+ through
SFP+ ports (I,II) [Mikrotik S+RJ10 /r2]. Web interface is inaccesible, PING to
device failed, (DHCP lease failed) and static IP on the device do the same.
Standard 1G ports 1-8 works correctly (DHCP/PING/WEB). Switching between
ports 1-8 / SFP+ I,II (vice versa) always working well.

Answer SUP-30842 :
Hello,

Thank you for the report!

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming SwOS versions, unfortunately, I cannot comment on the version availability.

Ahhh Thank's for that info. I already thought I did something wrong. Not a big issue at the moment, but great that they will fix it.

nagylzs · Thu Oct 22, 2020 8:45 pm

> Can anyone of you, also owning that switch, try if you have the same issue?

I can also confirm this problem. I just plugged in two identical CSS610-8G-2S+ switches, connected them via SPF+. I can access both of their web interfaces through RJ45 port, but not with SFP+ port.

nagylzs · Thu Oct 22, 2020 11:28 pm

It is not just the management interface. It seems that DCHP client is also affected. On the DHCP server side I see that address was "offered" to the switch, but the switch is not bound to the offered address.

wojrep · Thu Oct 29, 2020 8:50 am

I got the following responses from MikroTik:

A similar issue has been observed also in our labs and we look forward to fixing it on upcoming SwOS versions, unfortunately,
I cannot provide an ETA now.

and

Unfortunately, I cannot share any details regarding software availability. My apologies for the caused inconvenience.

nagylzs · Fri Oct 30, 2020 9:37 am

Well, I bought these units for a concrete installation, and now I'm not able to use them. I have a deadline. Since they cannot tell when it will be fixed, I have to use something else.

When I bought them, I did not know that web management and DHCP client won't work on SPF+ port. It also turned out the VLAN is not working normally.

Are these covered by the manufacturer's warranty?

angelspire · Wed Nov 04, 2020 7:49 am

Bump. Same with CSS610-1Gi-7R-2S+ and RB4011iGS+RM

When connected via SFP+ it works pretty much like unmanaged switch. And only in DHCP mode.

Configurations tested:

All configurations assume default router config with IP changed to 10.0.1.1 and DHCP address space to 10.0.1.101 - 10.0.1.254. Client IP set to 10.0.1.50 manual.

Case 1: Switch configured to "Static only" with IP: 10.0.1.100. Switch connected to Router vis SFP+
- switch can be accessed when client plugged into switch
- router (10.0.1.1) can't be accessed from client when client plugged into switch
- switch can't be accessed via IP address when client plugged into router
- resources connected to router are NOT accessible from client, connected to switch
- resources connected to switch are NOT accessible from client, connected to router

Case 2: Switch configured with "DHCP only" or "DHCP with fallback". Switch connected to Router vis SFP+
- switch can NOT be accessed when client plugged into switch
- router can be accessed when client plugged into switch
- switch can NOT be accessed when client plugged into router
- router can be accessed when client plugged into router
- resources connected to router are accessible from client, connected to switch
- resources connected to switch are accessible from client, connected to router

Case 3: Any switch configuration. Switch connected to router via ethernet
- both admin UIs are accessible when client connected to either box
- all resources are available when client connected to either box

leopardus2 · Tue Nov 10, 2020 4:07 pm

Same here. Really annoying.

nannou9 · Tue Nov 10, 2020 9:58 pm

Same problem. Took me few hours of wondering what am I doing wrong before I found this.
Agree. Quite annoying as my networks are connecting to this switch through sfp.

norepto · Wed Nov 11, 2020 2:14 pm

Same problem... I have 33 new units of this model. My dead line is in 7 days. If i don't have any solution i go to return the units.

leopardus2 · Wed Nov 11, 2020 2:22 pm

Same problem... I have 33 new units of this model. My dead line is in 7 days. If i don't have any solution i go to return the units.

return them so Mikrotik support will learn what you get when someone submits a very annoying (and easy to fix) bug and their answer is "NO ETA"

norepto · Wed Nov 11, 2020 2:36 pm

Same problem... I have 33 new units of this model. My dead line is in 7 days. If i don't have any solution i go to return the units.
return them so Mikrotik support will learn what you get when someone submits a very annoying (and easy to fix) bug and their answer is "NO ETA"

In the last 10 Years we spend in MKT devices more than € 250,000. Sometimes we had some problems but never something as obvious as this. Aswell we work with Huawei, Ruckus, Netgear, Mimosa, Silvus.... I don't normally buy switches from MKT and now I know I did it right.

norepto · Wed Nov 11, 2020 2:53 pm

Hello
Same issue

I contacted technical support:
Description:

Problem: It is not possible comunicate with device CSS610-8G-2S+ through
SFP+ ports (I,II) [Mikrotik S+RJ10 /r2]. Web interface is inaccesible, PING to
device failed, (DHCP lease failed) and static IP on the device do the same.
Standard 1G ports 1-8 works correctly (DHCP/PING/WEB). Switching between
ports 1-8 / SFP+ I,II (vice versa) always working well.

Answer SUP-30842 :
Hello,

Thank you for the report!

We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming SwOS versions, unfortunately, I cannot comment on the version availability.

Ahhh Thank's for that info. I already thought I did something wrong. Not a big issue at the moment, but great that they will fix it.

It think is a big issue... If do you have 33 units in a ring using the SFP+ ports and you can not manage it.

angelspire · Wed Nov 11, 2020 5:23 pm

Guys, seriously? This is NEW product. Not really tested by earth and fire. If you're planning a commercial install based on an untested product - it's not MKT problem, it's your risk management. Go check Cisco forums for new products they release. Give folks some slack.

Again, you wanted a cool shiny new thingie? Wanna pay a fraction of what you'd pay for Cisco? Be ready to deal with early adopter issues.

To Mikrotik team - you guys are doing great, keep pushing.

And maybe after you resolve this you could think of replacing "G" with "P" in this product name? Having PoE+ for this switch will truly make it THE instant classic :)

leopardus2 · Wed Nov 11, 2020 5:51 pm

Guys, seriously? This is NEW product. Not really tested by earth and fire. If you're planning a commercial install based on an untested product - it's not MKT problem, it's your risk management.

you missed the point completely
bugs do exist, in any product, new or not new.
what we are criticizing is support's answer to the request to fix a bug which should be trivial to fix
for these, Cisco used to deliver us custom builds back then when I was a customer.

norepto · Thu Nov 12, 2020 11:08 am

Guys, seriously? This is NEW product. Not really tested by earth and fire. If you're planning a commercial install based on an untested product - it's not MKT problem, it's your risk management.
you missed the point completely
bugs do exist, in any product, new or not new.
what we are criticizing is support's answer to the request to fix a bug which should be trivial to fix
for these, Cisco used to deliver us custom builds back then when I was a customer.

Totally agree. As you say, sometimes there are bugs. The strange thing is this type of error and the support that MKT provides. It's so strange that they didn't test it before launching it. On a managed switch I think this is the first point to check because... Do you want to be able to manage it? LOL.

nagylzs · Fri Nov 13, 2020 5:56 pm

This is like selling a car that has no wheels. We may classify this problem as a "software bug". But this is an obvious fault, and the product could never work with the simplest configuration.

leopardus2 · Fri Nov 13, 2020 6:33 pm

Well I canceled mine, I believe many people will do the same.

norepto · Mon Nov 16, 2020 12:59 pm

Hi all,

I was in contact with MKT support. They had email me with a RC release. It works and i can manage the switch by the SFP+ but i'm waiting for a final release with the corrected bug...

leopardus2 · Mon Nov 16, 2020 1:18 pm

Can you please share the RC somewhere?

norepto · Mon Nov 16, 2020 2:25 pm

Can you please share the RC somewhere?

Hi,

I go to ask MKT support first if i can share de direct link from them or i can share by my self....

leopardus2 · Mon Nov 16, 2020 3:29 pm

thanks. I canceled my order for 2 of them but already got one, so I can use that.

Mon Nov 16, 2020 4:36 pm

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device:
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

And for the netPower Lite 7R (CSS610-1Gi-7R-2S+) device:
https://box.mikrotik.com/f/089b908aede040b099c8/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

leopardus2 · Mon Nov 16, 2020 4:39 pm

Thanks. Appreciate it.

norepto · Mon Nov 16, 2020 7:07 pm

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device.
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

TY

bikerrich · Wed Nov 18, 2020 10:48 pm

This is like selling a car that has no wheels. We may classify this problem as a "software bug". But this is an obvious fault, and the product could never work with the simplest configuration.

You're not wrong. Just got 2 of these and the main thing people will use the SFP's for is to do 10G back-haul to a main switch not testing that management access works over the SFP is pretty poor

norepto · Thu Nov 19, 2020 11:26 am

Hi all,

Now i can manage the devices but icmp to IP of the device is very unstable...

AvAxxCZ · Thu Nov 19, 2020 12:54 pm

I know and understand it's the rc5 version, but here are my observations

device unstable response (ICMP)

+

lazy web interface (often you need to refresh the page to retrieve tab content)

Just for the record, Mikrotik introduced SwOS Lite

marekm · Thu Nov 19, 2020 1:44 pm

Has anyone with some electronics knowledge tried to open the CRS318-16P-2S+OUT to see inside if its PoE-out ports could be modded for use as PoE-in?
It's more expensive but runs proper RouterOS and just works, power consumption could be an issue though (would probably need 48V PoE-in).

I've done a similar mod for 24V reverse-PoE-in on a much smaller device (OmnitikUPA - old one with 802.11n and 10/100 ports), it was just adding 4 diodes (used 2 dual schottky diodes in isolated TO220, anodes to pins 4,5 of each port 2-5, common cathode to "+" of DC input jack - which becomes an output in case you need to power something non-PoE, I haven't used it).
PoE-out ports 2-5 have diodes in series, so simply applying power (without the mod) does nothing (no current flow, no damage).
Ports used as PoE-in must be set to PoE-out "off" of course - in my case ports 1-4 are used as PoE-in and port 5 as PoE-out powering the uplink radio.

soporte_tecnico · Fri Nov 20, 2020 3:23 am

we are having the same problem cannot be accessed from the sfp ports, they do not have connectivity from the sfp port among other CCS610, we bought more than 25 and I am waiting for the resolution of Mikrotik I follow the thread.

bikerrich · Fri Nov 20, 2020 11:10 am

we are having the same problem cannot be accessed from the sfp ports, they do not have connectivity from the sfp port among other CCS610, we bought more than 25 and I am waiting for the resolution of Mikrotik I follow the thread.

r5 definitely allows access over SFP however the switch doesn't seem to be able to re-negotiate lower link speeds with copper 10G Mikrotik SFP modules. I have these renegotiating fine between a Mikrotik RouterOS device to a Zyxel XGS switch where they will happily renegotiate at 2.5G or 5G if the cable or length is not good enough but the CCS610 only want to do 10G or nothing. It looks like there are quite a few bugs left in SwitchOS to fix....

aurelepavia · Fri Nov 20, 2020 1:38 pm

Hello
on a css610 I configured port 1 in the lab as a trunk with 5 vlans and I configured 5 access ports on each vlan - on port 1 I connected a mikrotik router which delivers me the vlan and the associated dhcps - I can't get the vlans to transit - I followed the procedure step by step I don't see where the problem is - can you help me
I checked with a sw cisco that the router was correctly configured it's correct - my problem is of course on the css

angelspire · Fri Nov 20, 2020 10:28 pm

Trying to install r5 - fails with error that bad firmware file. Tried both from webfig and winbox. Any hints?

msimmons · Sat Nov 21, 2020 12:23 am

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device.
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

You got this for the NetPower 7R Lite?

Mon Nov 23, 2020 4:21 pm

I edited my first post and added a download link for the netPower Lite 7R, see above.

sterling · Mon Nov 23, 2020 11:52 pm

Thanks for providing us with further RC candidates.

I've got 8 units now, and just was notified that my backorder of 20 units from Baltic Networks has shipped.
So I'm coming to the point where I would like to have a known good release version soon!

msimmons · Tue Nov 24, 2020 4:57 am

I edited my first post and added a download link for the netPower Lite 7R, see above.

Thank you, sir!

However, It doesn't seem to be taking on my unit running 2.12rc2. It doesn't give me any errors, it just briefly says upgrading, then the page automatically refreshes and nothing happens or upgrades. Thanks.

angelspire · Tue Nov 24, 2020 10:01 pm

Same case for me. Shutting it off and powering back helped solving this issue. Also, make sure you use firmware for your specific device. I.e. CSS610-8G-2S+ and CSS610-1Gi-7R-2S+ are not cross-compatible.

nannou9 · Wed Nov 25, 2020 1:31 am

Big thanks to Mikrotik!

msimmons · Thu Nov 26, 2020 12:02 am

Same case for me. Shutting it off and powering back helped solving this issue. Also, make sure you use firmware for your specific device. I.e. CSS610-8G-2S+ and CSS610-1Gi-7R-2S+ are not cross-compatible.

A power cycle finished the upgrade. Thanks.

localnetplus · Thu Nov 26, 2020 4:14 am

I upgraded to rc5 and I still can't manage with the SFP+ port active. I have to unplug the fiber from the SFP and plug in the cat 6. Very frustrating. DHCP still doesn't work very well either.

aitidina · Thu Nov 26, 2020 10:48 am

I've rarely worked with mikrotik devices, but I just bought 3 of these and upon tinkering, I found this same problem. I'm glad it's already being worked on. Unlike many of you, I don't have any deadline and this is more of a learning project, but it would have nonethelessly bothered me to have to setup another port for management. Just wanted to thank you people who already have complained to Mikrotik about the problem.

soporte_tecnico · Fri Nov 27, 2020 9:50 pm

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device:
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

And for the netPower Lite 7R (CSS610-1Gi-7R-2S+) device:
https://box.mikrotik.com/f/089b908aede040b099c8/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

works with this version but with different hardware equipment, if the CSS610 equipment is not connected

bikerrich · Wed Dec 09, 2020 9:21 pm

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device:
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

And for the netPower Lite 7R (CSS610-1Gi-7R-2S+) device:
https://box.mikrotik.com/f/089b908aede040b099c8/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

Is there any movement on a release version that fixes the various bugs - I have a couple of these that I would like to deploy but until the major bug(s) like management access over SFP are fixed they're not really a viable option as everyone wants to do 10G segment back haul. rc5 seems to occasionally work over SFP but then mainly not. At the moment the only way I can manage the device is by having a Raspberry Pi in a LAN port and doing an SSH port forward to the switch. It's weird as it looks like traffic switching works fine but management traffic routing seems really broken.

wojrep · Thu Dec 10, 2020 8:35 am

I guess you have to be very patient ... I have the same problem, but the support's answer does not show that it quickly solves the problem definitively.
Recently, there are many problems with the new MikroTik models.

marekm · Fri Dec 11, 2020 1:49 am

Waiting for the updated firmware, too. I have a few netPower 7R switches which I'm waiting until fixed to install.
Firmware upgrade of a reverse-PoE switch should not need a power cycle. With redundant power from a few customers, it's difficult to ask all of them to power-cycle their PoE at the same time - or ask the electric power company to power-cycle the whole area ;)
Perhaps such devices should have some independent way to remotely power-cycle - just a thought, use a cheap esp8266 wifi-controlled relay module?

gateff · Mon Dec 14, 2020 9:39 am

I have a login loop issue with that model and mozilla firefox 78.5.0 esr (can not try different browser at the moment). Help!
Edit: no problems with SwOS 2.13rc5 so far

soporte_tecnico · Tue Dec 15, 2020 12:07 am

someone has version 2.12 update to 2.13rc but I don't like the results, where can I find version 2.12 to go back to the previous one, thank you very much.

cwachs · Mon Dec 21, 2020 1:08 am

Looks like VLANs are still totally broken with 2.13rc5 firmware. Makes this unusable for us in production. While I get this is a new product, switches are not new to Mikrotik and having a switch product leave the production line with no VLAN support at all is ridiculous. That is not a new product bug, that is rushing something out the door when you know it has limitations but not mentioning that in any documentation. I would never expect a Mikrotik product to arrive without a basic feature like VLAN support in a switch not working.

bikerrich · Mon Dec 21, 2020 9:32 am

Looks like VLANs are still totally broken with 2.13rc5 firmware. Makes this unusable for us in production. While I get this is a new product, switches are not new to Mikrotik and having a switch product leave the production line with no VLAN support at all is ridiculous. That is not a new product bug, that is rushing something out the door when you know it has limitations but not mentioning that in any documentation. I would never expect a Mikrotik product to arrive without a basic feature like VLAN support in a switch not working.

Well said, likewise I also realise it's a new product but releasing something with release candidate firmware with so many bugs is just not on.

Mikrotik this device is unusable for production environments and we have been waiting weeks for some release firmware to fix the issues - why the delay?

spippan · Mon Dec 21, 2020 11:08 pm

various bugs on getting basic functionallity ... for example setting the MANAGEMENT VLAN and handling a "hybrid config" on the 2 SFP+ ports so tagged AND untagged (native) traffic is handled correctly. working on the 8 ethernet interfaces but not on the SFP+ ports

it would be a perfect replacement for some overprived cisco and HP switches but only if basic VLAN performance is given!
sadly disappointed with this incestment :-(

spippan · Mon Dec 21, 2020 11:19 pm

It is not just the management interface. It seems that DCHP client is also affected. On the DHCP server side I see that address was "offered" to the switch, but the switch is not bound to the offered address.

same issue observed here. DHCP server is a routerboard 922
also it is not possible to configure these ports to handle tagged traffic (trunk) and also untagged traffic (native/pvid) at the same time.
which, in the cisco world, would look like something like

interface Te1/0/1
  switchport mode trunk
  switchport trunk native vlan 10
  switchport trunk allowed vlans 10,20,30
  spanning-tree port type edge

--> which leaves TAGGED frames unchanged in their respected VLANs (egress + ingress) and all UNTAGGED frames would go to VLAN10 ingress and UNTAGGED egress! one hell of a basic VLAN configuration

also i would like to FINALLY have SSH access to SwOS! please mikrotik, let this happen!

JJT211 · Sat Jan 02, 2021 9:31 am

BUMP

Anxiously waiting on basic VLAN support. I dont even care about the SFP issue. Just get the VLAN issue working ASAP. Ill take another rc firmware. As long as we at least have VLANS

wojrep · Sat Jan 02, 2021 9:41 am

Bad things happen at MikroTik, a product released for sale without a basic functional check. It is a great shame ... and even bigger is a long wait for a correction.

They are selling "beta" hardware and we are still paying a lot of money to test everything for them !!!

JJT211 · Sun Jan 03, 2021 8:23 pm

Agreed, the LONG wait makes it that much worse. This is going on 3+ months now right? How hard is it to fix basic VLAN functionailty? I wonder if its some core hardware issue. If thats the case, why are they still selling it? If not, and giving the development team the benefit of the doubt, its a allocation of resources issue. This switch is very far down on there priority list. Which is shame.

As far as im aware, the Netpower 7R is the only switch of its kind. I need something ASAP. Anyone know of another switch that can do reverse POE with gigabit ports??

marekm · Mon Jan 04, 2021 10:06 am

If 10Gb not required (just 2x 1Gb SFP, 7x gigabit PoE-in, 1x gigabit PoE-out), there are no-name Chinese boards you can put in your own box.
I have been using these after Netpower series was announced by MT, but I got tired of waiting for its real avaiability (a year later, only 10/100 ports)
Pros: working reverse-PoE gigabit switch with standard VLAN functionality
Cons: you have to roll your own weatherproof box (doesn't look as nice), import from China (long wait, no invoice), probably no future firmware updates

Another option (where you also need to roll your own box), with more SFP ports: CRS112-8P-4S-IN should be easy to modify for reverse-PoE (solder a few diodes on the separate PoE board)

nannou9 · Wed Jan 06, 2021 1:14 am

Accessing admin via sfp on 2.13rc5 usually doesn’t work for me. I gave up on it and I vpn to edge router to access it. Or connect physically to eth ports.

I’ve got my vlans working however.
This thread was helpful viewtopic.php?f=17&t=168532

sterling · Wed Jan 06, 2021 2:21 am

I loaded a CSS610-1G-7R-2S+, and a CSS610-8G-2S+ with the 2.13.rc5 SWOS (respectively).

I STILL cannot get it to pick up a management IP via VLAN.
It just picks up the regular vlan1 DHCP assigned ID and I can access it from any port.

I have management subnet on VLAN 400 handed out by DHCP.
If it go in to the CSS interface and change Allow from VLAN and put 400 in there, it appears to do absolutely nothing.

I added VLAN 400 to the VLANs tab with defaults all members, and STILL gets vlan1 dhcp IP, not management 400 IP.

Is there something else I need to be doing??

Or is this still broken in this RC5 version??

cwachs · Wed Jan 06, 2021 2:27 am

We got VLAN support working in RC6.

angelspire · Wed Jan 06, 2021 2:33 am

Where did you get rc6?

sterling · Wed Jan 06, 2021 2:36 am

Yes, where is RC6? I'll try it out if someone can link it here.

cwachs · Wed Jan 06, 2021 2:59 am

Support sent me a copy.

JJT211 · Wed Jan 06, 2021 7:51 am

We got VLAN support working in RC6.

Nice, thanks for the heads up!! Thats all I really need!

EDIT: Just stumbled upon below support response from another thread. Got my VLANs working now

First, try to disable the "Add Information Option" under the System menu.
For access or untagged ports, use "VLAN Mode = optional", "VLAN Receive = only untagged" and specify the "Default VLAN ID". For the trunk or tagged ports, use "VLAN Mode = strict", "VLAN Receive = only tagged". And make sure to include all the necessary member ports for each VLAN ID under the VLANs menu.
[...]
The wiki manuals will get updated, thank you for pointing this out. We are still working on a new SwOS version for CSS610 devices, but I cannot predict when this version will be available.

JJT211 · Thu Jan 07, 2021 6:05 am

Support sent me a copy.

I tried contacting support and theyre stonewalling me. Which switch did you get the RC6 version from? CSS610-7R (netpower) or the CSS610-8G-2S+ ?? If you have the Netpower firmware, could you email it over?

gintarasp2 · Thu Jan 07, 2021 8:40 am

Support sent me a copy.
I tried contacting support and theyre stonewalling me. Which switch did you get the RC6 version from? CSS610-7R (netpower) or the CSS610-8G-2S+ ?? If you have the Netpower firmware, could you email it over?

Completely the same here.
They said wait for it to be published on the web.

sterling · Thu Jan 07, 2021 8:59 pm

Great... I guess we'll sit on our inventory of 40+ units until they pull their heads out of their ass(es) collectively speaking.

I mean really, sending out a product without a viable config solution that is their "standard"?

Who ISN'T programming these on a management VLAN separate from the main/customer default vlan??

leopardus2 · Thu Jan 07, 2021 9:23 pm

I upgraded to rc5 and I still can't manage with the SFP+ port active. I have to unplug the fiber from the SFP and plug in the cat 6. Very frustrating. DHCP still doesn't work very well either.

same here. rc5 did not fix the problem for me.

msimmons · Sat Jan 09, 2021 12:21 am

Support sent me a copy.

Would love to try RC6. You mind sending it over since MikroTik won't?

cwachs · Sat Jan 09, 2021 1:27 am

https://box.mikrotik.com/f/a72e315282d149eda481/?dl=1

There is the link they sent me for RC6. I guess if they object to this, they can delete this post. Since it is from their servers and they willingly sent me the link, I hope it is OK to put it here. I guess I should state this is a release candidate, not a stable firmware and is for testing only.

sterling · Sat Jan 09, 2021 1:32 am

Nice.

Did they give you a link to the css610g version as well?

cwachs · Sat Jan 09, 2021 1:34 am

No, I only am running the NetPower 7 so that is the only one I needed a firmware for.

JJT211 · Sun Jan 10, 2021 9:46 pm

https://box.mikrotik.com/f/a72e315282d149eda481/?dl=1

There is the link they sent me for RC6. I guess if they object to this, they can delete this post. Since it is from their servers and they willingly sent me the link, I hope it is OK to put it here. I guess I should state this is a release candidate, not a stable firmware and is for testing only.

Nice!! Thank you sir!

norepto · Tue Jan 12, 2021 11:43 am

Any news?

gintarasp2 · Tue Jan 12, 2021 12:10 pm

Any news?

O: Hello,
Thank you for contacting MikroTik Support.
Please wait for it to be released to our web page. Thank you!
Best regards,

G:Hello O,
Any idea when this will happen?

O:Hello,
Unfortunately, we do not have ETD for this. Sorry for the inconvenience caused.
Best regards,
O.

From what I learned I will not buy or recommend any Mikrotik device when it is realeased prior to checking forums for bugs reported by the end users.
Feels like early access game. And that is a damn shame.

Tue Jan 12, 2021 1:29 pm

We have created a new testing version (rc6) which addresses some of the VLAN related problems, but the management connection from the SFP+ port is still being investigated. In some cases, it might help if you disable the RSTP on SFP+ ports and reboot the switch, but make sure there is no L2 loop on these ports. Let us know the results.

As for the VLANs, I would suggest trying these settings:
- Disable the "Add Information Option" under the System menu
- For access or untagged ports, use "VLAN Mode = optional", "VLAN Receive = only untagged" and specify the "Default VLAN ID".
- For the trunk or tagged ports, use "VLAN Mode = strict", "VLAN Receive = only tagged".
- Make sure to include all the necessary member ports for each VLAN ID under the VLANs menu.

In case you are using tagged VLAN for the device management, I would also recommend using a static IP configuration:
- Set "Address Acquisition = static" and configure "Static IP Address = x.x.x.x".

The rc6 version still contains some VLAN issues (e.g. when using "Allow From VLAN" or enabling "Add Information Option" in the System menu), so I would first suggest trying the above configuration. If you are still interested in upgrading, below are the latest testing versions:
for CSS610-8G-2S+ https://box.mikrotik.com/f/5daa1f8f216a4045b776/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/a72e315282d149eda481/?dl=1

gintarasp2 · Tue Jan 12, 2021 2:06 pm

We have created a new testing version (rc6) which addresses some of the VLAN related problems, but the management connection from the SFP+ port is still being investigated. In some cases, it might help if you disable the RSTP on SFP+ ports and reboot the switch, but make sure there is no L2 loop on these ports. Let us know the results.

As for the VLANs, I would suggest trying these settings:
- Disable the "Add Information Option" under the System menu
- For access or untagged ports, use "VLAN Mode = optional", "VLAN Receive = only untagged" and specify the "Default VLAN ID".
- For the trunk or tagged ports, use "VLAN Mode = strict", "VLAN Receive = only tagged".
- Make sure to include all the necessary member ports for each VLAN ID under the VLANs menu.

In case you are using tagged VLAN for the device management, I would also recommend using a static IP configuration:
- Set "Address Acquisition = static" and configure "Static IP Address = x.x.x.x".

The rc6 version still contains some VLAN issues (e.g. when using "Allow From VLAN" or enabling "Add Information Option" in the System menu), so I would first suggest trying the above configuration. If you are still interested in upgrading, below are the latest testing versions:
for CSS610-8G-2S+ https://box.mikrotik.com/f/5daa1f8f216a4045b776/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/a72e315282d149eda481/?dl=1

Why would you ship a product with issues like this?

nannou9 · Tue Jan 12, 2021 5:30 pm

Disabling rstp on sfp port makes the admin working well for me.
Thanks for this workaround.I

sterling · Tue Jan 12, 2021 8:13 pm

Thanks for posting that EdPa (support) in this thread, that is very helpful.

I will do some testing with the code and suggestions to see if this works for us for our management scenario.

JJT211 · Wed Jan 13, 2021 8:40 am

It is what it is everyone.

Thanks EdPA for sharing info and latest RC. I do have my VLANs working now with some brief testing.

gintarasp2 · Wed Jan 13, 2021 5:04 pm

It is what it is everyone.

Thanks EdPA for sharing info and latest RC. I do have my VLANs working now with some brief testing.

Seems like VLANs work yet I do not get dhcp from it. Do you get DHCP leases for VLANs?

nannou9 · Wed Jan 13, 2021 7:48 pm

DHCP client for MikroTik devices doesn’t work for me somehow, have all addresses static on my mix of css610 and crs305.
But it works for devices attached to them- untagged traffic, so does the minimum required.

gintarasp2 · Thu Jan 14, 2021 9:03 am

DHCP client for MikroTik devices doesn’t work for me somehow, have all addresses static on my mix of css610 and crs305.
But it works for devices attached to them- untagged traffic, so does the minimum required.

Well fo my device DHCP client worked, but for access ports DHCP does not :D

kaeferfreund · Thu Jan 14, 2021 9:22 am

I observed the same behavior:

Communication via VLANs basically works with 2.13rc6 but DHCP does not work. The Clients do not get IP-Addresses via VLAN.

In my case I cascaded (topology doesn't allow any other solution) two MikroTik devices: CRS326 and CSS610.

When I connect to the CRS326 directly, VLANs work fine an I get an IP address from the DHCP server. But with the CSS610 that's not the case. Static IPs work as expected for me.

@EdPa Can you guys look into this as well? I'm quite confident, that this is no configuration issue, but rather a firmware issue as I have installed over 200 Mikrotik devices in 2020 an many of them run VLANs 24/7. I can reproduce the behavior with all 5 CSS610 devices I have at our lab.

Thu Jan 14, 2021 9:37 am

Does the DHCP still fail, when you disable the "Add Information Option" in the System menu?

kaeferfreund · Thu Jan 14, 2021 10:51 am

Jepp, just retested. DHCP on IPv4 still fails. On IPv6 it works with the option off. Strange thing^^

JJT211 · Fri Jan 15, 2021 5:43 pm

Yea, DHCP still doesn't work for me. You have to set a static

bikerrich · Sat Jan 16, 2021 1:32 pm

Disabling rstp on sfp port makes the admin working well for me.
Thanks for this workaround.I

That's annoying i need to use RSTP for Sonos' - come on Mikrotik can you get some engineering time to work on this hardware I've got 2 that I want to deploy but good hardware is being ruined by awful software.

Standard · Sun Jan 17, 2021 11:23 pm

Hello,

I'd like to share my experience with CSS610-8G-2S+.

I managed to make vlan + ipv4 dhcp + management access from sfp+ working.

Maybe it's not the best solution for you, but with DAC cable on sfp+ (with vlan trunk) magagement works great, with the RC5 firmware, and without disabling RSTP.
Obviously with a 10GB base T module (with vlan trunk), it's not as great, but it also works by disabling RSTP on the port as you already know.

With a 10GB base T module without vlan it works great without disabling RSTP.

About VLAN, myc conf is close to what EdPa explained on "Tue Jan 12, 2021 1:29 pm", but it works for me with RC5 firmware.
I have multiple VLANs with one DHCP server per VLAN and every client gets its IPv4 from the correct DHCP.

You obviously have to disable "Add Information Option" and check trusted ports to make it works (and have a static IP for the Switch is better).

I didn't test the RC6 firmware yet as everything works for me.

I 'll wait for a stable version.

Joebar16 · Mon Jan 18, 2021 8:10 pm

Hi,
I switched to Mikrotik product last month with 3 CSS610-8G-2S+ and 1 CRS309-1G-8S+
First tests with SFP+ and copper network. It worked great.
When I switched to fiber as planned ... Inaccessible switches. Outch !
While searching, I discovered this thread.

Support response today with a new RC version of the firmware I passed :

Please upgrade CSS610 to SwOS Lite v2.13rc10 from the link and check if previously experienced problems remain.
https://box.mikrotik.com/f/9c2a7656ab554dd397e1/?dl=1

As seen in previous posts, I hope not to upset Mikrotik by giving this link. I think it's useful to the community!

The switches are correctly viewed, accessible for management by SFP+ fiber (MikroTik S+85DLC03D) Great !
No special modification for RSTP.
I am not using VLAN. I couldn't make any returns. I know there are quite a few worries too!
It is worth testing it for those who are in wait.

Is it better for you too?

kaeferfreund · Mon Jan 18, 2021 8:14 pm

as this is now advertised here:
https://www.youtube.com/watch?v=Xh3oQKcMOmg

I hope, things get leveled up in priority.

@EdPa
BTW: Genius move to connect the metal housing on the bottom for cooling. My RJ45 transrecievers are getting way better temps than in my css326-24g-2s+rm

Will this model (css326-24g-2s+rm) be updated with the same cooling trick? I had a LOT of trouble with using RJ45 transrecievers of various brands with this particular model. I know this is not advertised or recommended and no longer use any RJ45 trans with it. But with the CSS610-8G-2S+ that works remarkably well!

I think many people would be more than happy to pay extra for this feature

gintarasp2 · Tue Jan 19, 2021 8:51 am

as this is now advertised here:
https://www.youtube.com/watch?v=Xh3oQKcMOmg

I hope, things get leveled up in priority.

@EdPa
BTW: Genius move to connect the metal housing on the bottom for cooling. My RJ45 transrecievers are getting way better temps than in my css326-24g-2s+rm

Will this model (css326-24g-2s+rm) be updated with the same cooling trick? I had a LOT of trouble with using RJ45 transrecievers of various brands with this particular model. I know this is not advertised or recommended and no longer use any RJ45 trans with it. But with the CSS610-8G-2S+ that works remarkably well!

I think many people would be more than happy to pay extra for this feature

If you check this Youtuber's comments, you'll see that he encountered the same issues. More details in his web.

bikerrich · Tue Jan 19, 2021 12:14 pm

Hi,
I switched to Mikrotik product last month with 3 CSS610-8G-2S+ and 1 CRS309-1G-8S+
First tests with SFP+ and copper network. It worked great.
When I switched to fiber as planned ... Inaccessible switches. Outch !
While searching, I discovered this thread.

Support response today with a new RC version of the firmware I passed :
Please upgrade CSS610 to SwOS Lite v2.13rc10 from the link and check if previously experienced problems remain.
https://box.mikrotik.com/f/9c2a7656ab554dd397e1/?dl=1
As seen in previous posts, I hope not to upset Mikrotik by giving this link. I think it's useful to the community!

The switches are correctly viewed, accessible for management by SFP+ fiber (MikroTik S+85DLC03D) Great !
No special modification for RSTP.
I am not using VLAN. I couldn't make any returns. I know there are quite a few worries too!
It is worth testing it for those who are in wait.

Is it better for you too?

This appears to have been pulled - shame as it sounds like it fixed some of the major bugs - this is getting beyond ridiculous the time we've had to wait for working software.

Standard · Tue Jan 19, 2021 2:08 pm

Support response today with a new RC version of the firmware I passed :
Please upgrade CSS610 to SwOS Lite v2.13rc10 from the link and check if previously experienced problems remain.
https://box.mikrotik.com/f/9c2a7656ab554dd397e1/?dl=1

Hello, thanks a lot , but the link already seems to be dead.

Tue Jan 19, 2021 7:01 pm

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

gintarasp2 · Tue Jan 19, 2021 7:38 pm

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

What about dhcp clients in vlan access port?

Standard · Tue Jan 19, 2021 7:47 pm

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

Thanks

bikerrich · Tue Jan 19, 2021 9:03 pm

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

SFP management works! Thank you.

nannou9 · Tue Jan 19, 2021 9:29 pm

On 2.13rc12 all working for me even with rstp and add information option.
I am using multiple vlans, access ports, trunk ports etc. All good.

wsware · Tue Jan 19, 2021 9:50 pm

I just picked up the CSS610-8G-2S+ and could not get the SFP+ ports using DAC to connect at all with 2.12.
Installed the new 2.13rc12 and it is now working properly.

msimmons · Wed Jan 20, 2021 5:13 am

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

Thank you!

AvAxxCZ · Wed Jan 20, 2021 10:11 am

2.13rc12

access/managing through SFP+ ports >> looks OK
RSTP on SFP+ >> looks OK
VLAN and DHCP >> looks OK
LAG (LACP) shows MAC address again and seems more stable

Its looks promising

nannou9 · Wed Jan 20, 2021 2:58 pm

2.13rc12
I have new problem now.
When I change port name and save I am loosing connection on some ports. It happens every time for me.
I need to completely reboot the switch to recover operation. Switching information option off doesn’t change anything.
Tested like 5 times and happened each time.
Sfp seem to work however as I am able to reach switch from there but eth ports seems to be down.
Surely connection to router is down (eth1 with poe, trunk port) as I cannot reach the switch from there when it happens and my internet is completely down.

Can anybody test their switches to confirm if this is my case only?

ropeguru · Wed Jan 20, 2021 4:24 pm

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

The version when I was logged in show SwitchOS, not lite, on the top left and version 2.12, no RC...

mzaferyahsi · Wed Jan 20, 2021 6:42 pm

I seem to get the DHCP on VLANs working as well but it takes too much time (60s) and in some cases I am not getting IP at all.

AvAxxCZ · Wed Jan 20, 2021 8:56 pm

2.13rc12
As [nannou9] writes. I confirming described port rename problem. Reboot fix it.

JJT211 · Thu Jan 21, 2021 6:25 am

Thu Jan 21, 2021 9:28 am

Thanks nannou9 and AvAxxCZ, it will be fixed in the next versions. For now, avoid changing the "Name" setting on the Link page when running the 2.13rc12 version.

nannou9 · Fri Jan 22, 2021 12:49 am

2.13rc12
One more minor issue noticed:
MikroTik discovery doesn’t seem to work anymore.
Can’t discover devices behind the switch. I am pretty sure this was working previously. Switch itself is discoverable however. My other devices are on trunk port eth1 with poe.
Connections however still works if I put address manually, so as said: minor issue.

Thanks to MikroTik team for all improvements over last weeks.

nafeasonto · Fri Jan 22, 2021 3:43 am

I was going crazy, I was like what the heck is going on lol. Thanks for the hotfix. Any idea when they are going to release a stable firmware?

ChillFre4k · Fri Jan 22, 2021 9:44 am

Assign a new IP to the Swtich via DHCP wont work

Setting the Hostname/Identity wont work

Reset to factory settings should ask beforehand if you really want to do this

SNMP doesnt show LAG/Trunk Interfaces

I can't understand how a product can be released like this. At least the Rlease candidates bring improvement. Unfortunately they are not linked on the download page.

TheFF · Fri Jan 22, 2021 2:51 pm

Hey everyone,

I recently got my CSS610-8G-2S+ switch and its running great so far.

Yesterday I connected my servers via SFP+ RJ45 modules and removed their 1G links but after doing that, I could no longer the management website of the switch from the servers. If I move the cable to a normal RJ45 Port it works again. I also checked port isolation, nothing configured there and the "Allow from Ports" setting in the general tab, but all is default there - access to management from every port. A reset to default etc. didn't change the problem. My CSS610-8G-2S+ is running 2.12rc2.

Can anyone of you, also owning that switch, try if you have the same issue?

thanks
MiseryOne

I've got the switch yesterday and spent about 5 hours trying to access the management via SFP+.
Until now i haven't got it working and i was trying to find an update for SwOS that may fix this.

Also there seems to be a problem with the vlans.
I've connected two different devices to the switch and both of them are getting their ip address from the untagged vlan of the switch on the SFP+ uplink.
This happens although both ports of the devices are in different default vlans.
It seems the packets got no vlan tag assigned once they arrive at the switch.

I'm happy to find this thread, because i thought the problems are caused by my configuration, but i couldn't find an error.

nafeasonto · Sat Jan 23, 2021 12:57 am

Any news when a stabile patch will be released?

jookraw · Sat Jan 23, 2021 10:43 am

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1

I've tested this one for a few hours, but I was having a huge packet loss via one of the SPF+ ports using an S+RJ10 module to 2.5G NIC, reverted back to rc5, as rc6 was way worse.

nannou9 · Sat Jan 23, 2021 11:48 am

A new testing version 2.13rc12 is available - the VLAN and management connection through SFP+ ports are fixed. Please try upgrading your devices and share your feedback.

Below are versions
for CSS610-8G-2S+ https://box.mikrotik.com/f/0a98c88515a64596be3d/?dl=1
for CSS610-1Gi-7R-2S+ https://box.mikrotik.com/f/6321df1cdb1b42708c6a/?dl=1
I've tested this one for a few hours, but I was having a huge packet loss via one of the SPF+ ports using an S+RJ10 module to 2.5G NIC, reverted back to rc5, as rc6 was way worse.

I had temporarily more than 90% pocket loss too.
Not sure why tbh and what is worse not sure why it went away as I did many things at a time after which it suddenly went away and never happened again.
Try some silly things like resetting your switch to factory settings for example or power cycle it. I was power cycling even devices connected to it.
Anyway, never observed it again regardless of config change.
GL mate.

ChillFre4k · Sat Jan 23, 2021 12:13 pm

Plugging in a SFP+ needs a reboot of the switch

mirabelle · Sat Jan 23, 2021 11:15 pm

With rc12, my SFP module does not work anymore (it still appears but does not receive any packets from the other side). It works fine with rc5 (to which I reverted).

The module is a SFP-GE-BX from fs.com (https://www.fs.com/uk/products/75340.html). Autonegotiation is disabled and it is set to 1G.

koffeiniker · Mon Jan 25, 2021 12:34 pm

Guys, seriously? This is NEW product. Not really tested by earth and fire. If you're planning a commercial install based on an untested product - it's not MKT problem, it's your risk management. Go check Cisco forums for new products they release. Give folks some slack.

We have January 25th, 2021 ... I have 3 of these unholy electronic misfits. One would think that 2-3 month after reporting a showstopping bug, they would come up with a solution.

They are now at 2.13rc6 apparantly, but where is the 2.12 release for those who received and rc2 device?

Now of my 3 devices , one managed to run a trunk port and an access port to it. The other two just failed. I had them in the locker for almost three months due to work-load. Seeing the error-reports expecting a firmware update. I got nothing. Then I found the 2.13.rc6 and the description to it. Gave it a try .. failed. The issue with the WebGUI is bad, but my fail is even worse.

I am now busy writing a novel with an error description for sending them back for repair. Obvious reason: 3 devices configured alike, 1 works , 2 don't.

I am sorry but the 610 is a big fail. Probably not the device. But Mikrotik let us down on it, they created a mess and left us alone with it.

I will try to find another supplier for network equipment. I am ok if it costs more even 2-3 times as much, but it will work.

I mean it is not like we got a rebate for not getting what we paid for, right? I paid for a web-managed switch and I got a dumb switch.

I could not be more disappointed.

Paternot · Mon Jan 25, 2021 1:37 pm

Reading through this thread, I have a sugestion to Mikrotik, two in fact:

1) Get some form of automated basic testing. Something that would test "units of functionality", and do it one item after another. I'm not a developer, so I don't know the real name of this - but it is something wildly used, in order to get regressions and known bugs.

2) When some REALLY critical bug exists (no management from SFP+ on this product is beyond critical), release a new firmware, with JUST this correction. Something like 2.12 -> 2.12b. Change nothing else, leave the "only" serious bugs to the next version - but release a "critical fix" as soon as possible.

Really, I like Mikrotik - but sometimes the company need to step up.

JJT211 · Mon Jan 25, 2021 4:10 pm

Guys, seriously? This is NEW product. Not really tested by earth and fire. If you're planning a commercial install based on an untested product - it's not MKT problem, it's your risk management. Go check Cisco forums for new products they release. Give folks some slack.
We have January 25th, 2021 ... I have 3 of these unholy electronic misfits. One would think that 2-3 month after reporting a showstopping bug, they would come up with a solution.

They are now at 2.13rc6 apparantly, but where is the 2.12 release for those who received and rc2 device?

Now of my 3 devices , one managed to run a trunk port and an access port to it. The other two just failed. I had them in the locker for almost three months due to work-load. Seeing the error-reports expecting a firmware update. I got nothing. Then I found the 2.13.rc6 and the description to it. Gave it a try .. failed. The issue with the WebGUI is bad, but my fail is even worse.

I am now busy writing a novel with an error description for sending them back for repair. Obvious reason: 3 devices configured alike, 1 works , 2 don't.

I am sorry but the 610 is a big fail. Probably not the device. But Mikrotik let us down on it, they created a mess and left us alone with it.

I will try to find another supplier for network equipment. I am ok if it costs more even 2-3 times as much, but it will work.

I mean it is not like we got a rebate for not getting what we paid for, right? I paid for a web-managed switch and I got a dumb switch.

I could not be more disappointed.

Just FYI, there's an 2.13RC12 a few posts up

nafeasonto · Mon Jan 25, 2021 9:20 pm

Any news when a more stable patch will be released? This is a little ridiculous.

JJT211 · Tue Jan 26, 2021 4:44 am

Changing management IP requires reboot.

VAXman65 · Tue Jan 26, 2021 6:20 am

I have a CRS326-24G-2S+ running CAPsMAN connected to my CSS610-8G-2S+ with 10Gb copper SFP+. I have multiple CAP AC units, including one connected to the CSS610-8G-2S+. This generally works but I have had troubles when changing configuration. Specifically, if I am on WiFi against the CAP AC on the CSS610-8G-2S+, changing just the name of the ports on the Link page causes the connection to be lost and for the switch to become inaccessible. So far, the only way out is to physically power cycle the unit. Once the unit comes back, I do see that the change took effect. During the time the switch is not accessible for management, it also stops passing traffic of any kind in or out of the switch for WiFi or cable connections.

I tried this a few times before reporting it.

I am running with SWOS v2.13rc12

JJT211 · Tue Jan 26, 2021 6:47 am

^^^ This

I was just testing things out to see if I could deploy one but noticed the same thing, any change requires a reboot and I just cannot risk it.

AvAxxCZ · Tue Jan 26, 2021 12:17 pm

To: VAXman65
Problem was already reported and commented by EdPa from MikroTik Support

2.13rc12
I have new problem now.
When I change port name and save I am loosing connection on some ports. It happens every time for me.
I need to completely reboot the switch to recover operation. Switching information option off doesn’t change anything.
Tested like 5 times and happened each time.
Sfp seem to work however as I am able to reach switch from there but eth ports seems to be down.
Surely connection to router is down (eth1 with poe, trunk port) as I cannot reach the switch from there when it happens and my internet is completely down.

Can anybody test their switches to confirm if this is my case only?

Thanks nannou9 and AvAxxCZ, it will be fixed in the next versions. For now, avoid changing the "Name" setting on the Link page when running the 2.13rc12 version.

mbelanger · Tue Jan 26, 2021 1:12 pm

Woah. I was pretty intrigued with this switch for my company, especially with the features, size and price-point, but not after reading this thread.

Shipping a switch that lists VLANs as a feature, but that don't function es no bueno. And what's the point of having those powerful SFP+ ports if they're unstable?

I'm new to Mikrotik, are their new product releases typically this problematic?

mknyby · Tue Jan 26, 2021 4:36 pm

Also with 2.13rc12 it is not stable at all. Disconnect with no errors on interfaces, no traffic though the switch, interface get no link when disable/enable. A reboot works for max. 4-5 minuts.
Management though SFP+ are now working.

Paternot · Wed Jan 27, 2021 4:05 am

I'm new to Mikrotik, are their new product releases typically this problematic?

They usually have some teething problems. But this time they went the whole nine yards. I don't remember seeing one release as bad as 6.48 (nothing to do with this hardware), and the ney models are having their fair share of problems.

I don't know why. Maybe COVID compounding with RoS7, and getting the development team swamped.

wojrep · Wed Jan 27, 2021 6:37 am

As I remember it was always a problem with new devices. However, the problems with the CCR2004 / CSS610 can only be compared to those introduced by the first CCR models. But it was never the case that support was silent for such a long time.

I see the following possibilities:
1. They row forward to spend R7 as soon as possible
2. They have to wait for the fixes of the manufacturer of individual components, eg chip firmware.
3. The problem is unsolvable and requires hardware changes.

msimmons · Wed Jan 27, 2021 8:41 pm

Thanks nannou9 and AvAxxCZ, it will be fixed in the next versions. For now, avoid changing the "Name" setting on the Link page when running the 2.13rc12 version.

Any new release candidates or info on a stable release?

cwachs · Thu Jan 28, 2021 5:34 am

We are still running rc6 and had it stop responding to pings and SNMP today. At first I thought it was cold related (10 degrees F when the problem began) but it never cleared up once it warmed up. I have not rebooted the switch yet. It is still passing traffic but we can't get at it, it won't respond to ICMP ping and SNMP stopped. Well, ICMP ping drops 75% of the pings - some bounce back. It has had an uptime of about 3 weeks. This is very similar to the RB4011 (and 3011) issues that were traced to ARM software. I am expecting this switch to totally die and stop passing traffic in the next 24 hours.

JoSchaap · Fri Jan 29, 2021 11:55 am

Might it be an idea to create a sticky/pinned thread with SwOS Beta releases and their known fixes/faults?

I had to upgrade my CSS610-8G-2S+ to 2.13rc12 to resolve my SFP+ Management & DHCP passthrough issue and it took me a while to find out there is actually more then just the stable release out there.

Whilst it's a bit annoying to have to reboot the switch every time anything is changed on the interfaces page (not just names, even changing flow control/negotiation makes all ports except for SFP+ cease working); my use of the Tik devices is @home so i'm willing to shotgun any release you want us to try :)

I also wonder if anyone was able to setup 2 (or more) port LAG between the CSS610-8G-2S+ and a non-MikroTik/RB device such as a managed 3com/netgear switch or LAG supported ISP router?

JJT211 · Sat Jan 30, 2021 8:15 pm

We are still running rc6 and had it stop responding to pings and SNMP today. At first I thought it was cold related (10 degrees F when the problem began) but it never cleared up once it warmed up. I have not rebooted the switch yet. It is still passing traffic but we can't get at it, it won't respond to ICMP ping and SNMP stopped. Well, ICMP ping drops 75% of the pings - some bounce back. It has had an uptime of about 3 weeks. This is very similar to the RB4011 (and 3011) issues that were traced to ARM software. I am expecting this switch to totally die and stop passing traffic in the next 24 hours.

Have you tried RC12 yet?

cwachs · Sat Jan 30, 2021 9:44 pm

Just installed rc12 after we power cycled the router to regain access to it.

mbelanger · Mon Feb 01, 2021 11:42 pm

Can someone update me on the current status of the CSS610 firmware?

Can one access the management site over the SFP+ ports?

Do VLANs properly work now?

Any other pressing issues remaining?

How far away is this software from deploying in a small production environment?

Thanks,
MB

JJT211 · Tue Feb 02, 2021 7:44 am

Just installed rc12 after we power cycled the router to regain access to it.

Cool, keep us posted

JJT211 · Tue Feb 02, 2021 7:46 am

Can someone update me on the current status of the CSS610 firmware?

Can one access the management site over the SFP+ ports?

Do VLANs properly work now?

Any other pressing issues remaining?

How far away is this software from deploying in a small production environment?

Thanks,
MB

Scroll up the page and you'll see the latest 2.13RC12

VLANS and SFP management works. I have yet to deploy it yet as some have mention there's still a few bugs

alexk1 · Tue Feb 02, 2021 1:08 pm

I have now successfully got this switch running with all the features I need; VLANs, Trunking, 2x10Gb MMF, SNMP, RSTP.

Haven't tried LAG yet as I don't need it, but other than that it has been up and stable for 3 days of heavy usage.

Using RC12.

Alex

mbelanger · Tue Feb 02, 2021 8:22 pm

I have now successfully got this switch running with all the features I need; VLANs, Trunking, 2x10Gb MMF, SNMP, RSTP.

Haven't tried LAG yet as I don't need it, but other than that it has been up and stable for 3 days of heavy usage.

Using RC12.

So happy to hear!

Is anyone using this with the S+RJ10 connecting at 10G over cat6a?

Thanks,
MB

bikerrich · Wed Feb 03, 2021 11:02 am

I have now successfully got this switch running with all the features I need; VLANs, Trunking, 2x10Gb MMF, SNMP, RSTP.

Haven't tried LAG yet as I don't need it, but other than that it has been up and stable for 3 days of heavy usage.

Using RC12.
So happy to hear!

Is anyone using this with the S+RJ10 connecting at 10G over cat6a?

Thanks,
MB

I tried but was using at 30M cable lengths and the transceivers weren't stable, I ended up switching to 80M transceivers and they're solid as a rock - just ticked over 2 weeks up time with no issues. It would just be nice if we could get some proper release firmware now.

jookraw · Wed Feb 03, 2021 1:51 pm

Using RC6 and RC12 the SFP+ with an S+RJ10 module I get a huge packet loss to the rest of the network.
I have a server connected via an SFP+ DAC cable at 10g without issues, so, for me, it seems to affect any speed with the 10GBase-T SFP+, did not test 10G or 5G, because of the lack of 10G NIC's for BaseT.

ectoplasmosis · Thu Feb 04, 2021 5:31 pm

I'm running 2.13rc12 on a CSS610, trunked via SFP+1 to a CRS317 at 10GbE via a DAC.

VLANs are configured and working on the 1Gb copper ports; I get correct DHCP addresses when plugging a client in.

But when I plug a client into SFP+2, regardless of how I have VLANs set up, the CSS610 will not pass traffic to SFP+2, and the copper ports also stop working properly until I re-plug SFP+1 trunk.

What is happening here? It would be great to be able to use the second SFP+ port for a 10Gb-capable client.

JoSchaap · Fri Feb 05, 2021 6:04 pm

I have now successfully got this switch running with all the features I need; VLANs, Trunking, 2x10Gb MMF, SNMP, RSTP.

Haven't tried LAG yet as I don't need it, but other than that it has been up and stable for 3 days of heavy usage.

Using RC12.
So happy to hear!

Is anyone using this with the S+RJ10 connecting at 10G over cat6a?

Thanks,
MB

I am, but only over 7 MTR length to my server; so I cant vouch for range :)

switch.jpg

ropeguru · Fri Feb 05, 2021 8:09 pm

Can someone from Mikrotik support please explain why we have to dig through months long threads just to see if there is a new version available? Why are you avoiding putting up a pinned item for easier tracking like someone trying to avoid COVID?

This whole new set of switches and SwOS Lite seem to be the bastard children which will never get the support they deserve. Put a huge black eye on Mikrotik for me and wanting to avoid the products in the future.

bikerrich · Fri Feb 05, 2021 9:03 pm

Can someone from Mikrotik support please explain why we have to dig through months long threads just to see if there is a new version available? Why are you avoiding putting up a pinned item for easier tracking like someone trying to avoid COVID?

This whole new set of switches and SwOS Lite seem to be the bastard children which will never get the support they deserve. Put a huge black eye on Mikrotik for me and wanting to avoid the products in the future.

Bit harsh but I get where you're coming from - even with Covid etc etc..., not having a release software version for hardware that shipped months ago is pretty shoddy. I think MikroTik are expecting quite a lot from their customers - hardware many be cheap but if the software doesn't work then that cheap hardware looks like an expensive paperweight.

ropeguru · Fri Feb 05, 2021 10:06 pm

Can someone from Mikrotik support please explain why we have to dig through months long threads just to see if there is a new version available? Why are you avoiding putting up a pinned item for easier tracking like someone trying to avoid COVID?

This whole new set of switches and SwOS Lite seem to be the bastard children which will never get the support they deserve. Put a huge black eye on Mikrotik for me and wanting to avoid the products in the future.
Bit harsh but I get where you're coming from - even with Covid etc etc..., not having a release software version for hardware that shipped months ago is pretty shoddy. I think MikroTik are expecting quite a lot from their customers - hardware many be cheap but if the software doesn't work then that cheap hardware looks like an expensive paperweight.

It is more about transparency. When I first received the CCS610-8G-2S+ and powered it up, it show something like "SwitchOS 2.12" in the web UI so I went to the site, like I do for every new piece of hardware that I get, to see if there was any newer version of the code. I was really baffled as on the download page there was version 2.13 available but none of the versions included the switch I. had just purchased. I had to come to the forums and search and dig only to find out that the firmware was still in RC status and was a "Lite" version at that. I then had to search through this long a$$ post and found RC5 which I downloaded, only to find out later, in this same thread, that RC12 was available which fixed some of my issues.

It is just frustrating to get a new device in only to find out it is still in Beta, although not advertised that way, and has so many issues with very little response from the manufacturer.

cwachs · Sat Feb 06, 2021 11:23 pm

I have upgraded our switch to RC12. I have two customers attached to it via ether1 and ether2 - both have GPEN powered devices on their end. The uplink to the switch is into SFP+1 using a 1G SFP module.

What we notice is on RC12, every hour at exactly :13 past the hour, the switch (and all customers behind it) loose exactly 15 pings (1 second apart) - or 15 seconds on connectivity. On RC6, we would loose access to the switch over SFP+ port so it was too unstable to use.

I have swapped out the GPEN power supplies and the SFP module. The switch at the other end of the fiber never looses a ping so the problem is in the CSS610 and seems to be in the SFP+ port. We've tried turning off flow control with no effect.

cwachs · Sun Feb 07, 2021 9:42 pm

Looks like Watchdog is broken in RC12. This seems to be what was causing our router to reboot every 3600 seconds. I've turned Watchdog off and we have gone 2 hours now without a reboot.

AvAxxCZ · Mon Feb 08, 2021 8:40 pm

viewtopic.php?f=17&t=172032#p842824

I currently have 4 trunk ports on 7,8,SFP1,SFP2 and ports 1-6 I assign as needed. I did previously have a client(access port) on SFP2 working fine(same as what you are trying to achieve) and i had just removed the extra VLANs on SFP2 and assigned a native VLAN ID on the VLAN tab.
Thanks for the tips; I'll try this.

Mikrotik Support also replied with a new firmware version, 2.13rc25: https://box.mikrotik.com/f/a4b001debcee4a05aec2/?dl=1

alexk1 · Mon Feb 08, 2021 9:30 pm

Appearently this is RC25 haven't checked link yet https://box.mikrotik.com/f/a4b001debcee4a05aec2/?dl=1

Edit: Yep it is

cwachs · Mon Feb 08, 2021 11:01 pm

That firmware is not for the netPower 7R.

alexk1 · Mon Feb 08, 2021 11:24 pm

Working fine so far for me on the CSS610-8G-2S+

cwachs · Tue Feb 09, 2021 12:16 am

We need a version for the CSS610-1Gi-7R-2S+ switch.

alexk1 · Tue Feb 09, 2021 2:19 pm

I take back what I said about RC25 being fine, I am getting hourly reboots of the switch on the hour with full outage.

Switch Uptime.PNG

Switch Uptime2.PNG

Started a transfer just before reboot for testing, you can see where the switch cuts out

Switch reboot.PNG

Disappointing :(

elevendroids · Tue Feb 09, 2021 2:33 pm

Interesting - mine works without issues - simple setup with ports 1-7 serving as untagged ports bound to a VLAN, 8 and both SFPs as trunk ports:

Screenshot from 2021-02-09 12-27-33.png

I have yet to test another issue that was present in rc12 - hotplugging (or unplugging) a SFP module from SFP2 would sometimes cause the traffic to be no longer forwarded via SFP1 (which is set as trunk port), need to re-check that though.
So far this firmware seems to be stable...

nannou9 · Tue Feb 09, 2021 2:54 pm

Rc25 fixes all my remaining problems

ectoplasmosis · Tue Feb 09, 2021 3:08 pm

2.13rc25 breaks IGMP Snooping for me...

When IGMP Snooping is enabled in System and web interface is on the IGMP tab, multicast members are shown for a few seconds before the page is replaced with an error message in red text:

gintarasp2 · Tue Feb 09, 2021 4:53 pm

I take back what I said about RC25 being fine, I am getting hourly reboots of the switch on the hour with full outage.

Switch Uptime.PNG

Switch Uptime2.PNG

Started a transfer just before reboot for testing, you can see where the switch cuts out

Switch reboot.PNG

Disappointing :(

Have your device actually rebooted? Because it might be that Uptime is only bugged.
I noticed it back in RC2 with Zabbix SNMP scan. Yet I did not recall losing connection at all, i had my always plugged via the switch.
I used switched as it is in current situation usable - as dumb switch.

cwachs · Tue Feb 09, 2021 4:56 pm

See my comments a little higher up. I think watchdog is broken. Our was rebooting exactly every hour as well. It was a true reboot with 15 seconds of packet loss through the switch each time it rebooted.

gintarasp2 · Tue Feb 09, 2021 6:48 pm

See my comments a little higher up. I think watchdog is broken. Our was rebooting exactly every hour as well. It was a true reboot with 15 seconds of packet loss through the switch each time it rebooted.

I just powered on the PC after I got home.
6 hours earlier I have upgraded to RC25 leaviang default config with Watchdog enabled.
Switch shows uptime with no reboots 06:16:04

mbelanger · Tue Feb 09, 2021 11:12 pm

The UI keeps timing out, but uptime shows 23:33:37 since I last rebooted after installing rc25. Granted I'm still testing this switch, so it hasn't had a lot of traffic running over it, but it is connected to my network.

-MB

alexk1 · Wed Feb 10, 2021 9:38 am

It is strange that we have different problems with the same hardware.

I have tried a factory reset and rebuild but i still get the same problem with hourly reboots. If I disable the watchdog function(as mentioned by Cwachs - Thank you!) i do not get the reboots.

Edit: I am also getting a similar issue to ectoplasmosis where igmp tab keeps clearing itself but i don't get the error message they do.

sterling · Wed Feb 10, 2021 6:58 pm

I assume you guys are reporting all problems in RC to support as they are getting closer to release?

I submitted a ticket to get the latest 7R RC update package so I can test it along with the 610 8 port 2 SFP+ port switches we have and want to use.

gintarasp2 · Thu Feb 11, 2021 2:21 pm

Hello everyone, yesterday I have compiled a list of issues with CSS610-8G-2S+ that I have found in this forum.

I have upgraded two units of CSS610 to RC25 and run two instances of testing:
1. With default configuration.
2. With VLAN configuration.

P.S. Due to not having SFP cable of any kind, SFP issues could not be tested by me, feel free to post below your results.

Here are my tests and results:
1. With default configuration after RC25 upgrade:
1.1. Management Access Via SFP+ - NOT TESTED - do not have available cable.
1.2. Default access ports - TESTED - dumb switch forward everything works.
1.3. DHCP client SWITCH - TESTED -works with no VLANS.
1.4. DHCP client SWITCH-Connected-Device - TESTED - works for all devices.
1.5. ICMP drops - TESTED - none observed.
1.6. Less than 10G speed negotiation on SFP fails the port - NOT TESTED - do not have available cable.
1.7. Port rename causes port to fail - TESTED - no issues observed.
1.8. Discovery behind the Switch - TESTED - no issues with discovery.
1.9. Random packets get lost between/to switch. - TESTED - did not observer any lost packets.
1.10. Plugging in SFP requires device to be rebooted. - NOT TESTED - do not have available cable.
1.11. Changing IP for management requires reboot the device. - TESTED - it requires reboot yes, is it intended? I do not know.
1.12. Changing flow control causes to fail ports. - TESTED - one PING got dropped.
1.13. Switch reboots every hour. - TESTED - 6 hours later, no reboots.
1.14. IGMP snooping is broken. - NOT TESTED? - Empty window, no idea is it broken or not.
1.15. Changing negotiations causes port failures. - TESTED - No failures, need to be set on both sides, no reboot required.

2. With VLAN configuration after RC25 upgrade:
2.1. Management Access Via SFP+ - NOT TESTED - do not have available cable.
2.2. VLAN access ports - TESTED - works with Optional + Untagged + ID + Port membership configuration
2.3. DHCP client TRUNK port SWITCH - TESTED - does not work.
2.4. DHCP client SWITCH-Connected-Device in VLAN - TESTED - works fine. All separate VLANs gave their own DHCP leases.
2.5. ICMP drops - TESTED - none observed.
2.6. Less than 10G speed negotiation on SFP fails the port - NOT TESTED - do not have available cable.
2.7. Port rename causes port to fail - TESTED - no issues observed.
2.8. Discovery behind the Switch - TESTED - no issues with discovery. Device has to be in the same VLAN as managed device (router, switch, etc.)
2.9. Random packets get lost between/to switch. - TESTED - no issues observed.
2.10. Plugging in SFP requires device to be rebooted. - NOT TESTED - do not have available cable.
2.11. Changing IP for management requires reboot the device. - TESTED - it requires reboot yes, is it intended? I do not know.
2.12. Changing flow control causes to fail ports. - TESTED - one PING got dropped.
2.13. Switch reboots every hour. - TESTED - no reboots after one hour of testing today.
2.14. IGMP snooping is broken. - NOT TESTED? - Empty window, no idea is it broken or not.
2.15. Changing negotiations causes port failures. - TESTED - No failures, need to be set on both sides, no reboot required.
2.16. Management access via TRUNK port - TESTED - works fine from trunk port / no issues observed.
2.17. Mikrotik DHCP client on access port - TESTED - gets IP address.

Topology:
HAP AC3 router -> Atheros 8327 SW chip for trunk port -> CSS610(SW1) -> CSS610(SW2)
Point to point connections are trunks. Access ports are VLAN 10, 20, 30, and default 1.
Access ports : Mode=Optional + Receive=Untagged + ID=1/10/20/30 (depends)
Trunk ports : Mode=Strict + Receive=Tagged + ID=-
After configuration configure VLAN and port memberships.

Hope this post saves you some time of scrolling thru this page.
Leave a like, comment, subscribe.

Best regards,

ectoplasmosis · Thu Feb 11, 2021 5:32 pm

Update:

Using the second SFP+ port as an access port for a client is broken again. Using 2.13rc25, was working fine until I changed the native VLAN on the SFP+ access port.
Even with everything set as per the copper access ports, the client connected to SFP+ will not get DHCP or pass traffic.

The strange thing is that in the 'Stats' tab, Rx Rate always shows zero when a client is connected to the secondary SFP+ port, whereas Tx Rate and Tx Bytes count up.

sterling · Fri Feb 12, 2021 2:26 am

Mikrotik support punted and gave me the "default" useless answer:

"Hello,
Thank you for contacting MikroTik Support.
You can download the latest releases from our download page, www.mikrotik.com/download, or wait till the next version is releases with fixes.
Best regards,
Oskars K."

Of course the answer is invalid since they currently have NO firmware available on the download page for 610 series anything.

Can someone post the latest 7R version firmware download link please?

I mean, it's not like I've been purchasing Mikrotik since they first started selling junky wireless PCBs a couple decades ago.......

msimmons · Fri Feb 12, 2021 5:00 am

Mikrotik support punted and gave me the "default" useless answer:

"Hello,
Thank you for contacting MikroTik Support.
You can download the latest releases from our download page, www.mikrotik.com/download, or wait till the next version is releases with fixes.
Best regards,
Oskars K."

Of course the answer is invalid since they currently have NO firmware available on the download page for 610 series anything.

Can someone post the latest 7R version firmware download link please?

I mean, it's not like I've been purchasing Mikrotik since they first started selling junky wireless PCBs a couple decades ago.......

Let me know when you get that, Sterling.

marekm · Sun Feb 14, 2021 12:35 am

Is there still (as of current RC) any situation where the reverse-PoE switches might need a reboot by power-cycle (remote reboot either not possible, or possible but not sufficient)?
Asking because power-cycle is difficult to do in many reverse-PoE installations (redundant power from several different customers who may not even be around all at the same time).

sterling · Sun Feb 14, 2021 12:51 am

Is there still (as of current RC) any situation where the reverse-PoE switches might need a reboot by power-cycle (remote reboot either not possible, or possible but not sufficient)?
Asking because power-cycle is difficult to do in many reverse-PoE installations (redundant power from several different customers who may not even be around all at the same time).

I sure hope it doesn't have issues.

But to be sure, we've implemented watchdog based on a ping to the upstream switch to make sure it power cycles itself.
That works in most cases so far with older CRS switches, so I'm hoping it's solid in the 2.13 release...

JJT211 · Sun Feb 14, 2021 1:04 am

Mikrotik support punted and gave me the "default" useless answer:

"Hello,
Thank you for contacting MikroTik Support.
You can download the latest releases from our download page, www.mikrotik.com/download, or wait till the next version is releases with fixes.
Best regards,
Oskars K."

Of course the answer is invalid since they currently have NO firmware available on the download page for 610 series anything.

Can someone post the latest 7R version firmware download link please?

I mean, it's not like I've been purchasing Mikrotik since they first started selling junky wireless PCBs a couple decades ago.......

Yea, I got same answer as well

sterling · Tue Feb 16, 2021 11:53 pm

I emailed suppport back and asked them to give me access again to the RC candidates.

I did some testing on the 610-8G-2S+IN today in preparation to start testing them out in the field.
Doing some rate limiting on the Ingress/Egress with management/feed on SFP1.
Egress/Download to client on any of the Ethernet GigE ports seems to work ok when I put in something like 250M in the field.
It gives me around 255Mbps on speedtest.net client. So download/Egress works.
Ingress on any of the GigE ports seems broken though.
If I put a similar value of 250M on Ingress it limits my upload to around 5Mbps.
If I put it to some max value around 900M it lets it go to about 20Mbps.
So that doesn't work correctly.

If I do set the Egress on the uplink SFP1 at 250M then it does successfully limit the client to 250Mbps both ways.
But that limit ALL upload in total to 250Mbps across the switch outgoing SFP1 uplink.
So it's a temp solution for us until they fix it.

Also, the download never seems to get above 900Mbps Egress on any of the GigE ports without throttle, so there might be some 50Mbps of optimization to do there as well.
Our uplink is 10Gbps to a Force10 switch with 40Gbps to the speedtest server, so there is plenty of bandwidth there for testing.

That's all I've tested so far.

I will also be testing Option 82 DHCP Snooping and port isolation as well.

pwnet · Wed Feb 17, 2021 7:04 am

Well, I have to say, reading this thread (and others) has been really disappointing. Thankfully, I wasn't too invested in Mikrotik; I purchased one CSS610-8g for lab testing before deployment, and I've decided not to move forward with Mikrotik at all.

You guys realize you are beta testers, right? What is this RC25 nonsense? If you are on version 25 of a release candidate, and your forum users are having to issue their own test findings on long-list point form, just call it what it is: a beta. They are selling a product that they have known for months isn't functional as documented or advertised, with crippling bugs, and providing extremely little feedback as to when these issues will be resolved.

Where are the recalls? Where are the end user bulletins? Why have the vendors not been instructed to pull these off the shelves? Why is Mikrotik continuing to authorize the sale of a product that they know will be deployed in a enterprise setting, when they are well aware that the product doesn't even work properly? Aren't there some sort of consumer protection laws against this sort of thing?

We aren't talking about some small obscure bugs here. These are major issues. If they released a product with these glaring deficiencies, how can we trust they have implemented the more discrete security measures properly? Perhaps they haven't?

I am very glad I did my due diligence and tested a unit before full deployment. I feel sorry for people who have been sitting on a full inventory of these bricks for months now with no word on when they will even be usable.

gintarasp2 · Wed Feb 17, 2021 11:59 am

Well, I have to say, reading this thread (and others) has been really disappointing. Thankfully, I wasn't too invested in Mikrotik; I purchased one CSS610-8g for lab testing before deployment, and I've decided not to move forward with Mikrotik at all.

You guys realize you are beta testers, right? What is this RC25 nonsense? If you are on version 25 of a release candidate, and your forum users are having to issue their own test findings on long-list point form, just call it what it is: a beta. They are selling a product that they have known for months isn't functional as documented or advertised, with crippling bugs, and providing extremely little feedback as to when these issues will be resolved.

Where are the recalls? Where are the end user bulletins? Why have the vendors not been instructed to pull these off the shelves? Why is Mikrotik continuing to authorize the sale of a product that they know will be deployed in a enterprise setting, when they are well aware that the product doesn't even work properly? Aren't there some sort of consumer protection laws against this sort of thing?

We aren't talking about some small obscure bugs here. These are major issues. If they released a product with these glaring deficiencies, how can we trust they have implemented the more discrete security measures properly? Perhaps they haven't?

I am very glad I did my due diligence and tested a unit before full deployment. I feel sorry for people who have been sitting on a full inventory of these bricks for months now with no word on when they will even be usable.

Until the legal expenses are not greater than recal expenses, there wount be any recal, that is how corporate and reality works. If you want some kind of recal, go to court.

Sucks, Mikrotik seemed to be something else for business and for home, even considered to get certified, but it seems their name means less than money.
How many months device is for sale?
How long not even a warning on device tab in official site or eshop?

nafeasonto · Wed Feb 17, 2021 5:01 pm

Well, I have to say, reading this thread (and others) has been really disappointing. Thankfully, I wasn't too invested in Mikrotik; I purchased one CSS610-8g for lab testing before deployment, and I've decided not to move forward with Mikrotik at all.

You guys realize you are beta testers, right? What is this RC25 nonsense? If you are on version 25 of a release candidate, and your forum users are having to issue their own test findings on long-list point form, just call it what it is: a beta. They are selling a product that they have known for months isn't functional as documented or advertised, with crippling bugs, and providing extremely little feedback as to when these issues will be resolved.

Where are the recalls? Where are the end user bulletins? Why have the vendors not been instructed to pull these off the shelves? Why is Mikrotik continuing to authorize the sale of a product that they know will be deployed in a enterprise setting, when they are well aware that the product doesn't even work properly? Aren't there some sort of consumer protection laws against this sort of thing?

We aren't talking about some small obscure bugs here. These are major issues. If they released a product with these glaring deficiencies, how can we trust they have implemented the more discrete security measures properly? Perhaps they haven't?

I am very glad I did my due diligence and tested a unit before full deployment. I feel sorry for people who have been sitting on a full inventory of these bricks for months now with no word on when they will even be usable.

I hate to be a dick, but you do realize these aren't business switches/routers/L3 right? I mean at MOST you should only be using Mikrotik in very small business environment, or home lab. I would never use these things at a big business. There are way too many bugs in these things. I.E. this model. There have also been many many bugs in their previous.

But honestly, for as cheap as these are, they work decently well, and Mikrotik doesn't abandon them, and the firmware upgrades are free.

mikronerd · Thu Feb 18, 2021 8:24 am

I hate to be a dick, but you do realize these aren't business switches/routers/L3 right? I mean at MOST you should only be using Mikrotik in very small business environment, or home lab. I would never use these things at a big business. There are way too many bugs in these things. I.E. this model. There have also been many many bugs in their previous.

But honestly, for as cheap as these are, they work decently well, and Mikrotik doesn't abandon them, and the firmware upgrades are free.

This is like saying you should be happy with a brand-new but cheap Toyota that can't go as fast as it claims because tires are not inflated, there is no windshield and clutch doesn't work half the time. You can be upfront about software beta status during purchase so people know what to expect.

marekm · Thu Feb 18, 2021 1:32 pm

Is there still (as of current RC) any situation where the reverse-PoE switches might need a reboot by power-cycle (remote reboot either not possible, or possible but not sufficient)?
Asking because power-cycle is difficult to do in many reverse-PoE installations (redundant power from several different customers who may not even be around all at the same time).
I sure hope it doesn't have issues.

But to be sure, we've implemented watchdog based on a ping to the upstream switch to make sure it power cycles itself.
That works in most cases so far with older CRS switches, so I'm hoping it's solid in the 2.13 release...

CRS running RouterOS have the ping watchdog feature, but it has been fixed to work properly with VLANs only recently (previously it never got any response and rebooted periodically).
But this device only supports SwOS, probably on some small microcontroller - not sure if it can support the ping watchdog, if it does TCP/IP with simple algorithm (replying to the same IP/MAC it got the request from) this means it can't initiate any communication on its own. I don't understand the reasons for SwOS today, some CPU capable of running full RouterOS should be cheap enough (see the RB931-2nD - slow CPU is OK here, as it only manages the switch and doesn't handle all the traffic).

Just an idea how remote reboot could be added in a reverse-PoE setup - add a simple hardware circuit to monitor the supply voltage (after the logical OR with diodes from PoE-in ports, but before powering the device itself and its PoE-out) and disconnect it with some series P-channel mosfet if detected too high. So if you usually run the setup with 24V PoE from customers, connect a 48V power supply at one customer to reboot without need to visit all other customers at the same time. As an added bonus, you get some overvoltage protection (reboot instead of damage). But of course, before connecting a higher voltage power supply you need to be sure such protection exists in the device where you connect it, so it's still not fool-proof (some other devices might be damaged). But then, any passive PoE is not fool-proof anyway.

nafeasonto · Sun Feb 21, 2021 5:27 pm

I hate to be a dick, but you do realize these aren't business switches/routers/L3 right? I mean at MOST you should only be using Mikrotik in very small business environment, or home lab. I would never use these things at a big business. There are way too many bugs in these things. I.E. this model. There have also been many many bugs in their previous.

But honestly, for as cheap as these are, they work decently well, and Mikrotik doesn't abandon them, and the firmware upgrades are free.

This is like saying you should be happy with a brand-new but cheap Toyota that can't go as fast as it claims because tires are not inflated, there is no windshield and clutch doesn't work half the time. You can be upfront about software beta status during purchase so people know what to expect. I'm so glad I stumbled upon this forum by mistake before purchasing.

Yeah that is exactly what I am saying. So what?

ectoplasmosis · Wed Feb 24, 2021 7:15 pm

IGMP Snooping still broken for me on RC25...

Anyone using IGMP Snooping?

ropeguru · Thu Feb 25, 2021 12:06 am

IGMP Snooping still broken for me on RC25...

Anyone using IGMP Snooping?

I have it enabled on a single vlan and do see entries under the igmp tab, but have not tested any further than that.

msimmons · Thu Feb 25, 2021 12:28 am

Can someone post the latest rc?

gintarasp2 · Thu Feb 25, 2021 8:04 am

Can someone post the latest rc?

If you look up there is a link.

msimmons · Thu Feb 25, 2021 8:26 am

Can someone post the latest rc for the netpower 7r?

maigonis · Fri Feb 26, 2021 2:05 pm

IGMP Snooping still broken for me on RC25...

Anyone using IGMP Snooping?
I have it enabled on a single vlan and do see entries under the igmp tab, but have not tested any further than that.

I use IGMP snooping on my network and I see entries on tab. I use it as simple switch, no vlans or other complex config. SwOS 2.13rc25.

ectoplasmosis · Mon Mar 01, 2021 3:08 pm

IGMP Snooping still broken for me on RC25...

Anyone using IGMP Snooping?
I have it enabled on a single vlan and do see entries under the igmp tab, but have not tested any further than that.
I use IGMP snooping on my network and I see entries on tab. I use it as simple switch, no vlans or other complex config. SwOS 2.13rc25.

.

On my device with 9 VLANs, IGMP tab shows entries for a minute or so, then a red 'Unexpected Token' error. Some clients end up being falsely unsubscribed to random multicast addresses. IGMP Snooping therefore appears functionally broken.

.

Benqer · Mon Mar 01, 2021 11:03 pm

Is there already a new status?

bikerrich · Tue Mar 02, 2021 3:10 pm

Is there already a new status?

Don't think so, it must be almost 6 months since many of us purchased these - for me R25 stopped them being only good as a paperweight. Regardless, it's really poor that we still don't have release firmware.

pwnet · Tue Mar 02, 2021 5:26 pm

Is there already a new status?
Don't think so, it must be almost 6 months since many of us purchased these - for me R25 stopped them being only good as a paperweight. Regardless, it's really poor that we still don't have release firmware.

I suspect these problems may be hardware related. If the problems could be fixed by software, I would think that they would have resolved them already.

Not being able to access management on SFP+. How hard could that possibly be to fix?

fryfrog · Tue Mar 02, 2021 5:50 pm

I suspect these problems may be hardware related. If the problems could be fixed by software, I would think that they would have resolved them already.

Not being able to access management on SFP+. How hard could that possibly be to fix?

Have you tried any of the RC firmware? They've already fixed the management over SFP+, I have it open right now on RC12 and it worked on RC25 too. Others above have tested older RC versions and it works too. Right now, my "only" issue is that it *doesn't* link w/ an X520 nic. :|

bikerrich · Tue Mar 02, 2021 5:59 pm

Is there already a new status?
Don't think so, it must be almost 6 months since many of us purchased these - for me R25 stopped them being only good as a paperweight. Regardless, it's really poor that we still don't have release firmware.
I suspect these problems may be hardware related. If the problems could be fixed by software, I would think that they would have resolved them already.

Not being able to access management on SFP+. How hard could that possibly be to fix?

R13 & R25 fixed SFP+ access for me but I think the current bug lists are issues associated with config changes that require reboots etc. The frustrating issues is the lack of engagement from Mikrotik telling their customers (beta testers) what's been fixed and what's not and what bugs have been fixed.

pwnet · Tue Mar 02, 2021 6:43 pm

R13 & R25 fixed SFP+ access for me but I think the current bug lists are issues associated with config changes that require reboots etc. The frustrating issues is the lack of engagement from Mikrotik telling their customers (beta testers) what's been fixed and what's not and what bugs have been fixed.

I agree. In my opinion, this is what will keep Mikrotik from ever becoming a contender in the enterprise league. If you look at the big boys (Cisco, Fortinet, Juniper, etc), the support product they offer is almost as important as the hardware product. They justify their high price tag with top tier support. The lack of support also is what will keep Mikrotik out of most of the home market. Home users need support to (arguably more so), especially with how complex Mikrotik can be to configure.

Ruling out most of the enterprise market and most of the home market, Mikrotik is left with a very niche market in the middle of hobbyists and small business IT providers.

Obviously, the lack of support infrastructure is what allows Mikrotik to justify the low price tag. Cisco might be expensive, but at least you can get someone on the phone 24/7 to walk you through problems. Mikrotik doesn't offer that.

But then again, we aren't asking for top tier support. We are just asking for development updates, and we aren't even getting those. That is going to turn off a chunk of the hobbyist market as well. I'm not really sure who is left. Masochists?

nannou9 · Tue Mar 02, 2021 9:26 pm

R13 & R25 fixed SFP+ access for me but I think the current bug lists are issues associated with config changes that require reboots etc. The frustrating issues is the lack of engagement from Mikrotik telling their customers (beta testers) what's been fixed and what's not and what bugs have been fixed.
I agree. In my opinion, this is what will keep Mikrotik from ever becoming a contender in the enterprise league. If you look at the big boys (Cisco, Fortinet, Juniper, etc), the support product they offer is almost as important as the hardware product. They justify their high price tag with top tier support. The lack of support also is what will keep Mikrotik out of most of the home market. Home users need support to (arguably more so), especially with how complex Mikrotik can be to configure.

Ruling out most of the enterprise market and most of the home market, Mikrotik is left with a very niche market in the middle of hobbyists and small business IT providers.

Obviously, the lack of support infrastructure is what allows Mikrotik to justify the low price tag. Cisco might be expensive, but at least you can get someone on the phone 24/7 to walk you through problems. Mikrotik doesn't offer that.

But then again, we aren't asking for top tier support. We are just asking for development updates, and we aren't even getting those. That is going to turn off a chunk of the hobbyist market as well. I'm not really sure who is left. Masochists?

I think MikroTik is well aware how disastrous CSS610 launch turned to be.
Few people lost bonuses if not jobs I assume: QA manager, technical lead on project, CTO, product manager etc.
It is now taking 5 months to fix the issues. I am scratching my head every day why it is taking so long. Either it is so badly written that they cannot get it fixed as one fix breaks other things (as we can see happening in fact), or it is such a low priority to them. But having all their expertise and existing IP, I would have thought ~4-6 months is the time you need to implement new chip from scratch for swos, which is very limited in features really.

They are however undoubtedly cheapest when compared power to cost.
I don’t think there are any other 10gb switches on the market for similar price?

JJT211 · Tue Mar 02, 2021 9:44 pm

So how is RC12 doing? Anyone using it in production?

I have a few of the Netpower 7R's and all I really need is basic VLAN functionality with reverse POE at gigabit speeds. I have no use atm for the SFP.

pwnet · Tue Mar 02, 2021 10:50 pm

So how is RC12 doing? Anyone using it in production?

I have a few of the Netpower 7R's and all I really need is basic VLAN functionality with reverse POE at gigabit speeds. I have no use atm for the SFP.

They are up to RC25 now. Check the other thread on this section. Some things are still borked, but VLANS seem to work now.

I'm not using it in production.

pwnet · Tue Mar 02, 2021 10:56 pm

I don’t think there are any other 10gb switches on the market for similar price?

Lower dollar value maybe, but not necessarily lower price. Time is money. There are a number of people who lost a lot of diagnostic hours trying to figure out why VLAN wasn't working (thinking they were doing something wrong). I was one of them. Not to mention the folks that purchased these in quantity and have to sit on them because they don't work. That kind of thing can really hurt a small business.

When you take into consideration diagnostic time, potential lost clients, scheduling delays, reputational damage, etc; is it really less expensive overall?

I guess it depends on what you are using them for.

mbelanger · Tue Mar 02, 2021 11:18 pm

I think MikroTik is well aware how disastrous CSS610 launch turned to be.
Few people lost bonuses if not jobs I assume: QA manager, technical lead on project, CTO, product manager etc.
It is now taking 5 months to fix the issues. I am scratching my head every day why it is taking so long. Either it is so badly written that they cannot get it fixed as one fix breaks other things (as we can see happening in fact), or it is such a low priority to them. But having all their expertise and existing IP, I would have thought ~4-6 months is the time you need to implement new chip from scratch for swos, which is very limited in features really.

They are however undoubtedly cheapest when compared power to cost.
I don’t think there are any other 10gb switches on the market for similar price?

How can you make such assumptions given how opaque MikroTik has been? I'm not convinced that MikroTik has any of those roles, as they certainly don't act like a traditional tech company.

I can definitively tell you that the CSS610 is a unicorn, mostly because of its small size. There is nothing else out there with its feature-set and size at any price. It could be an ideal switch for small work groups that deal with large volumes of data, but not with it's current software.

What's puzzling to me is why they opted to released a new "swOS Lite," instead of relying on swOS.

What's baffling to me is why MikroTik has remained silent when a chorus of people have cried out for information and help. Do they do this with all their hardware? I'm new to MikroTik and as of now, this is my first and last purchase from them. What a shame...

-MB

msimmons · Wed Mar 03, 2021 1:28 am

Below you can download the SwOS 2.13rc5 version for the CSS610-8G-2S+ device:
https://box.mikrotik.com/f/2d3d33561426401a8697/?dl=1

And for the netPower Lite 7R (CSS610-1Gi-7R-2S+) device:
https://box.mikrotik.com/f/089b908aede040b099c8/?dl=1

It should improve the management connectivity for the SFP+ interfaces. Other fixes and improvements are coming, but I cannot comment when the stable version will be released.

@EdPa Any real updates to give us from MikroTik? There's gotta be a stable firmware any day now, right?

Presto · Wed Mar 03, 2021 2:00 am

I have some bad news for CSS610-8G-2S+IN owners!
An anonymous source close to MikroTik just confirmed it to me. Yes indeed the CSS610-8G-2S+IN has been discontinued and will no longer be produced. There will be leftovers sold off to at least cover the losses of the failed CSS610 series. I feel sorry for all those who managed to buy them, now it is their problem and they are left alone with the problem. Now it is nothing more than a stupid box that nobody needs. The CSS610-8G-2S+IN was originally not designed correctly and the firmware will not fix it. For the future, do not buy a new device until at least one year has passed, it will help avoid unnecessary costs and headaches.
The only way to somehow recoup the loss is to try to get rid of it while few people know about this news and be smarter next time.

mbelanger · Wed Mar 03, 2021 9:55 am

I have some bad news for CSS610-8G-2S+IN owners!
An anonymous source close to MikroTik just confirmed it to me. Yes indeed the CSS610-8G-2S+IN has been discontinued and will no longer be produced. There will be leftovers sold off to at least cover the losses of the failed CSS610 series. I feel sorry for all those who managed to buy them, now it is their problem and they are left alone with the problem. Now it is nothing more than a stupid box that nobody needs. The CSS610-8G-2S+IN was originally not designed correctly and the firmware will not fix it. For the future, do not buy a new device until at least one year has passed, it will help avoid unnecessary costs and headaches.
The only way to somehow recoup the loss is to try to get rid of it while few people know about this news and be smarter next time.

While I wouldn't be surprised, your single historical post doesn't lend you the most credibility. Do you have any specific evidence beyond "anonymous sources?"

Hominidae · Wed Mar 03, 2021 11:05 am

..if there is a design bug, it is in here: https://www.marvell.com/content/dam/mar ... 015-05.pdf
Not impossible to imagine but very unlikely.
With v2.13rc25 mine is performing fine, without issues...and I would still recommend it for Home/SoHo use...I'd also rather go for a CRS version though ;-)