I finally got a batch of CRS317-1G-16S+RM and to my surprise, neither Winbox nor console allow VLans to be configured on the switch chip.
Default firmware from factory was 6.40.2. I’ve even upgraded to 6.40.3 to see, if that fixed the problem, but no joy.
The dynamic VLAN 3501 mentiones ports unknown, unknown, unknown …
A vlan can be created via winbox, but no ports can be selected.
A vlan can be created via terminal, with ports, but the sub-directories for egress and ingress Vlan tagging do not exist.
I’ve already raised a ticket with Mikrotik Support, but would like to know, if anybody else has come across this. I mean .. honestly … basic vlan configuration on a managed 10gig switch should be a given and is part of the specification.
Hmmm, have one on pre-order here in the US and was looking forward to it.
Have either of you tried SwOS or do you need the L3 capabilities? From what I’ve read only SwOS supports hardware LACP at the moment, I don’t know about other features.
I want to use RouterOS due to wanting to have one management experience. And using it as mpls lsr doing hardware routing/switching purly based on mpls tags.
Backbone functionality such as igp and ldp (control plane stuff) would then be handled by the cpu but that should not be any problem as all data packet handled by the system would be mpls pakets.
I’ve not looked at SwOS in a long time… but i always found it to be terrible.
As with Jimmy, a unified management system across the network is why those switches are considered in the first place.
I’ve been using RouterOS since 2.7 .. and well .. it wouldn’t be the first time, that something half baked hits the shelf .. but this is a bit of a bummer.
Hardware mpls offload look prommising… think of the system as control plane / dataplane
if you have slow cpu but some memory you can run protocols and get ldp running in the “control plane” but ingress and egress processing would be soly mpls label switching one will have to se what is lying round the corner.
A sowftware ip router working with hardware mpls switching in the datapath…
I have same problem.
every day I’m more and more disappointed in the products of the MikroTik! they began to send equipment that can not be configured directly !!! without losing any time!!!
I spent 2 hours for find solution for configuring SWITCH !! I dont have explication of this - MIKROTIK you should be careful when sending unfinished equipment to customers !!!
p.s. and I send for support question WHY and HOW it configure ? and here answer - Hello,
I wouldn’t use the 317 Series in Production anyhow at the moment.
supouts can’t be saved persistantly, so in the case of semi-crashes, where you can recover via console, the supout is gone after the reboot. So you never get to download the darn thing.
So far I’ve seen 4 Switches randomly crash loosing all management and the fault light coming on. No access via console possible or anything. Just completely unresponsive.
The switch fabric will continue to pass traffic as per configuration, but anything done in CPU/software won’t work, which means that basic features like port-span or QinQ are not an option.
And this continues as far up as at least rc52. We’ll have to see if rc61 fairs any better, but I certainly don’t appreciate, that we’re basically alpha testing Mikrotiks equipment. The current feature and stability level of the 317 can not be consider beta nor rc level. Nevermind stable.
+1 we have the problem that switch is not accessible from access port of a vlan. Newest Beta should fix this. We are testing this Switch in our office environment where we could solve problem’s. The SW is alfa at best. MT falls back to old behaviour. A new customer buying this switch will never consider MT again. This is very good HW and will be very useful in the future but MT is not able to make something like UBNT Beta store where anyone who buys knows this is no production environment equipment. It is very unprofessional selling this as a working product.
