Cisco Meraki Wireless LAN Reviews

We have deployed this solution both on private cloud and on-premises across at least 100 distinct locations.

I can't say that there are any additional features that we would like to see included in it. Our only concern at this stage is how it's licensed.

We have been using Cisco Meraki Wireless LAN for approximately four years.

It is very stable, very resilient, and very robust.

We don't have any challenges with the scalability so far. From our experience, it's quite scalable.

On a daily basis, we probably have an excess of 5,000 users on this solution.

There are no immediate plans to increase usage, however, there's probably a growth rate of about 5% to 8% per year for the next year or two.

This solution is not significantly hard to setup and deploy.

It's a manual process.

We deployed this solution across a complete government network over a three-year period.

We had a system integrations consultant working cohesively with us on it.

We don't like the licensing model and we think that it needs to be improved significantly.

I would rate this solution an eight out of ten.

I use this solution for wireless.

It is easy to manage and configure. The dashboard of Meraki is easy to use.

Currently, only a limited number of clients can connect to these devices.

I have been using this solution for three years.

Our clients are small and medium companies, and we didn't have any problems with scalability. Our clients may increase its usage in the future.

Their support is great. Its documentation is also good.

I used Juniper Mist. Cisco Meraki Wireless LAN is easy to use in the cloud.

It is expensive.

I would rate Cisco Meraki Wireless LAN a nine out of ten.

The flexibility, since it's a cloud service, is the most valuable feature of this solution. As well as:  

• The administration 
• Management of the whole platform 
• Development
• Deployment options in the cloud

There is only one particular thing that needs improvement. Sometimes, for example, when you need to open a ticket, although it's under the umbrella of Cisco, you still need to go to the Meraki support. We had issues with Cisco in general. We have multiple platforms from Cisco but when it came to Meraki, we thought to go to another support team to open a case. That's something that might be improved. My opinion and recommendation would be that when you open a case at Cisco, Meraki should be irrelevant. You should have the same support experience just as we have with Cisco.

In the next release, they should improve the way that you engage support. Once you engage them, they are quite knowledgeable and they are okay. There's no issue with that. 

It's stable. In terms of our users, we have guest users and such. It might be that on a particular day we have about a thousand clients and devices connected to the platform.

It's scalable. 

The technical support is good. We never had any particular dispute. From the technical point of view, the technical support is fine. The only thing is the thing that although it's Cisco, you have Meraki dashboards. 

We did have another wireless solution that was made up of bits and pieces from different vendors and obviously Meraki was one of the vendors that integrated everything together. So you had one platform from one supply manufacturer. That's a big plus for them.

The initial setup was quite straightforward. As always in technology, you have difficulties. It was normal on the second deployment because it was in phases. You will always have failures but that's normal.

I would rate this solution a nine out of ten and would recommend it. 

It's a cloud-managed network, which makes it easy to manage and to configure. You can configure the access points before it reaches your offices and can configure it through serial numbers. You can add the serial number of the access point and the Meraki dashboard. It's easy.

In a future release, they should offer a next-generation UTM, where you can manage all items and the network, and have it include a lot of security features like fingerprinting functionality.

The solution is very stable. It is a very manageable and secure system.

The technical support is very good. They reply immediately.

I work with various versions of the solution, including MR32, MR33 and MR42. We're a reseller of the solution. We typically handle enterprise-level clients.

I'd rate the solution ten out of ten.

We use our Meraki system to provide new IOD access and internal access for wifi devices.

It provides an easy login page for most students.

In terms of wireless network visibility, we have a lot more insight into what students are doing now. We can track down peer to peer very quickly and can just lock it down. If we find an offender that gets caught with the law, we can direct the authorities directly to them.

The solution also reduced our false positives by about 50%, as well as saves us time, money, and administrative work.

The management and upgrades are very simple and straightforward.

Traffic analytics give us insight, but they don't decrypt anything.

I would be interested in seeing more enterprise-level, advanced user features.

Technical support can be improved, as well as having more detailed capabilities to go without using an API.

I would rate scalability as five out of ten. It's kind of hard to say.

Their technical support is hit or miss.

The wifi solution that we had before wasn't great so we had to go with something else.

It's a pretty good value, but not great. Pricing is on a yearly basis for the Meraki solution.

The biggest lesson we've learned is that wifi systems are very complicated. My advice is to be sure you understand the depth that the system gives you.

