Cisco Cloud Services Router could improve the GUI.

If you lose connectivity to the cloud, it is difficult to establish connectivity between the hub and spoke. 

We tried to implement VPN services but it is missing. ISR or ESR router services are also missing.

I'd like additional features connected to my network for video design, topology design, and graphing. For example, the topology provided is not enough and should include where traffic is coming and going. Normally this feature comes with firewall services, but it would be great to have it included and managed with cloud services. 

One central area for improvement in Cisco is its product line offering. Cisco has ISE and other products, such as DNS Center and other components. Instead of small to medium-sized customers purchasing devices and maintaining the devices, it would be great if customers could have subscriptions.

A CAPEX/OPEX model instead of that Cisco code, where the pricing model is subscription-based, would give much better flexibility for the customers. The pricing and model for Cisco Cloud Services Router and other Cisco products could be improved.

One good example of what I want to be added to the Cisco Cloud Services Router in its next version is for it to be more of a plug-and-play product. For example, Juniper has developed QR codes, so if you need to plug in a device, you scan from your phone and connect to the internet. That's it. You can provision the device remotely through the cloud orchestrator, so I want to see a similar function or feature in Cisco Cloud Services Router.

Cost is a big factor. We would like to see the price reduced.

The ease of use within the AWS environment needs to improve. Sometimes, it is very esoteric in how you use it. Therefore, you have to learn to use it, then you are able to.

It is too complex. It is not easy to set up, even with the documentation that they provided. It is a little confusing.

I would like a GUI interface. The command line is not very straightforward, especially if you don't use it every day.

They have an online registration that happens after they pick up block months. If they could decrease to yearly or something, sometimes the device is not cell phone accessible. That becomes an issue or challenge for us. If that can be improved, that would be really great.

I would like the ability to moderate between devices on-premise to off-premise. This would be a vast improvement.

In the next release, I would like them to add the ability to track a security feature to track the various IPs that come in.

In the next release, I'd like Cisco to add automation functions and the ability to monitor the environment and network status.

Cisco Cloud Services Router could improve by having more features. It is lacking features, such as virtualization and containerization. Additionally, there should be increased security and connectivity between routers.

I would like some deployment examples and guides specific to AWS VPCs and how to separate your subnets. Then, how they tie-in with the Internet gateway and any NAT services that we are running on our VPC. This would be extremely helpful. Thus, a lot more detail around deployments would go a long ways towards easing customers' fears.

We need to use older versions as the newest options are very costly.

The configuration is difficult.

We find the installation process to be hard.

The version of this solution that we are using does not support the LISP protocol. The new versions support LISP, which helps with the aggregation of routing across the landings.

Over the past couple of years, I've noticed that the Cisco CLIs and web-based interfaces have changed. As such, there is a bit of a learning curve for people. It is understandable that newer technology is different, but it would be helpful if the interface had more in common with the older, legacy systems. There should be a system in place to help existing users make an easier transition to the newer interfaces.

It does the job, but it's not cloud native. It could be even better, like having a single pane of glass and being less expensive. However, the product works.

The possibility to use on-premise the same protocols as they're using on the cloud. When we want to do a high availability architecture, we have to use AWS features. The Cisco does not give you these features.

It could grow or adapt to changes in the cloud. For example, cloud does not support autoscaling. When people want to grow, they have to do manual activities.

Cisco should improve on the operation due to a clock signal component failure. I would also like to see better security, where there are more access controls and data confidentiality.