How to Manage Bandwidth with Meraki Traffic Shaping

Bandwidth is a finite resource in any business network. No matter how fast your internet connection, there is always a limit to how much data can flow at any given moment. When every employee in your office is simultaneously making video calls, uploading files to SharePoint, streaming training videos, and accessing cloud applications, that finite bandwidth must be shared — and without intelligent management, the most demanding applications can monopolise the connection at the expense of everything else.

This is where traffic shaping comes in. Traffic shaping — sometimes called bandwidth management or Quality of Service (QoS) — is the process of prioritising certain types of network traffic over others, ensuring that business-critical applications always have the bandwidth they need, even during periods of heavy network usage. Cisco Meraki, one of the most widely deployed cloud-managed networking platforms in the UK, provides powerful and remarkably accessible traffic shaping capabilities that can transform the performance experience on a congested network.

This guide explains how Meraki traffic shaping works, how to configure it effectively for a UK business environment, and how to use it to eliminate the frustrating performance issues that plague so many office networks.

Understanding the Bandwidth Challenge

The nature of office network traffic has changed dramatically. A decade ago, the primary bandwidth consumers were email, web browsing, and occasional file downloads. Today, the average UK office sees constant streams of video conferencing (Microsoft Teams, Zoom), cloud application traffic (Salesforce, Xero, HubSpot), file synchronisation (OneDrive, SharePoint, Dropbox), VoIP telephony, and an increasing amount of software-as-a-service traffic that was previously handled by local servers.

Not all of this traffic is equal. A Teams video call requires consistent, low-latency bandwidth — any interruption manifests immediately as frozen video, robotic audio, or dropped calls. An email download, by contrast, can tolerate slight delays without any noticeable impact on the user experience. Yet without traffic shaping, the network treats all traffic identically, allocating bandwidth on a first-come, first-served basis. This means a large file upload can easily degrade the quality of every video call in the building.

How Meraki Traffic Shaping Works

Meraki traffic shaping operates at multiple levels, providing granular control over how bandwidth is allocated across your network. The system uses deep packet inspection and Layer 7 application identification to recognise traffic types and apply policies accordingly.

Layer 7 Application Identification

Meraki's Layer 7 firewall engine inspects network traffic and identifies the application generating it — not just by port number (which is easily spoofed) but by analysing the actual traffic patterns and signatures. This means Meraki can distinguish between a Microsoft Teams video call, a YouTube stream, a Dropbox sync, and a Windows Update download, even though they might all use the same HTTPS port. This application-level visibility is the foundation of effective traffic shaping.

Traffic Shaping Rules

In the Meraki dashboard, traffic shaping rules are configured under Security & SD-WAN for MX appliances, or under Wireless for MR access points. Rules allow you to set bandwidth limits, prioritisation levels, and throttling policies for specific applications, application categories, or custom traffic definitions. Each rule specifies a per-client bandwidth limit and an overall bandwidth limit, giving you control at both the individual and aggregate level.

Global Bandwidth Limits

Beyond per-application rules, Meraki allows you to set global bandwidth limits per client or per SSID (for wireless networks). This prevents any single device from consuming an unreasonable share of the available bandwidth, regardless of what application it is running. For guest Wi-Fi networks, this is particularly important — you want guests to have internet access, but not at the expense of your business traffic.

Configuring Traffic Shaping: A Practical Guide

Setting up traffic shaping on Meraki involves several steps, each building on the previous one. The following approach ensures a structured, effective configuration that addresses the most common bandwidth challenges in UK business environments.

Step 1: Baseline Your Traffic

Before creating rules, use Meraki's built-in traffic analytics to understand your current bandwidth usage patterns. The Meraki dashboard provides detailed visibility into which applications consume the most bandwidth, which clients are the heaviest users, and when peak usage occurs. Run this analysis for at least a week to capture typical usage patterns, including any weekly variations.

Step 2: Define Your Priorities

Work with your business stakeholders to define which applications are business-critical, which are important but tolerant of slight delays, and which are non-essential. This is a business decision, not a technical one — the finance director may insist that Xero accounting traffic is always prioritised, while the marketing team may argue that their video content uploads are equally important. Reach consensus before configuring rules.

Step 3: Create Traffic Shaping Rules

In the Meraki dashboard, navigate to the traffic shaping section and create rules for each priority tier. For high-priority applications, set the bandwidth limit to "Ignore" (no limit) and the priority to "High." For low-priority traffic, set specific per-client and overall bandwidth limits. For non-essential traffic such as personal streaming, consider setting aggressive limits during business hours with more relaxed policies outside working hours.

SD-WAN and Traffic Shaping

For organisations with multiple sites — a head office in London with branches in Manchester, Leeds, and Edinburgh, for example — Meraki's SD-WAN capabilities extend traffic shaping beyond a single location. SD-WAN allows you to define application-level routing policies that direct traffic across the most appropriate WAN link, combining traffic shaping with intelligent path selection.

With SD-WAN, you can route Microsoft 365 traffic directly to the internet via a local breakout rather than backhauling it through the head office, reducing latency and improving user experience. VoIP traffic can be routed over the most reliable link with the lowest jitter, while bulk data transfers use a secondary link. This combination of traffic shaping and path selection delivers a significantly better experience than traffic shaping alone, particularly for organisations with bandwidth-constrained branch links.

Monitoring and Ongoing Optimisation

Traffic shaping is not a set-and-forget configuration. Network usage patterns change as new applications are adopted, team sizes fluctuate, and business processes evolve. Regular review of your traffic shaping policies — at least quarterly — ensures they remain aligned with your actual traffic patterns and business priorities.

Meraki's dashboard provides real-time visibility into how traffic shaping rules are being applied, which applications are being throttled, and whether any high-priority traffic is being impacted by bandwidth constraints. Use this data to fine-tune your rules over time, adjusting limits as your internet connection is upgraded or as application usage patterns shift.