Cisco 9000 Series Aggregation Services Routers (ASR 9000)
MikroTik Cloud Router Switch
Likelihood to Recommend
Cisco
It is very well suited to act as your aggregator / core switch for mid to large facilities. it is flexible enough to really be useable in small environments but costs may hinder that. It has redundancy of power and management blades that does add a lot of peace of mind and security. Really the only reason you would not use a 9000 series is frankly cost and/or real requirements for performance. They have several versions of this model, plus they have an entire set of lines that can accommodate nearly as much as the 9000. Less demand or less of a budget can weigh in the decision to select this particular model.
MikroTik Cloud Router Switch work very well as layer2/3 switches in enterprise environments, aggregation or distribution layers. Example: in our case (ISP) we use CRS326 and CRS317 at multi-dwelling units to finish the customer lines, manage vlans of service and apply basic qos. They offer a good variety of ports 1/10G, which is perfect for connecting other ISPs or connecting corporate end users. MikroTik Cloud Router Switch would work fine in low-traffic Routing and Switching, you could configure L3 Hardware offloading and serve some significant traffic, but you may missing some features like, mangle, nat, firewall or other things that may be solved with other device in an upper layer of infrastructure. Based on our experience MikroTik Cloud Router Switch is not good for high performance traffic, they are not optimized for heavy L3 routing task. Example: if you use a CRS as core or router in a small DC or IX the result is traduced on high cpu usage and load performance. If you are looking for special works, MikroTik Cloud Router Switch in this aspect is out.
[The] upgrade process [is] overly complicated compared to NX-OS or IOS. New images and the current configuration need to be compiled into "golden IOS's". If you don't include the configuration, you will have a clean device with no configuration.
[There are] major bugs in every release. We have had to cycle through all of our routers 3 times in the last year for updates due to show-stopping bugs that did not come to light until after the changes were made in production.
[It has] terrible documentation. You have to mine their site to get to any documentation for recent versions of IOS-XR. If you make the leap from 32-bit cXR to 64-bit eXR, then the documentation is more or less non-existent. Due to the internal architecture of hardware itself, technical specs can change from software version to software version, so don't expect any sort of firm scalability numbers. You'll have to rely on your sales engineer for that.
The code for the switch is slightly different than the 2960X series that it is replacing, but still very familiar. It was relatively straightforward to work around this minor issue. The switch itself is solid and is very flexible as well as reliable.
Powerful features at a low price: MikroTik Cloud Router Switch provides a good variety of features that are not present on more expensive brands. Flexible deployment options: SwOS for simple switching use cases and RouterOS for more advanced configurations. Winbox is a fast and responsive tool for configuring, maintain and monitoring the traffic or other variable. Why it doesn't score higher, we think that the learning curve for new users could be hard. Sometimes the logic configuration can be unintuitive example: bridge filtering, vlan interfaces. Inconsistent UX Across RouterOS versions, some features may change without clear documentation causing confusion missconfig or incompatibility between versions. Documentation and support are poor, official documentation is fragmented and depht in some cases, the active community should be your best friend.
At the time (during 2020 - COVID) there was an issue getting the new switches due to circumstances around COVID with reduced work force, etc. Generally we have not had an issue getting the product in a timely fashion.
In some ways, the platform is a big improvement over our previous IOS and NX-OS devices: They offer version-controlled configuration staging/commits. They have a robust portfolio of network protocols and features even beyond datacenter devices. Due to the use of NPUs instead of relying entirely on ASICs for forwarding, new versions of the software are able to improve hardware performance and capacity. Unfortunately, I have run into more bugs on IOS-XR than I ever did on IOS or even NX-OS (which has a shocking number of bugs of its own) and you have to be a licensing guru to get your order right the first time.
Really, the only issue encountered when deploying the new 9000 series was attempting to copy a working config from an older series switch and applying it to the new 9000 series. Once it was explained that a new switch configuration needs to be built up specifically for the 9000 and deployed were the issues resolved.
When we are integrating the ASR9000 router with other devices then there should be the same device that can cater to the throughput. We can use the Cisco 9600 Switch which can be easily integrated and can handle the speed in terms of uplinks 40G can be handled. Adding to this Cisco DNA Center can be integrated to do the automation and monitoring purposes.
We chose MikroTik Cloud Router Switch because it met our technical requirements without significantly affecting our budget. MikroTik Cloud Router Switch offers a performance reliable and scalable for access and aggregation roles and is easy to integrate with our existing infrastructure (Mikrotik CCR). While it doesn't offer enterprise-class UX, or automation frameworks out the box, its disruptive focus, control and granular configuration convert it in an attractive option for ISP operations.
We work directly with our vendor/partner who works closely with our ability to pay at certain times of the year due to budget restraints of public education.
Depending on the model of 9000, it can be as simple of a setup as needed, or can be as expandable as required. The units we purchased only had SFP ports for basic trunk line configuration
We didn't need to buy new devices when we were increasing backbone capacity from 1G to 10G.
Due to the modular nature of the software, when there is an issue with any running services, we need not reboot the whole device which affects all clients and availability.
