You’re troubleshooting your network when suddenly everything stops. No traffic passing through your Meraki MX appliance. Just…nothing. Sound familiar?

Network administrators know that moment of panic when a firewall issue brings business to a standstill. Your phone starts ringing. Emails pile up. And somehow, it’s all on you to fix.

When your Meraki MX appliance isn’t passing traffic, every minute of downtime costs money. The good news? Most issues have straightforward solutions that don’t require calling Cisco support or completely rebuilding your configuration.

The trick is knowing exactly where to look first. Is it a simple configuration mistake? A hardware problem? Or something sneakier hiding in your security settings?

Understanding Meraki MX Traffic Issues

A. Common symptoms of traffic disruption

You know that sinking feeling when your network just stops working? With Meraki MX appliances, traffic disruptions typically show up in a few telltale ways:

Devices can connect to the network but can’t reach the internet
Intermittent connectivity where pages load partially or timeout
Some protocols work while others fail (like DNS works but HTTP doesn’t)
VPN connections drop frequently or can’t be established
Internal devices can’t communicate with each other across VLANs
Throughput suddenly drops to a crawl

The dashboard might show everything as “green” while users are screaming that nothing works. Classic disconnect.

B. How to verify if traffic is truly blocked

Don’t just take users’ word for it. Here’s how to confirm what’s really happening:

Check the Meraki dashboard traffic analysis tools
Run packet captures on the MX appliance (Security & SD-WAN ＞ Packet capture)
Test connectivity with simple ping tests from various network segments
Try traceroute to identify where traffic stops
Verify firewall logs for blocked connections
Check NAT settings to ensure translation is occurring properly

C. Distinguishing between connectivity vs. traffic passing problems

These are totally different beasts. Connectivity issues mean the device can’t establish a connection at all, while traffic passing problems mean the connection exists but data isn’t flowing properly.

Connectivity Issues	Traffic Passing Issues
No IP assignment	Can ping gateway but not internet
Unable to reach gateway	DNS resolution fails
Dashboard shows device offline	Dashboard shows device online
Link lights off or amber	Link lights green
Complete failure	Partial functionality

D. Impact of firmware versions on traffic handling

Firmware matters more than you think. Some versions have known bugs that can wreak havoc on traffic processing:

MX 15.x introduced Security Center but had VPN instability issues
MX 16.x improved IPS but some versions had NAT problems
MX 17.x enhanced SD-WAN capabilities but early releases had traffic processing bugs

Always check release notes before upgrading. Sometimes the fix for your traffic issues is literally a firmware update away. Other times, a buggy firmware might be the actual cause of your troubles.

Never underestimate the impact of automatic firmware updates – they can fix or break things overnight without warning.

Quick Troubleshooting Steps

A. Power cycling the appliance properly

When your Meraki MX isn’t passing traffic, sometimes the simplest fix works best. Power cycling isn’t just turning it off and on—there’s a right way to do it:

Disconnect all cables except power
Hold the reset button for 5 seconds (no longer, or you’ll factory reset it!)
Wait until all lights are completely off
Unplug power for at least 30 seconds
Reconnect power and wait for full boot (about 3-5 minutes)
Reconnect remaining cables

Most admins rush this process. Give your MX the full 30 seconds unplugged—it clears the memory completely and often resolves stubborn issues.

B. Checking physical connections and cable integrity

Bad cables cause weird problems that drive you crazy. Check these:

Look for bent pins or damaged connectors
Replace any cables with visible wear
Ensure cables click firmly into place
Try swapping cables with known working ones
Check for port LED activity

I once spent hours troubleshooting what ended up being a cable crimped under a desk drawer. Don’t skip this step!

C. Verifying WAN connectivity status

No WAN, no traffic. Your Meraki dashboard shows WAN status, but here’s what to check:

Dashboard WAN status (green = good)
Check IP addressing (static IPs configured correctly?)
Verify DNS settings
Look for upstream ISP issues
Check if the internet service is actually working

D. Examining dashboard alerts for clues

Your Meraki dashboard is practically screaming clues at you:

Security alerts (blocked connections?)
Configuration changes (who changed what when?)
Firmware update notifications
Hardware warnings
Network topology changes

These alerts tell a story. Connect the dots between when the problem started and what alerts appeared around that time.

E. Testing basic traffic with ping and traceroute

Time to get technical. From a client machine:

Ping your local gateway (if this fails, problem is local)
Ping 8.8.8.8 (if this works but DNS doesn’t, it’s a DNS issue)
Ping a domain name (confirms DNS resolution)
Run traceroute to see where traffic stops

The exact point where traffic dies tells you where to focus troubleshooting. No response from hop 1? Local issue. No response from hop 3? Probably your ISP.

Firewall and Security Configuration Fixes

A. Reviewing firewall rule conflicts

Firewall rules are the gatekeepers of your network, but when they start fighting each other, traffic stops dead in its tracks.

