I'll be requesting some help with my failed attempts to configure this bad boy! Hopefully I'm overlooking something simple. Coming from other hardware/software that I've used in the past I find the current implementation rather convoluted, but I am new to RouterOS so I guess I should expect the learning curve. I am definitely frustrated with the lack of switching features that aren't there yet, although I am happy that they have committed to adding features with every update. I received my CRS on Friday and have been fumbling through different configurations all weekend. Putting my new CSR125 on a shelf for some time, unusable. Lack of documentation on switching functions unclear with STP configuration beeing only for bridge interfacesĤ. didnt find a way to terminate vlan on a switch(SVI)ģ. Couldnt get "VLAN" and "VLAN Tagging" tabs to work at allĢ. The way from examples(to match default VID with a "In.Vlan Tran" rule and to apply a different VID) feels complicated. didnt find an easy way to assign vlan to a port or easly configure a trunk link and permit all vlans. This time i got CSR125 ros6.5, and boy.Īfter spending 5hours trying to acomplish the most generic switching tasks i felt stupid as faq because i failed:ġ. Virtual stacking (management and when you get bigger xconnect interfaces maybe even backplane)īeing huge fan of MT i get almost every MT new product to check it out and to play around. QoS policies (full 802.1p support if possible)Īnd when you get your 802.3at spec CRS's out for the corp/ent offices : Of course none of the above should go anywhere near that 600Mhz CPU if possible Jumbo frames (i dont know the chip/chips being used and haven't used a CRS yet, may already be supported) Correct use of a FIB + TCAM in the chip ** this to me is probably the main function that the CRS requires. SVI's/元 VLAN management for VLAN routing HP do these groupings quite well, super simple) Some key features I would like to see (many have already been said already) in order to begin using it is: Alot of vendors have straight forward illustrations of this (HP, Dell and many others). The tagging functionality should be straight forward on the CRS, a simple GUI window with Tag, Untag, Forbid options would be good. I think Omega's comments are a good place to start. Until this functionality exists, I won't be purchasing any of these, and I won't recommend them to anyone that is looking for a 元 switch. MT needs to be able to do this, ESPECIALLY on a product that you are calling a "fully capable 元 switch."' Otherwise, it's just another MT router. In this configuration, I can easily assign VL10 or VL20 to any switchport on the switch, tagged or untagged. Next, we turn Port1 into a dot1q trunk port which tags both VL10 and VL20. This enables routing between the two VLANs. So, we create two 元 VLAN's and assign IP addresses to them (an "SVI" in Cisco).
An example of what the CRS should be able to do (using Cisco): MT's VLAN configuration has always been overly-complicated and confusing.