Meraki MS Switches Reviews

When it comes to troubleshooting, in the past we had to take the console and do configuration changes, and we had to be on location or have a VPN connection to access it. But with Meraki, there is the advantage that you have dashboard access via the internet and you can work on it from anywhere. With Meraki switches, there is virtual stacking. Let's say you have two branches where two different switches are located. I can take a few ports from switch 1 and few ports from switch 2 and I can do a virtual stack between these ports. And there is a port schedule, as well. For example, some customers want to do make budget choices to save power or something. There is a port schedule option to give power for access points through these PoE ports on a schedule you choose, like during office hours. Morning 9:00 to evening 6:30, and it will work only Monday to Friday. I can schedule so these ports will be running those times only. In an annual scenario, this can mean more savings for the customer.

You can select multiple ports at a time in a checkbox, and you can do a port configuration. If uplinks are required, you can configure that, too. There are a couple of tools available in the Tools section where you can do ARP, Ping, LED status, etc. If any network goes down or is getting any warnings, you'll get an immediate amber symbol. We'll get alerts and an immediate email even if one link goes down or anything is wrong. We require some additional integrated tools for when a switch is down, like WhatsUp Gold, or SolarWinds. So on the back-end, we need to integrate our email servers into the process. We need more tools for that. But in the dashboard, it all comes together and gives greater visibility, including the UX pack if you want - everything will be there.

The features part is good. Everything in terms of access and everything else.

In terms of what could be improved, there's API. For example, we recently implemented Microsoft Azure. We have it integrated now into the dashboard for authentication. Dashboard authentication includes local users which we are creating in the dashboard itself. We integrated Azure with our local active directory. As the administrator in IT, I can log into the dashboard with my AD credentials only, so we used Xero and SAML with the Microsoft Azure. It's working fine. Similarly in the camera. Generally, the camera is in the cloud. In the camera, every field requires you to enter some information. If you have a cloud archive, it will be directed towards your Meraki cloud based on whatever storage license you have, 90 days or 30 days. But we worked on a different approach. We developed some more internal applications with other partners. We are pitching data from the Meraki camera, and we are putting into our internal storage with the Python script in the back-end.

Another thing is CMX. There is a location tracking for the employees who are inside, and with Meraki there is a Bluetooth option with a separate radio. They have a separate Bluetooth radio, Air Marshal radio, 2.4 and 5 GHz, for all the different radios, but it's all ELM mode in the old access points. It serves the clients as well as monitors the rogue access points. But in Meraki, we have a separate radio for it to monitor all the Bluetooth clients who are coming and who are identified from the dashboard. We will send it through the API to the location-scanning API to a third-party application and it gives you greater visibility. We can customize our own application of the dashboard. For example if you have a retail shop, you can put your store map on there and you can track the clients, like how many clients have visited. We can customize it. We worked on that customization pack.

In terms of troubleshooting, if we get more tools there is an issue. Our pack has some internal access, right? In traditional solutions we can go to the CLI and we can see whatever you want to change and you can play around with it. But in Meraki, if they got additional tools maybe it would help. In terms of MS I see some complications. There are some voice-related services that some customers are expecting, so they want to put an MS firewall in Azure or AWS, and they want to ship the traffic from that firewall. For example, I am at different branches, so the initial firewall will make the decision. They are looking at that kind of scenario. I hear from some of the customers with MS, that there are some voice-related, SIP services. So it's a limitation. If you have a voice service with AmEx, I saw something that SIP ALG will not support AmEx. So that's one limitation here.

I have been working with Meraki Switches for the past year. I have actually worked with all Meraki products, not only a particular one, as it is a complete stack. I've worked with them for a couple of POC's that we did for the customers. They were implemented mostly in firewalls and access points. A feature we recently implemented for one location was Mindtree.

In terms of stability, it is stable.

