Cisco Firepower 4100 Series vs. Cisco Meraki MX

When we are asked by local partners which security equipment we use we always recommend our Cisco security products. The Firepower firewall is no exception and we can easily recommend this to others who need a fast, secure, and well built system that integrates well with all your existing hardware and software.

Incentivized

the Cisco Meraki MX 's work great for us we have over 40 locations and each has it's own Cisco Meraki MX that connects to our main Cisco Meraki MX in our datacenter. Each site then connects to Meraki switches and access points. Very easy to setup and keep running smoothly. Secure and easy for users to get connected to VPN.

Incentivized

• VPN Site to Site
• High Availability / Failover
• Ldap mapping to vpn connections

Incentivized

• It's very easy to deploy these devices because it's a cloud-based controlling controller that controls it. So able to, once the device has internet access, all you need to do basically is to look up the controller serial number and it'll basically find it. And once you add it to your network to automatically incorporate that device into your network and basically build the panels for the SD-WAN service.

Incentivized

• The failover process is clunky. When out Fortigate firewalls failed over, we lost 1 ping. When our Firepowers failover, whether it is on purpose or not, we experience a 2.5 minute complete outage.
• Cisco could stand to improve their support documentation. I have found it difficult to find good directions for configuring these, especially when it comes to NAT and IPSEC tunnels.

• Inbuilt wireless does not support tunnel SSID mode. This has meant not all SSID in our organisation can be deployed at a MX site.
• Whilst Inbuilt switch ports support dot1x, they do not report as well on our NAC server as on a MS switch or catalyst switch.

Incentivized

The simplicity and ease of use for the Meraki Dashboard make it an easy choice for our organization to renew our Meraki Enterprise Agreement. We will likely continue using the Meraki MC67-C, MX450, and other MX models in their catalog until we shift away from Meraki completely

Incentivized

In general, the Cisco Firepower 4100 Series works well, great performance, support a high volume of traffic, configuration, users, the device is powerful and once you have something configured you can be sure that it will rarely fail but for day to day troubleshooting or modifications needed can be a little complicated due to you have to deploy every change you make in the device and is not as fast as other devices, in general a deploy takes 5 minutes.

Incentivized

Some features simply aren't there, but the ones that are there are pretty easy to use. Sometimes it is easy to get lost when trying to find the specific device you want to work on, but that's mostly due to how rarely we have to go into the interface.

Incentivized

Meraki MX devices support high availability (HA) configurations, which ensures minimal downtime if one device goes offline. This feature has helped us maintain a stable and reliable network, even in cases of hardware failures. ince Meraki is cloud-managed, we've noticed that the cloud infrastructure is generally highly reliable, with minimal service interruptions or downtime. This makes it easier to manage the network remotely without significant availability concerns. Meraki automatically pushes firmware updates and patches, which helps maintain system stability without requiring manual intervention. These updates are rolled out in a manner that ensures minimal disruption to service.

Incentivized

The interface is pretty responsive. The lower end devices are easy to overwhelm if you have a lot of throughput. Be sure the model you get is rated for the amount of traffic you will have. Overbuild if possible, otherwise you won't be fully leveraging the connection from your ISP.

Incentivized

I haven't ever had a bad experience with Meraki support. On the few occasions where I wasn't understanding the UI or needed some clarification about what a setting actually would do, I contacted them and they were very quickly able to provide help. Returns are simple and fast, too. We had to return a defective device one time and they shipped the replacement before we had even un-racked the one that was faulty. Unlike many other vendors, they didn't ask use to a do long list of scripted diagnostics, they just took my word for it that the device was broken and sent out a replacement immediately

Incentivized

great when they offered it, really tested your knowledge with hands on and see what your peers from other orgs know. glad to see that we were ahead of the curve of what our peers knew

Incentivized

it was okay as it was moderated but still better than nothing and done via semi self paced webex meeting

Incentivized

Implementing Meraki MX devices in phases—starting with a pilot group or select branch offices—was invaluable. This allowed us to identify potential configuration issues, troubleshoot problems, and refine our setup before rolling it out company-wide. It also helped to get feedback from early users and adjust the deployment strategy accordingly. The SD-WAN capabilities in Meraki MX were essential for optimizing our WAN traffic and ensuring better application performance across various locations.

Incentivized

Cisco Firepower 4100 Series deployment is straightforward and easy to implement. It is also can support high availability and able to achieve redundancy. Besides, firmware upgrade is quite simple and the process does not take much effort as the upgrade will be automatically done by itself. Cisco Firepower 4100 Series is also very cost effective compared with other similar ranges of firewalls.

The Meraki Dashboard has been a lot more intuitive than CradlePoint NetCloud. We switched from CradlePoint to Cisco Meraki MX because we were already familiar with the interface which allowed us to be familiar with a single dashboard.

Incentivized

I think at an organization level it's definitely a 10. You can automate when you're going to upgrade. You can do it on a peer network basis. There might be issues around scalability if things get a bit too complicated, but if you keep it simple and stupid is my examples of a retail store with an fpos machine, you're going to be fine.

Incentivized

• Positive impact would be our increased security network wide.
• Another positive would be the increased processing power, saving us time and [from] needing more equipment.
• A negative impact would be the increased need for having to learn a new interface.

Incentivized

• I'm going to say positive impact. The biggest thing is especially coming from having a third party taking care of our network to us doing it ourselves. The ease of this with the overall high level visual that we can get as to how our day is starting and running reports to see how many outages have we had, what areas have they actually been in running these reports and being able to gather if it's a certain service provider that's causing an issue in a general area, maybe we need to switch service providers for ISP. So it's been great in that mannerism for us. Ease of manage, I mean, we have a limited number of staff, we have a lot of different offices across the country. And then this is relatively new for us because we did have a previous provider doing all of this for us.

Incentivized