Please share with the community what you think needs improvement with Cisco Meraki Wireless LAN.
What are its weaknesses? What would you like to see changed in a future version?
I am new to this solution. At the moment, I am not the right person or in a position to suggest something new or point out something that's lacking. I time to use it properly and see the pros and cons of the product and the requirements regarding our business. The dashboard could be a bit better. I'd like to see more information about the whole controller and APs. It should be as simple and convenient.
You're starting to see CO2-type sensors come into the classrooms and stuff like that. So it would be nice to build some "if-then" functions into IoT-type sensors. For instance, if a classroom has high CO2 levels, you could automatically open the Windows and use heat exchange to bring in fresh air into the room. At the same time, you could have the temperature control adjust automatically so it doesn't get too hot or too. So you would need to plug in some configurable where you collect the output from the sensors and have it carry out some small actions based on that. I think it's well within Meraki's capabilities.
They're great. If there's anything that they need to change, it is just simplifying the site to which you go to make changes on the admin side.
Overall the solution needs to have more time to mature.
The problem with the solution is that if you go for firewall, then there is no SSL encryption available. If you are talking about deep packet inspection, that is not available. If you want SSL encryption, then you have to integrate with Cisco Umbrella. If they could work on the Meraki firewall hardware, and add SSL decryption as well as more application control and deep packet inspection, that would be ideal. Also in Cisco Meraki access points, MAC filtering is not available. If they could add that feature, that would be great.
The solution should be more secure. It is overpriced and more expensive than Hauwei.
Its licensing can be better.
There could be more functionality.
The ease of use is average. It could be more user-friendly. The initial setup could be simplified.
It is super expensive for what you get. I just wish it was less expensive.
The throughput of the switches for wireless could be improved. I am expecting more from it. The bandwidth should be improved. It should be increased.
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.
On the performance side, there are always updates to different versions. It's more just getting it out to the client-side that's often the issue. The licensing could be a bit better. They should market Meraki as a mid-level solution for SMBs. There are a lot of SMBs out there, and they could use this technology.
This solution could benefit from a heat mapping ability so that you can tell where the hotspots are, and where the good signals are. To have that be available from within the management software would be fantastic.
The solution should be open to introducing more IoT sensors and to have a more complete solution to medium-sized customers. The solution could saturate more of the market, as likely 80% of the market would like to see more simple solutions such as Meraki. It would be ideal if you didn't necessarily have to go to professionals to get a product like this. It should be sold more in the retail space. It would be great if the solution could integrate with Amazon Alexa. We'd be able to leverage Meraki and build more intelligent homes and businesses. It would help us build new items we could deliver to our clients, and to build better B2C relations. It would be nice to have licensing that stays in place while the system is being renovated or changed. If there was a way to have remote WiFi to support local connections during issues, so that technical support doesn't have to shut down the entire network, that would be great. If there was something like a robot that could continue running the network while there are licensing or technical issues, so that WiFi never goes down, that would be an ideal situation.
The annual maintenance is something that needs to be changed.
I would like to see more cybersecurity. I would like the ability to go in and enhance security. Because WPA2 is becoming obsolete, many devices are now WPA3, but the challenge is that a lot of devices are not yet there. I would like to be able to go in and do monitoring, similar to ASPM. ASPM has the ability to monitor who's joining and who's active. It supports two-step monitoring. The stability of Cisco Meraki Wireless LAN can also be improved.
The user interface needs to be improved. We would like to see the DNS Proxy and some additional security enhancements in the future.
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.
When the license expires, access to the Cisco cloud stops immediately. They should introduce a grace period of 60 days after license expiry because as it is now, it automatically goes down and there is no grace period. There should be better integration with other products.
Initially, I liked some of the filtering features, but that's one of the components that we ran into problems with. We don't use it as much anymore. This is one of the things that I'm trying to find out if Aruba does better. For example, I like all of my iOS devices to go on one network so that if they try to do iOS updates, we have an Apple server online so that they can just pull the iOS updates from it instead of having them on other parts of the network. Also, we're a one-to-one school where we give laptops out, and I'd like to be able to block the old laptops from being able to access the network. That means that the students are forced to use their new laptop, as opposed to an older one. It would be really helpful if there were a way that the access point could determine whether the client has an AC radio and if so, force it to try and connect to there first. As it is now, it lets the client determine how it wants to connect. This is the case with wireless in general, but it would be nice to have this option.
Currently, only a limited number of clients can connect to these devices.
It would be better if they enable full integration with Cisco's cloud-based network in the next release. A couple of years back, we did an integration with Cisco Identity Services Engine. There we had some integration issues. Cisco had access in the portfolio, but Cisco Wireless wasn't fully compatible with that integration. If we sell Meraki, we can't promote some other Cisco products because there's a clash.
I would like to see integration with sensors.
It's a little bit customizable, but that's where it probably has one of its downfalls. It is not as feature-rich as some of the others. The customization needs to be improved because it's pretty locked down. You can't customize it much. In the next release of this solution, I would like to see the Radio Control feature included, and improved customization on the radios. Also, it needs more ability to control it. It works well but you can really change it a lot.
The advanced configuration makes it so that any user can enable some of these features without having to ask them for help. It's designed like this because their business model targets people with mid-range expertise. I think Meraki's doing fine, but I had to leave them because I came from using Cisco before they bought Meraki — which gives you so many options that you can expand upon that it's absolutely mind-numbing. As you learn, you miss some of those features when you switch to something else. I did enjoy using Meraki and I would use it again, but I wouldn't be using it for a large office because they don't have the kind of manpower to properly administrate it. If there are advanced features that you can have enabled, they should allow users access to that in an easier manner.
The price could be slightly lowered to make it more competitive in the market.
The Meraki platform needs better on-premises management options.
The connection to the internet via Wi-Fi, for external people who frequent the customer branch, needs improvement. In the next release, I would like to see the central control plane have the flexibility to control and distribute policies to all LAN networks, balance the traffic, and the performance based on application monitoring.
The price of Meraki Wireless should be reduced to make it more affordable. When we are using SSID roaming, it is not flexible in terms of which AP it connects to. It will not switch to the closet one, but rather, it will maintain a connection with the first one that it had connected to. This has a negative effect on signal quality because as we move around the building and the signal from the original access point gets weaker, it remains connected to it.
We haven't had any issues with the solution. We like the way it works. There isn't anything I can think of that makes me worry that it might be lacking in a certain area.
The product is fine as it is. Having been in the IT industry for nearly 20 years, there's nothing that jumps out at me. The product is improving all the time. It could be slightly cheaper but it's fine. It's actually a very good product.
In many wireless solutions, there are a lot of things that can be added, like WiFi 6. Meraki should share its viability roadmap. It is really hard to know which functionality will appear or when they will be available. It is also hard to know which features are available now but are not visible on the dashboard. In France, there's a law that requires we should keep a log of connection for 1 year, so it would be really nice to have a solution or feature that allows us to keep a log in the cloud during the year with log rotations and secure log authorizations. Right now, in France, it is not possible.
In terms of improvement, we're waiting on is the new standard WiFi 6. That's really where the research comes into. With wifi coming out, we're going to refresh everything. Hence we're going to look at the top three players. I'd like better integration with security providers.
The stability of this solution is not good. It needs improvement. Operation-wise this solution has some problems and the functionality is not very good. In the next release, I would like to see a third-party high tech center to connect multiple users to a particular network.
Some operations can be quicker within the solution. When it is deployed and registered on Meraki cloud, when you move, for example, a device from one customer to another, you need to un-claim the device from Customer A, and then claim it to Customer B. This process can take one hour. If they could shorten this time to about 10 minutes or so, that would be ideal. The commercial version of the solution could be cheaper.
Unfortunately, we have to deal with European privacy laws and as far as we can see, the solution is not compliant with these. It's why we're not able to continue with Cisco Meraki. They need to become compliant with GDPR laws. They should make the solution more transparent so we can better see what the system does.
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.
The technical support for Meraki needs improvements made to the waiting times. The explanation when you have problems, and the tools in place to follow the case, are not very good. They should reconsider the rules under licensing. If you do not pay your subscription within the month of it being due, the use of the product will stop.
These products are more suitable for SMB rather than an enterprise for one of the listed Access Points like MR-20, Whereas MR-33 and above models covers and target the Enterprise customers. We would like to see Wi-Fi 6 support for devices sold in the Middle East, however, Meraki has introduced WiFi-6 where we would strategize our GTM plans for WiFi 6, where we would offer WiFi 6 to specific customers with extensive needs of high WiFi availability in KSA.
The price is good, but it could be improved. The camera needs improvement because currently, it only accepts a 128-gigabyte memory card. It's too small to record a video. In the future, I would like to see IP telephony in Saudi Arabia. It is currently not available.
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.
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.
The logging sometimes doesn't give us the granularity needed. Some of the rules are a bit more complicated. The switch ports on the routers are not individually addressable, in the sense that with a switch you can tell what MAC address is on what port but with the security appliances, you can't, which would be beneficial for troubleshooting. I would like to see more information on what is plugged into each MX switch port. I would also like to be able to see that the templates would be able to be used because we're in MSP, so if I create a template, I have to recreate the template with each of our clients. I'd prefer to create one template and then personalize it for each client which is a little extra work that way. The dashboard security is not as good as it could be in terms of provision users. If I provision the user at the high level, I'd like to give them rights to our customers so if I have a new technician, I have to go and touch each customer and add that technician which is kind of silly.
It's performing well, really well. We don't have any issues. We only have issues if there is a lot of rogue APs in the neighborhood and that not Meraki's fault. There are many improvements that can be made. Mainly in the radio parts, they need to include some more features but it is hard to say exactly what we want. We had have a few cases where we could not use Meraki because it could not do advanced routing features, and so on, but it is very unlikely that Meraki would include that in the next releases. We have tried to push it because we are quite a big reseller in the Nordic region.
Let the community know what you think. Share your opinions now!