You can scale it up. You can take any traditional scenario that you have a license for and scale up. I'm working with 200 or so people, so I just bought a few access points and a few switches. If you compare Meraki with the traditional, every switch or every firewall and every access point, every WLCL switch in the traditional way requires some licenses. If that device has a MAC throughput capability, I need to go for another device. If there is a WLCL pack, it requires another device I need to purchase. But with Meraki, there is nothing like that, the license will cover the hardware, RMA, and the licensing plan.

Recently, it converted from the quote elimination to party-wise licenses. If you have a device license, you simply add the licenses and you can play around with it. There are more restrictions, like if you see access points with MR, ENT it will come with an MV, so it's not about the model. For example, today I have an MR42, tomorrow I'll buy some MR53 or MR87. It is independent of the model and you can add whenever you have the API licenses. Similarly, if you have a camera license, you can add. If you have MDM or MV, you can add. It's unlimited. It is scalable, and it gives you flexibility and security. Every device will establish a tunnel with official encryption towards the Meraki cloud and all the devices will be securely connected and it will take less than 1 kbps in terms of configuring data. 

We have worked on the homes of CEO's and directors and up to to hospitals, retail and manufacturing establishments. Everything is supported and scalable.

They give 24/7 support, so whenever you have an issue, you can write or call directly if you feel that it is higher-priority. You can simply call the toll-free number and they'll immediately come to the call and help. In terms of any troubleshooting, they will do it from their end. Because we have some limited access in terms of troubleshooting, if you want to do some changes like firmware-related bugs or something, they will fix it from their end on the back-end.

The initial setup is very simple. I ordered the devices and immediately the software is loaded and you'll receive a dashboard key so you can start the configuration. Once the device is running you can simply play around with it.

It only takes minutes to set up for basic configuration. If you're looking for integrations you may need to do some registration or back-end coding or something. Apart from that, if it's a dashboard it is a configuration template. If you have multiple branches, you can create one template for other branches.

I recommend Meraki MS Switches. If the user wants more flexibility in terms of configuration and manageability, I would definitely recommend implementing it.

On a scale of one to ten I would rate Meraki MS Switches a nine.

I am using MX400, MS320, MX250, and MS250. We also used MX64 before. We have replaced it with MX67.

The solution is efficient and easy to run.

The product has no CLI. The solution must provide a command line interface like the one in the Cisco environment with a proper iOS interrogation ability. It's the biggest thing for me because we don't know what these devices are doing half the time. It takes a long time to know we've committed a configuration change in Meraki. Sometimes, we have to wait for long before anything happens.

I have been using the solution for at least five years.

We have also used Cisco routers. They were plugged into NETGEAR Switches in our branches throughout the country. However, my organization wanted more visibility and the ability for our first-line support to do things rather than needing a higher technical level. So, we switched to Meraki.

The tool is expensive.

I will recommend the tool to an organization depending on its needs. It is a convenient product. Overall, I rate the product an eight out of ten.

For our customers, there are multiple locations, around 3,500.

My configuration is to do the configurations on Cisco Meraki Dashboard. There are MS Avant switches, MS switches, MS routers, et cetera. Mostly, I work with all the switches, switch modems and routers, and access points also.

The switches are very stable. 

It's able to expand.

The product is easy to set up. 

Sometimes, when we plug the new switch into the internet, they will upgrade there and it'll take time. At times, we didn't know whether the switch was operating or not so we have to take the console and we have to do some troubleshooting. In the console, we can find out there if the Cisco Meraki switch is not connected with the Meraki cloud. 

The MG21 is not working on a 5G SIM card. It requires 4G SIM cards. Therefore, we are using two links, an internet broadband link and one for MG21 that is on SIM card based for small sites. We all suffer a lot of issues for MG21. 

I've been using the solution for five years. 

It is stable as a product. The solution is reliable. There aren't any bugs or glitches. 

It is a product that can scale. It's not a problem.

