My main use case for Meraki Dashboard is monitoring and discovering our network performance and what's working, then being able to dive in and assess and change configuration if necessary.
A quick, specific example of how I use Meraki Dashboard for monitoring or configuration changes is when I had reports of poor performance from a site. I found that we were getting some issues from the ISP, and using the dashboard, I was able to see the network going up and down and track it down to the ISP's router. This allowed me to log a call with them and they resolved it reasonably quickly.
Regarding my main use case and how I use Meraki Dashboard day-to-day, it simplifies the management and means I don't have to rely on skills normally held by a high-level engineer. My help desk and service desk staff can log in and visually see what's going on on the network without those advanced skills that might otherwise be necessary.
My network engineering teams structure and govern configuration templates across our distributed branch locations within Meraki Dashboard with one configuration template that goes across all of our sites.
Meraki Dashboard's automated alerts and event logs have not altered how my team handles configuration drift across our multi-site deployments, as we don't use that function.
We are not incorporating AI-assisted insights and root cause recommendations within Meraki Dashboard into our day-to-day triage workflows.
Configuration templates influence policy consistency across our distributed branches, and we don't do local site exceptions, so we have consistent policy across all of our sites.
We don't use alerting thresholds within Meraki Dashboard. Instead, we use an external software product to do all of our alerting across all of our infrastructure platforms.
When diagnosing remote client connectivity issues using Dashboard's remote tools compared to dispatching on-site technicians, I observe that we very rarely need to dispatch an on-site technician as our environment is very simple and the configuration is not complex. If a switch is down or if there is an issue, it's most likely a power issue, which happens frequently on many of our sites, or it's an ISP issue. Very rarely is it a network configuration issue.
Meraki Dashboard has positively impacted my organization by providing the ability for the service desk staff to see and do some basic triage, whereas potentially before they were running blind and making guesses. Now they can actually see it and understand more of what's going on.
Although we don't measure that ourselves, I have noticed anecdotally improved response rates and response times to tickets logged or incidents raised.
The best features Meraki Dashboard offers include a user interface that is reasonably straightforward, easy to use, quick, and responsive. It shows us what we need at a level that each user can determine what they want to see, allowing advanced users to dive deeper while also providing quick and easy things that help desk staff can understand.
I would also add that we are able to integrate the dashboard through to our networking monitoring and alerting solution via a very simple API, which has made life easier. I'm very happy about that.
Nothing comes to mind regarding how Meraki Dashboard can be improved, and I don't have any suggestions.
I have been using Meraki Dashboard for six years.
Meraki Dashboard is very stable.
In terms of scalability, we're not a big company, so we haven't had any issues with the number of devices we have in the environment.
I have had no problems on the few occasions I've had to call regarding customer support.
On a scale of 1 to 10, I would rate the customer support at an eight.
Previously, we were using Cisco switching, but we moved to Meraki partly because of the graphical UI and the ease of configuration. This meant that we didn't need senior engineers with years of experience to configure switches. We could have intermediate level engineers do the onboarding and apply the configuration template, making deployment simpler. Anecdotally, we have been able to assign those tasks to a more junior engineer than we would have previously.
My experience with pricing, setup cost, and licensing has been reasonably straightforward. It was a bit of an interesting change moving to the subscription model, but so far, we're six to seven years in, and it's been quite straightforward.
Before choosing Meraki Dashboard, we didn't evaluate other options.
On a scale of 1 to 10, I would rate Meraki Dashboard a seven.
I chose seven for my rating because it's good, I like it, and I'm sure there are improvements that could be made, but nothing comes to mind at the moment.
Meraki Dashboard is deployed in my organization as Meraki cloud, public cloud.
My advice to others looking into using Meraki Dashboard is to do your research and make your own decisions. I'm not a big person to give advice about what products to select, so I'm very cautious about that, but I would tell them we've had a pretty good experience.