The most common issue? Contradicting rules. You’ve got one rule saying “let this traffic through” and another saying “block everything like this.” Your Meraki doesn’t know which to follow, so it defaults to the most restrictive option.

To fix this:

Log into your Meraki dashboard
Navigate to Security & SD-WAN ＞ Firewall
Look at your rules from top to bottom (remember, they’re processed in order)
Check for rules that might cancel each other out
Pay special attention to “deny all” rules that might be blocking legitimate traffic

Pro tip: If you’ve recently added new rules and things stopped working, that’s your first suspect. Either move it down in priority or adjust its scope.

B. Checking intrusion prevention settings

Your IPS might be a bit overzealous, flagging and blocking legitimate traffic as potential threats.

When your MX isn’t passing traffic, check if:

IPS is set too aggressively (blocking instead of alerting)
You’re using outdated signatures that trigger false positives
Specific business applications are getting caught in the crossfire

To adjust these settings:

Go to Security & SD-WAN ＞ Threat Protection
Review your IPS mode (Detection vs Prevention)
Look through recent alerts for patterns of blocked traffic
Consider creating exceptions for trusted business applications

C. Verifying content filtering exceptions

Content filtering is great until it blocks resources your team actually needs. The fix is usually simple:

Head to Security & SD-WAN ＞ Content Filtering
Check which categories are blocked
Review the “Blocked URLs” list for any critical business resources
Add necessary exceptions to the “Allowed URLs” list

Remember that content filtering works across all traffic types—not just web browsing. APIs, background services, and update servers can all get caught in these filters.

A common mistake is blocking CDNs (Content Delivery Networks) that many legitimate websites use. If users report partial website loading, this is often the culprit.

D. Troubleshooting site-to-site VPN tunnels

VPN tunnels failing is a classic cause of traffic issues between locations. When your tunnel goes down, so does inter-office communication.

Quick VPN tunnel fixes:

Check both ends of the connection in Dashboard ＞ Security & SD-WAN ＞ Site-to-site VPN
Verify that both MX appliances have active internet connections
Look for IP address changes (especially if using dynamic IPs)
Ensure your local networks don’t overlap between sites
Check for firewall rules blocking VPN protocols (UDP 500/4500)

If your tunnel shows “active” but still won’t pass traffic, the issue might be route-related. Double-check your “Local networks” settings on both ends to ensure they include all subnets that need to communicate.

Advanced Network Configuration Solutions

A. Resolving VLAN tagging issues

VLAN issues can drive you crazy when troubleshooting Meraki MX appliances. If your traffic isn’t flowing properly, check if VLAN tags are being stripped or added incorrectly.

Common VLAN tagging problems include:

Mismatched VLAN IDs between your Meraki and connected devices
Trunk ports configured as access ports (or vice versa)
Missing VLAN definitions on the MX interface

Fix these by verifying that your upstream switches have matching VLAN configurations. In the Meraki dashboard, go to Security & SD-WAN ＞ Configure ＞ Addressing & VLANs and confirm all VLANs are properly defined with the correct IDs.

Sometimes you need to enable “VLAN tagging” explicitly on specific ports. Check port configurations by navigating to Security & SD-WAN ＞ Configure ＞ Ports and make sure the proper tagging mode is selected.

B. Addressing NAT and port forwarding problems

NAT issues stop traffic dead in its tracks. If devices can’t communicate across your network boundary, check these:

Verify 1:1 NAT mappings match your public IP allocation
Confirm port forwarding rules don’t conflict with each other
Check that inbound firewall rules allow the traffic you’re forwarding

Port forwarding failures often come down to simple configuration errors. Navigate to Security & SD-WAN ＞ Configure ＞ Port forwarding and verify each rule has:

Correct public IP address
Proper protocol selection (TCP/UDP/Both)
Accurate internal IP destination
No overlapping port ranges

Don’t forget that NAT performance can tank when you hit connection limits. The MX’s hardware determines these limits, so make sure your model can handle your traffic volume.

C. Fixing routing table conflicts

Routing problems are subtle killers of network performance. When packets take wrong turns or disappear altogether, check your routing tables for:

Overlapping subnets causing ambiguous routing decisions
Static routes conflicting with dynamic routing protocols
Default routes pointing to the wrong next hop

To fix these, go to Security & SD-WAN ＞ Configure ＞ Routing and review all static routes. Make sure they don’t overlap with VPN subnets or locally connected networks.

If you’re using BGP or OSPF, verify that route advertisements match your intended design. Sometimes you need to adjust route preferences or implement route filtering to prevent unwanted routes from taking precedence.

The Meraki dashboard shows active routes under Monitor ＞ Event log (filter by routing events). This helps identify which routes are winning when conflicts occur.

D. Resolving DHCP configuration errors

DHCP problems leave clients stranded without valid IP configurations. When this happens, check:

DHCP scope conflicts between the MX and other DHCP servers
Exhausted IP pools without enough addresses for all clients
Helper address misconfiguration preventing DHCP requests from reaching servers

