After seven years of SonicWall TZ series appliances, the team finally greenlit a switch to Meraki MX. The CFO saw "cloud-managed" and got visions of reduced OpEx. I saw a chance to run some actual, reproducible throughput tests.
The trade-off isn't simple good/bad. It's a classic case of raw capability vs. operational smoothness.
**What Meraki Gets Right (The Win):**
* **Single Pane of Glass:** Managing 15 devices across 5 sites? The dashboard is undeniably slick. Pushing a unified policy is trivial.
* **VPN Client Experience:** AnyConnect for Meraki (now Cisco Secure Client) just works. User complaints about VPN dropped to zero.
* **Support & Diagnostics:** When you call, they *see* your config. No more "what firmware are you on?" The live packet capture tools are fantastic for blaming other parts of the stack 😉.
**What I Miss from SonicWall (The Cost):**
* **Deep Packet Inspection Throughput:** This is the big one. My SonicWall TZ670, on paper, had a lower "threat prevention" number. In my real-world iperf3 tests with DPI/IPS enabled, it handled a sustained 650 Mbps. The equivalently-priced Meraki MX85? It choked at ~420 Mbps. The marketing sheets never tell the whole story.
* **Granular Control:** Need a weird NAT policy or a specific application filter? SonicWall's object-oriented rules felt clunky but infinitely tweakable. Meraki's model is "simpler," which often means "you can't do that."
* **Cost Predictability:** SonicWall's recurring costs were for security services. Meraki's licensing is an **all-or-nothing subscription**. No license? Your shiny hardware becomes a brick. It's a different kind of lock-in.
My benchmark rig for posterity:
```bash
# Client -> iperf3 server through firewall with DPI/IPS enabled
iperf3 -c -t 300 -P 8 -b 0
# Measured average of 10 runs, 1-minute intervals.
```
Bottom line: If your priority is manageability for a distributed team and you have the bandwidth to spare, Meraki is a solid choice. If you need to squeeze every last megabit of inspected throughput from a mid-range box and love nitty-gritty control, SonicWall still has an edge. The network team sleeps better; I miss my throughput graphs.
benchmarks or bust
Junior analyst at a 200-person e-commerce shop here. I work with our IT team on reporting, so I've seen the dashboards and heard the arguments. We run a mix of SonicWall TZ series and Meraki MX in prod, mostly for site-to-site and remote user VPNs.
**Core comparison:**
**Cost structure:** SonicWall's upfront appliance cost is clear, but the yearly security subscription is a line item. For our Meraki MX68, the all-inclusive license is about $1,100/year per device. You lose a physical box if you stop paying.
**Dashboard vs. depth:** Meraki's dashboard is unbeatable for quick health checks and user VPN status. For actual traffic analysis, I still export SonicWall logs to a SQL database. The raw data from SonicWall is more granular for building custom security reports.
**VPN user troubleshooting:** Meraki wins this completely. I used to spend hours tracing user connection issues on SonicWall. With Meraki, I can see a user's connected client and their assigned IP in two clicks. Support tickets for VPN access dropped by maybe 80%.
**Hardware throughput reality:** Our SonicWall TZ570 with DPI enabled hits about 750 Mbps. The Meraki MX84 we tested, at a similar price point, leveled off at 500 Mbps. If your WAN link is above 500 Mbps, you need to size up, which changes the cost math fast.
My pick is Meraki for any company with distributed sites and a team that isn't full-time networking experts. If your primary need is max throughput for the dollar or you have dedicated security staff who live in the CLI, stick with SonicWall. To make a clean call, tell us your actual WAN speed and if you have someone on staff who can manage a complex firewall policy.
That throughput hit with DPI enabled is a real thing we've measured too. The Meraki's inline security services are pretty heavy, and their hardware specs aren't always as transparent.
We found the drop is way less pronounced if you're smart about applying policies. Don't just turn on the full IPS suite for all traffic. Use their traffic shaping and policy-based rules to only run deep inspection on risky traffic destined for your critical subnets.
It's a shift in thinking - SonicWall lets you crank everything to 11 and then just trusts the ASIC, but with Meraki you need to design for the limitation. The trade-off for that management simplicity.
Clean code is not an option, it's a sanity measure.
That exact throughput hit is what makes these discussions so tough. You're spot on, but I think the real trade-off is in who's doing the evaluation. The CFO sees simplified management and maybe even a lower total OpEx over three years, which is a real win for the business side.
But as the person who has to deliver the performance, that DPI number isn't just a benchmark, it's a hard ceiling you have to design around forever. It shifts the work from "managing the box" to "constantly micro-managing traffic policies," which is a different kind of OpEx that doesn't always show up on a spreadsheet.
Did your team do any capacity planning for that drop, or was it more of a "we'll adapt" discovery after the fact?
Raise the signal, lower the noise.
The point about log granularity is key. That raw SonicWall data is invaluable for security audits or custom compliance reporting. Meraki's API can pull similar data, but it's often pre-aggregated.
You lose the ability to ask truly custom questions of your traffic after the fact. That's a trade-off they never mention in the sales deck.