Typically, if I run into issues, I'd run them by my team lead. I don't reach out to Cisco directly. It's a good solution. We don't run into many issues. 

I previously used Cisco and HP switches. 

I've also used an Alcatel switch.

The solution is very straightforward, actually. It is not complex. This is a simple product to configure.

In terms of the ease of setup, I'd rate it a nine out of ten. 

I'm not familiar with the exact cost of the solution. 

Our organization has a partnership with Meraki.

It is a good product and it is scalable. It is not too complex in terms of configuration. It supports a lot of technology.

I'd rate the product eight out of ten. 

We are using it for local LAN switching.

Quality of Service is easy to deploy. The ease of deployment, in general, is valuable. It is easy to do port configuration and VLAN assignments.

On the switches, I don't know a whole lot that I would change. Different levels of switches have different layer 2 and layer 3 functionality. It's always nice to have layer 3 functionality across the board if you can, but that drives up the cost. 

They've got different lines for different amounts of layer 3 functionality. However, on their models that do include full layer 3 access, when you choose to use layer 3 on a switch, it doesn't have the full functioning routing capabilities of an MX firewall. It can be limiting in some of those aspects. I have found myself in a situation where I thought I was going to have the ability to do all the routing from an MX firewall, but even on their fully functional layer 3 switches, you don't have that. There are drawbacks. So, it is not just a, "Oh, I can use a switch instead of a firewall for the routing part of it." The answer is, "That's probably not a good way to think about that."

I have been using this solution for six years.

They are rock solid. I've got hundreds of these deployed, and we rarely had any issues. Meraki support is always great to handle advance replacement regardless of how old it is. It is really good.

Their support is really good.

The setup of all Meraki products is extremely simple.

We don't use standard licensing. Most of the time, we use the advanced security model. 

If there is a drawback to Meraki, it is the cost, but you also have to evaluate it based upon the other factors that you do get. Their support is really good; their hardware is really good. The ease of configuration and deployment is really good, but it is more expensive than most.

If you're looking for a solution that is easy and quick to roll out, you can go for these switches. If you want to deploy them without having somebody on-site, you can hire somebody very inexpensively to plug these up and configure them remotely or do advanced configuration beforehand. For deployments of a changing environment, these are the best switches I've ever used.

I would rate Meraki MS Switches a nine out of 10. There is something that could be better, but I don't have a lot of performance needs that drive that situation.

I use the MS series when I need to add power over ethernet (PoE).

This product has QoS, decent visibility of what's going on, and it's a managed switch.

Mandatory maintenance is an area that needs improvement.

I have been working with Meraki MS Switches for between five and ten years.

These switches are really stable.

I've used their lower-end products, and I haven't really looked at the larger units with additional ports. As such, I can't really say, although I think that there are some level 3s and even some level 4s.

At each location, there are between 15 and 20 users.

The technical support is very good. They are responsible and knowledgeable. On the Meraki side, you get through right away, whereas, on the Cisco side, you put in a call, and then it is difficult to predict when they will return it.

I work with a variety of Meraki Switches including the MS series, MR series, and MX series.

Prior to using Meraki, I was using a lower-end switch from Cisco. It didn't have any support requirements and my boss wanted me to get rid of anything that required maintenance. For this same reason, we will be getting away from using Meraki switches, as well.

The initial setup is easy.

As a one-person operation, I manage 15 or 16 locations.

The yearly maintenance fee is $100 and you can purchase used switches for about $200 each.

My advice is that this product may work well for a smaller shop, where they do not have many devices to pay maintenance fees for. I have 15 or 16 locations and combined, these have many switches and access points. For example, I have more than 45 devices in total, and paying $100 for each, annually, surpasses the amount of my initial investment. This is the reason that I am changing to another product.

In summary, this is a good switch but I just don't like the ongoing cost.

I would rate this solution a seven out of ten.

Meraki MS Switches have revolutionized our network operations. With cloud-based management, deployment is effortless, and monitoring is streamlined.