The fix often involves properly configuring DHCP settings in Security & SD-WAN ＞ Configure ＞ DHCP. Make sure your scope matches your VLAN subnet and doesn’t overlap with statically assigned addresses.

For relay setups, verify that helper addresses point to actual DHCP servers and that firewalls permit DHCP traffic (UDP 67/68).

Sometimes clients get stuck with old leases. Try shortening your DHCP lease time during troubleshooting to force faster renewals. This can quickly validate whether your DHCP changes are working correctly.

Dashboard-Based Troubleshooting

A. Using live tools for real-time diagnostics

When your Meraki MX isn’t passing traffic, the dashboard’s live tools can save your sanity. The ping and traceroute functions let you check connectivity without leaving the dashboard. Just navigate to Network-wide ＞ Configure ＞ Troubleshooting, enter the destination, and boom—instant results showing where traffic might be getting stuck.

The throughput test is another lifesaver. It measures actual bandwidth between your MX and Meraki’s cloud, helping you spot if performance issues are causing your traffic problems.

B. Analyzing packet capture data effectively

Packet captures are like X-rays for your network traffic. Start a capture by going to Security & SD-WAN ＞ Configure ＞ Packet capture. Focus on the interfaces where traffic should be flowing but isn’t.

Look for these telltale signs:

One-way traffic (packets going out but not coming back)
TCP retransmissions (potential packet loss)
DNS failures (name resolution issues)
Unexpected TCP resets

Don’t waste time capturing everything—use filters to zero in on specific IP addresses or protocols that matter.

C. Reviewing event logs for error patterns

The event log is your MX’s diary of everything that’s happened. Head to Network-wide ＞ Configure ＞ Event log and sort by “Appliance” to see MX-specific events.

Pay special attention to:

Interface flapping (rapidly going up/down)
VPN tunnel failures
Security alerts that might indicate blocked traffic
Configuration changes that coincide with when traffic stopped flowing

Pro tip: Export logs for longer timeframes to spot patterns that might not be obvious in the default view.

D. Leveraging support tools in the dashboard

The dashboard has built-in tools specifically for troubleshooting traffic issues. Use the Client tracking tool (Network-wide ＞ Clients) to see if specific devices are having problems.

The relatively new Connection stats tool shows active connections through your MX. If you see connections being established but no data transfer, you’ve found a clue.

For persistent issues, don’t forget the “Help” menu’s option to generate a support report. This creates a comprehensive snapshot Meraki support can use to help you faster.

E. Creating network snapshots for comparison

When troubleshooting, comparing current settings to when things worked is priceless. Before making changes, use the Configuration sync tool to download your current config.

Create configuration templates for your working setups so you can quickly spot differences when things break. The change log (Organization ＞ Configure ＞ Change log) shows all modifications, making it easy to correlate traffic issues with recent changes.

If you need to roll back, having these snapshots means you won’t be starting from scratch. It’s like having a time machine for your network configuration.

When to Contact Meraki Support

A. Preparing essential troubleshooting information

Sometimes DIY troubleshooting hits a wall. Before you reach out to Meraki support, gather these essentials to speed things up:

Device serial numbers (find these in Dashboard or physically on the appliance)
Recent configuration changes (even small ones matter!)
Screenshot of your Dashboard error messages
Network topology diagram (a simple sketch works too)
Timestamps of when the issue started
Any error logs you’ve exported from Dashboard

Pro tip: Create a simple document with all this info ready to go. Nothing wastes more time than a support agent asking for basic details you could’ve had ready.

B. Using the support case system effectively

The Meraki support system works best when you play by its rules:

Be specific with your case title – “MX68 not passing traffic after firmware update” beats “MX not working”
Set the right priority level – don’t mark everything “critical” or you’ll cry wolf
Include those troubleshooting steps you’ve already tried
Respond promptly to follow-ups (they expire after 72 hours!)

Most engineers skip straight to phone support, but the case system actually tracks your issue better and creates documentation you can reference later.

C. Escalation paths for critical outages

When your network is completely down and business is suffering:

Call the direct support line instead of email for true emergencies
Ask specifically for escalation if your case has been open ＞4 hours without progress
Have your case number ready if calling about an existing ticket
Request a Senior Network Engineer for complex MX routing issues

Remember that escalation doesn’t necessarily mean your support agent isn’t competent – sometimes issues require specialized knowledge or higher access levels to resolve.

When your Meraki MX appliance isn’t passing traffic, it can disrupt your entire network. Through proper troubleshooting, from checking basic connectivity issues to examining more complex firewall rules and security configurations, most problems can be resolved without escalating to support. The Meraki Dashboard provides powerful tools that help identify and fix connectivity issues efficiently.

Remember that persistent issues may require professional assistance. Don’t hesitate to contact Meraki Support when you’ve exhausted your troubleshooting options or face complex configuration challenges. With the right approach and knowledge of the common pitfalls, you can keep your Meraki MX appliance running smoothly and your network traffic flowing without interruption.

Blog

Meraki MX Appliance Not Passing Traffic? Here’s How to Fix It