Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Score 9.6 out of 10
N/A
Cisco 9000 Series Aggregation Services Routers (ASR 9000) are designed to support carrier edge networks.
N/A
Juniper MX Series
Score 9.9 out of 10
N/A
Juniper Networks describes their MX series as a robust portfolio of SDN-enabled routing platforms that provide system capacity, density, security, and performance with longevity. MX Series routers support digital transformation for service providers, cloud operators, and enterprises.
N/A
Pricing
Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Juniper MX Series
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Chose Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Each vendor has its advantages and disadvantages, I have had the opportunity to work with both ranges of products and they are quite stable, but personally, I prefer Cisco.
Juniper MX Series
No answer on this topic
Best Alternatives
Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Cisco 9000 Series Aggregation Services Routers (ASR 9000)
Juniper MX Series
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.
It is well suited as a WAN/Internet Edge device. It is easy to configure BGP, contexts and routing instances. Its suite of tools has saved our organization money by being able to provide services (tag stacking, for example) that our provider would normally charge us more for. Due to interface cost this would not be appropriate as a LAN aggregation device.
[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.
Juniper (Junos) and interoperability. Junos is so powerful as a troubleshooting tool and also as a configuration tool. We had test and roll back configurations which is very helpful. Being able to link to over vendors equipment and extend features is very nice to have.
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 preferred Juniper over Cisco for our WAN/Internet routing needs for a number of reasons. First was the price, the Juniper offering was much more competitive than Cisco's. Secondly, was feature set, Juniper's implementation of routing protocols, routing tables, and forwarding options are better thought-out than Cisco's (not to mention Juniper's longstanding use of commit/confirm/rollback features, which Cisco has only started to use recently, and only on some of their products).
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.
