Cisco Application Services Engine

Our main use case for Cisco Nexus Dashboard is to ensure that all devices have the correct code and to identify any configuration changes between the leaves. If they are not in sync, we try to have that notify us so that we can go and rectify it.

What I like the most about Cisco Nexus Dashboard is the easier way to know exactly which device is connected to where. It paints a pretty picture, and if there is a link that is down, it color codes it to indicate that you need to pay attention there, among other things. Those are my favorites.

I think Cisco Nexus Dashboard can be improved by making it easier to onboard devices because it is a little hard to onboard devices in my opinion, at least from what I remember. At least that was the case with the previous deployment where we were not using VXLAN technology. The newer version we are about to deploy again for this spine-leaf setup, and I hope it is easier to onboard.

I have been in my current field for a little over 15 years.

The first time when we got Cisco deployed, for some reason, it was not as scalable as how we wanted because the leaves stopped growing after approximately 150 or something. We needed to be scaled much larger, and that is when we pivoted from Cisco to Arista. However, I think it is coming back as they eliminated that problem.

On a scale of one to ten, I would rate technical support at a ten because if you do not know something, the TAC guys are going to walk you from end-to-end.

Prior to adopting Cisco Nexus Dashboard, we were using Cisco devices as one of our main switches that we work with.

I would describe my experience with deploying Cisco Nexus Dashboard as not that bad.

We do not use any of the providers like AWS, GCP, or Azure.

I have been using Cisco Nexus Dashboard for three to four years initially, and then got switched to Arista, and now it is coming back again as we just deployed the servers for those who are in the process of setting it up.I do not think Cisco optimizes the experience of a hybrid or distributed enterprise setup because we have Arista in our network too.I do not know how end-to-end visibility from Cisco affects my organization's troubleshooting capabilities.The first time when we got Cisco deployed, for some reason, it was not as scalable as how we wanted because the leaves stopped growing after approximately 150 or something. We needed to be scaled much larger, and that is when we pivoted from Cisco to Arista. However, I think it is coming back as they eliminated that problem.I would rate this review at a nine out of ten.

Cisco Nexus Dashboard serves as a dashboard to ensure that all Nexus devices are properly set up.

The feature I appreciate most about Cisco Nexus Dashboard is the ability to control everything in one centralized place.

This centralized place feature benefits my organization because most of our devices are Cisco, so I can see if something is going on with the device, if something is going wrong with the port, and other issues. It is literally a centralized place where I can see everything.

Cisco Nexus Dashboard is pretty solid, so I do not know what can be improved or what additional features should be included.

I have been using Cisco Nexus Dashboard for almost two years.

My impression of the end-to-end visibility offered by Cisco Nexus Dashboard is that it is excellent because you can see from one side to the other side.

Cisco Nexus Dashboard scales with the growing needs of my organization. We are a large organization, but not enormous. I will assess scalability further as my organization continues to grow, but for now, it works well.

I evaluate customer service and tech support for Cisco Nexus Dashboard as good, but sometimes it is challenging, and I have to escalate the case.

When I write a ticket for support, they respond immediately. I have no issues with that. It is just when they need to fix the problem that some people have to escalate because they do not have the knowledge or understanding of what is going on.

Prior to adopting Cisco Nexus Dashboard, I was using a solution called Splunk to address similar needs.

I considered the change to Cisco Nexus Dashboard because at the time I got Splunk, it was more command line oriented, with people doing coding and other technical tasks. Cisco Nexus Dashboard provides GUI visibility, so you can see what is actually going on through an interface rather than through commands.

My experience with deploying Cisco Nexus Dashboard is that everything went well because once you connect with the engineers, they will help you get everything connected. It is not difficult to do.

My experience with pricing, setup cost, and licensing for Cisco Nexus Dashboard is that it is expensive. They are not going to lower the price. If you want it, you are going to have to pay for it. It is good though. Once you have it, it is very good. Cisco Nexus Dashboard is expensive, as are most other Cisco products.

I did not consider any other solutions before selecting Cisco Nexus Dashboard because I always have Cisco equipment, so I am not going to any other provider.

I do not have any specific challenges with hybrid and distributed enterprise networks that Cisco addresses, because everything is set up so well that I do not have any problems.

The end-to-end visibility affects my organization's troubleshooting capabilities in that I do not use it as the main software. I have other software that I use to troubleshoot issues, but it is one of the tools that I can use. Most of the troubleshooting I do is through another software called Splunk, which is also owned by Cisco, and I prefer the coding part because I can track things better than just looking at Cisco Nexus Dashboard.

I rate this review as a 10.