Cisco 5000 Series Enterprise Network Compute System (ENCS 5000) vs. Cisco 9000 Series Aggregation Services Routers (ASR 9000)

It seems to me that it is a piece of equipment totally suitable for virtualization, it works perfectly either as an ISR or as an ASA Firewall. This 5000 series of equipment is a platform that is specifically designed and oriented to run VNF. This saves time and at the same time allows us to simplify operations.

Incentivized

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.

Incentivized

• Smaller footprint
• Less cooling required compared to physical hardware
• Easy to allocate more compute resources to virtual guests if required.
• Less power required compared to physical hardware

Incentivized

• [Cisco 9000] Series [Aggregation Services] Routers are exceptionally reliable when compared to other market options.
• One strength of Cisco routers, in general, is their compatibility with any standard market tools from other vendors.
• [It is] unmatched in terms of sheer performance.
• [It] comfortably supports very strong throughput requirements.

• Ease of configuration

Incentivized

• [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.

Incentivized

This depends on when Cisco EOL the product.

Incentivized

[I am] always impressed with Cisco products, from the functionality to the customer support.

Incentivized

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.

Incentivized

It is used due to its great adaptability in large networks since it allows you to use different technologies, which is a very important factor since you save physical space but also allow you to continue enjoying the services.

Incentivized

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.

Incentivized

• Saving on cabinet space due to smaller footprint
• Easier to ship and handle than physical hardware
• Princing is very similar to the combined price of what it replaces.

Incentivized

• 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.

Incentivized