Meraki MS Switches have been invaluable in our network management. Compared to other switches, Meraki stands out with features like Power over Ethernet. This capability, along with remote manageability, has transformed our network operations, allowing us to implement changes quickly and efficiently while maintaining our organization's standards. It has been a refreshing change, making our tasks easier and more streamlined.

The most valuable features of Meraki MS Switches are their reliability and simplicity. Once they are plugged in, they just work without needing much maintenance. They are dependable in various environments, from office to field settings. With Meraki, you can trust that they will perform reliably, which has been my experience.

One area where Meraki MS switches could improve is offering smaller switch sizes for distribution switches, as not all networks require the standard 24 or 48 ports. Having more compact options with fewer ports would be beneficial, especially for distribution switches with only a few connections needed. This could help optimize space, power usage, and cost efficiency, particularly for networks with many end-user switches and few distribution switches.

I have been using Meraki MS Switches for over a year.

I would rate the stability of the product as a ten out of ten. I have not faced any issues so far.

I would rate the scalability of Meraki MS Switches as a solid ten out of ten. We have approximately 20,000 end users at our company.

The technical support is excellent.

Before Meraki, we used a mix of Cisco and other brands. Then we switched exclusively to Cisco and eventually to Meraki.

I would rate the easiness of the initial setup as an eight out of ten. The deployment of Meraki MS switches typically takes a few days. We prepare parameters and schedule remote sessions with our network administrators. The actual session lasts about an hour, but the whole process involves coordination and preparation, including in-house support from an external company.

I would rate the costliness of Meraki MS Switches at around seven out of ten. They are not cheap, but I find them to be a good value for the money. However, I would prefer if the prices were a bit lower.

The analytics and dashboard functionalities of Meraki have greatly enhanced my network monitoring. While I primarily use it to monitor basic parameters like bandwidth and connectivity, it allows me to quickly spot potential issues and react promptly, despite overseeing a wide area.

In high-density environments, my experience with Meraki MS switches has been positive. They handle multiple wireless networks cohesively, including those for office and public use, without issues.

Overall, I would rate Meraki MS Switches as a nine out of ten.

We are partners of Meraki and operate as a service provider for Meraki switches, notably the Meraki MS Series 410, 420, and 450. Our responsibility is to help customers deploy these solutions, which are always situated on-premises.

The main use cases for our customers include end-user connectivity, IP telephony, and security purposes such as for the cameras and access points.

The top feature of Meraki MS switches for me is Layer 7 application visibility. Another positive in general is that you don't need to set up a console to the switch itself; it dials in to a single dashboard where you can completely manage all your network devices.

In my opinion, there's room for improvement cost-wise. With Meraki's licensing terms, you're required to pay an annual licensing fee, which can be for a one-year license or perhaps a five-year license. But if you analyze the costs involved, there are huge expenses incurred as far as the licensing is concerned. It's very costly.

When you see the cost of the device and the cost of the license, they're almost the same. So let's say, for example, a device costs $4,200 and you go for a three or four year license, it will cost you the same. And that's for everything; for the wireless, the switches, the firewalls, everything.

Of course, the total costs depend on several factors, including the customer requirements, the service provider, and the service integrators (which may have their own partnership bias). With Cisco partners, there are gold level partners which will have different discounts to the silver partners, for instance. Given these factors, I always try to get the maximum discount from the vendor so I can offer a solution to my customers at the lowest margin.

Apart from costs, one improvement that I would like to see in terms of features concerns the mobile application. Most users of our switches are now on the web-based interface and I feel it's time for Meraki to start developing the mobile app more seriously, because it's currently not up to standard and a lot of people aren't using it.

I've been using Meraki MS Switches for about six to eight years.

For the cloud license model, the stability of the switches largely depends on your Internet capability. For example, you will want to have both primary and secondary backbone connections for the Internet, and that's it. The stability of the hardware is fine.

