We just raised a $30M Series A: Read our story
2019-03-04T12:51:00Z

What needs improvement with Cisco DNA Center?

71

Please share with the community what you think needs improvement with Cisco DNA Center.

What are its weaknesses? What would you like to see changed in a future version?

ITCS user
Guest
66 Answers

author avatar
Top 20Real User

The architecture should not be limited only to the USXC as a platform. Let's say if I'm referring to the Catalyst 1000 Series or an MB Series of an SG or FX. Due to the fact that there are mid-market and commercial customers who are using such kinds of product lines apart from the Catalyst 9000 or Cisco UCS architecture, they should all come under a single pane of glass. Any new product should be added right from Cisco itself. The network automation should not be limited only to Cisco, as there may be customers who are using Palo Alto firewalls, or they might be using Ruckus for wireless. There has to be some sort of integration with a third party. The integration of Cisco DNA with a couple of leading CRMs or ticketing solutions would be ideal. The solution can be quite pricey.

2021-06-22T17:21:07Z
author avatar
Top 20Real User

With their provisioning status, if there's a failure in provisioning or in some type of task that DNA is trying to push out to a switch or whatever device, sometimes the task status errors or the provision errors are a little bit big. I think they could provide a little more detail to someone when a task fails. It's an error code that tells you that this task has failed, but it doesn't get too deep into why it failed. The task failure reporting or provisioning failure reporting could be a little bit better in the UI, with more information given to the user. From the CLI you can get much more information from MagLevs. Also, the UI could use a little bit of improvement. I know that things have gotten a lot better in version 2, but I haven't worked with version 2 yet. A feature that I would like to have seen is the true debt disaster recovery, which is now available in the 2.2.1 version. More detailed information would be helpful, but you can get that information from the CLI but not everyone is comfortable working in the Linux shell.

2021-03-18T23:01:42Z
author avatar
Top 10Real User

We have had a lot of problems with the Cisco switches and have needed to upgrade the operating systems, which means that we have to upgrade the DNA. When we upgrade the DNA it means that we have to upgrade the ISE, also. If it is a large cluster then this process is painful. DNA Center has been on the market for a few years and they need to update it.

2020-03-30T07:58:05Z
author avatar
Top 20Real User

The network, data center, and SD-WAN are all being treated as different services, but I would like to have only one solution to manage all of them. Data is traveling from the inside to the outside layer, and I want to be able to fully control all of the data going in and out. It should not be set up as multi-service, but rather a single one. If you have old Cisco hardware such as switches or access points, or they are from another vendor, then they will not work with this solution. The hardware will still function but you will not be able to control it with DNA.

2020-01-12T12:03:00Z
author avatar
Top 20Reseller

The pricing of this solution could be improved. There is a limitation with the number of VRFs that you can have in your network, and this has caused us problems with some customers. This solution does not support IP version 6. I would like to see better integration with Cisco Meraki.

2019-12-19T06:32:00Z
author avatar
Real User

Better compatibility with third parties and to other Cisco products because if versions are not perfectly matching requirements, it gives a lot of problems.

2019-03-04T12:51:00Z
Learn what your peers think about Cisco DNA Center. Get advice and tips from experienced pros sharing their opinions. Updated: October 2021.
542,029 professionals have used our research since 2012.