I would rate this solution as eight out of ten. It's a pretty solid solution. It lacks the advanced features that I would like to see to do proper wireless engineering, but it's a pretty solid solution.

Our environment consists of five locations and we are using the Meraki APs in all of them for user/guest WiFi access.

This product has allowed us to easily create custom SSIDs for clients and carve out the necessary bandwidth for clients needs.

• Ease of use
• Central management
• Pretty reliable devices

I also really love their cloud-based dashboard which allows me to see all my locations in one place.

I believe every product always has room for improvement. When it comes to Meraki I would like to see them improve their support where an assigned engineer can take the case all the way to closure. Usually, you get a different engineer calling regarding the same ticket.

I am a system integrator. I help integrate Meraki Solutions. 

We have customers with offices in Sri Lanka who have other small resorts globally. We use Cisco Meraki Wireless LAN for the management and configuration without having to go to the site.

The most valuable feature of this solution is the application visibility, which is one of the main features.

We need more options for core switches. More switches with hardware capabilities that can be used at the core level. That would be very helpful.

It would be good to integrate with ISE in the future.

I have been integrating Cisco Meraki Wireless LAN for more than five years.

I don't have any issues with the stability of the Cisco Meraki Wireless LAN.

It's a scalable solution.

Most of our clients are enterprise companies.

Technical support is good but can be improved. I would rate them an eight out of ten. 

I am a design engineer. I work with Cisco Meraki, Aruba, Alcatel, and Ruckus.

The initial setup is straightforward.

I would say that they have adequate pricing.

I would rate Cisco Meraki Wireless LAN a nine out of ten.

There are a variety of use cases. It is being used in a community center, a school, a gymnasium, and a youth center.

It's a combination of constituents. We have teachers, employees/staff, students, parents, and visitors. We have many different users.

The most valuable features are the multiple types of user groupings and access management. For example: what, when, how long for, what is the performance, and what device are they using are all groupings.

Some of the built-in capabilities need to be improved. The radius capabilities for filtering by MAC address, some of the group-based policy management, even though they have more flexibility.

They need a better reading of device TACs, which are terminal equipment codes.

When you read a MAC address or a serial number, you can detect if it's an iOS or an Android device. Specifically, within the Android world, it can detect if it's a Samsung, an Acer, or if it's a Dell. In the Apple world, you can detect if it's iOS, iPhone, or an iPad.

Their TAC reading and interpretation capability are not as effective. For example, they may be reading a MAC address and reporting it as an iPhone, but it may be a Samsung. It's not just iPhone and iPad confusion, but iPhone and Android cross confusion.

There is a processing limitation when you have multiple SSIDs, above three or four.

I have been working with this solution for three years.

We are working with the original version of Meraki, not the latest version.

In terms of stability, it's relatively straightforward.

It's a scalable solution. It's pretty good.

We have never had to contact technical support.

We work with Meraki, Eero, and Ubiquiti.

The initial setup is relatively straightforward. It's literally a plug-and-play, once you set up on the portal. I would be stretching to find an issue.

Anything that is common to all of the access points is the same, You have to run the cables. Once you have done the Delta it's probably a couple of days to deploy.

It depends on what you want to configure or the level of configuration complexity. We have, for example, access points in a specific location that are broadcasting on certain SSIDs and providing access to only certain users or certain devices, and for specific services which have to be configured.  

If you generate an existing configuration, you can just plug it in and it will boot. If however, it requires a specific configuration, it will take time to configure the specific set of requirements.

We had a deal and we went for it. If I had to go for it today, I would reconsider, unless I get more competitive pricing. The gap in terms of performance, quality, features, and functionality has decreased significantly compared to what it was five years ago. 

Now they have much more. They used to be a startup and they did pretty well. They got into growth mode, VCs pushed them to grow and they started developing features and functionality. 

Amazon bought them. Now that Amazon has its backing, they should be able to grow and improve features, which is going to put them on a similar pedestal as a Cisco Meraki, and the same for Ubiquity. But those are just nuances. 

Today, it would be harder for me to push for Cisco Meraki.

Their biggest challenge is cost. Since it's been acquired by Cisco, it's an even higher cost.

If they are going for the long run it's good, but if you go too long, there is a cost component to consider and figure out, because the cost is something that is coming down with a lot of new solutions.

I would rate Cisco Meraki Wireless LAN a nine out of ten.