I would say that it's scalable, especially in the sense that there are models up to at least 10 Mbps and at the upper range there are 10 Gbps copper switches. Then there are switches that support 1 Gbps fiber as well as 40 Gbps fiber (via QSFP). Thus, there are enough models to offer the scalability that you need as far as bandwidth is concerned.

There are fixed-model switches and also some older model switches to choose from, so it depends upon the customer's requirements to decide on their own solution. When it comes to scalability, there are various options available. 

Cisco is always top-notch when it comes to technical support. It's reassuring to know that they will be there to assist you in solving your issues. Of course, there are sometimes priority cases, but even then they make sure to be available to help you resolve the issue. It doesn't matter if you're a customer, a partner, or a service provider, they provide an excellent technical support service.

Positive

The setup is very easy. It's typically a one-touch provisioning process and it's like not traditional switches where you have to put in a lot of effort bringing the switch up and running with a basic configuration. With Meraki switches, all you need is a status page where you can log in locally. As soon as you connect it to the Internet, the device is on board and on the cloud, and you can start playing around with it.

You don't need a lot of technical staff to implement the switches. One engineer is capable of doing it alone and, in fact, most of the time it just takes a single team member to deploy. Naturally, this would be an individual who knows the product inside and out, to be able to deploy without anyone's help. You also need a few remote hands who can rack and stack the equipment, but as far as the configuration is concerned, only one engineer can do everything.

I had one scenario where I had 120 devices divided into three different models. Four of them were Layer 3 fiber switches which acted as the core switches and 16 of them were fiber switches for distribution, also with Layer 3 capability. Then we had almost a hundred devices acting as access switches, which is normally Layer 2 PoE-capable switches where we have a couple of SFP ports for the uplink. All of this a single person would be able to deploy in five working days, at eight hours a day.

When it comes to maintenance, it depends on the size of the infrastructure. In a retail mall, for example, you will have hardly 150 switches, compared to a big hotel or apartment building where you will have more than 200-300 switches. With those kinds of deployments, you will have to have multiple people to address the multiple issues with the guests.

There is a lot of scope for ROI with Meraki, mainly because your headcount will go down. With Meraki switches, you don't need to have too many people around to manage the infrastructure, and you don't have to travel much to maintain multiple branches across the globe.

Additionally, you won't need to spend much in terms of reporting tools, log tools (e.g. log collectors), or anything like that because everything is included in the product. There's a lot of sophistication and features that Meraki brings in terms of Layer 7 application visibility. You really have complete control over the end-users infrastructure.

If you buy a license for one switch, it will include the licensing for the device RMA, device failure warranty, technical support, and everything else. Also covered is support for software updates for future releases. It's a single license for everything and there's nothing that customers need to pay in addition to the license.

I would rate Meraki MS Switches an eight out of ten.

I use Meraki MS Switches for cloud-based management and web visibility, which I can control from a single pane of glass. I have a controller that lets me manage all devices.

I found the cloud-managed dashboard most valuable in Meraki MS Switches.

Management from a single dashboard is what I want to see from Meraki MS Switches.

The level of stability of Meraki MS Switches would depend on the environment.

My rating for Meraki MS Switches is nine out of ten in terms of scalability.

The Meraki MS Switches technical support is good, so I rate it nine out of ten.

Positive

The initial setup for Meraki MS Switches was straightforward and had no problems. The product is easy to manage and deploy. Deployment only took one week.

My company deployed Meraki MS Switches based on requirements. That was the only deployment strategy.

My company pays for Meraki MS Switches yearly. Pricing-wise, the product is relatively inexpensive.

My company is both a reseller and user of Cisco Meraki solutions, including Meraki MS Switches.

I work on different models of Meraki MS Switches.

My company has multiple clients using Meraki MS Switches.

I recommend the product to others for cloud-based management. You can manage everything from the cloud.

My rating for Meraki MS Switches is nine out of ten.