Big thanks to Mikrotik!
A power cycle finished the upgrade. Thanks.
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.
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.
works with this version but with different hardware equipment, if the CSS610 equipment is not connected
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.
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.
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?
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
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.
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?
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 
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!
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
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 !!!
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??
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)
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 http://forum.mikrotik.com/t/css610-8g-2s-and-vlans/144400/1
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??