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

Who is online