May be great product in the future but at the moment it's not in prime time
June 13, 2019
May be great product in the future but at the moment it's not in prime time
Score 5 out of 10
Vetted Review
Verified User
Overall Satisfaction with Cisco DNA Center
It has been used for PNP, templating, swim, discovery. SDA is future use. It has been used in all of the remote sites. We are still in the early phase of production deployment.
- I think using the API to manage devices has great potential.
- The GUI is not great right now. Lots of bugs if I want to use the GUI exclusively.
- One question hangs around on my mind regarding using an API vs a GUI is why should one use DNA if the focus is on API and scripting? Why not directly run scripts using Python netconf and restconf guest cells.
- Auto Rollout feature in case of template failure
- Auto backup and restore function
- Add more programming languages on template like Python, Jinja.
- We have been using DNA from the EFT phase. We put lots of engineering hours into it. We opened lots of Cusco TAC cases which helped to find lots of bug cases. HWE helped to improve the product.
First of all we were not familiar with Meraki switches at that time. Also we were very excited about the SDA features and benefits. But we were not aware of any complications or bugs DNA would have brought into the system. One final note is that Meraki switches did not have that heavy processing power to handle a heavy load.
Using Cisco DNA Center
30 - Network engineers