Connect. Secure. Manage.
Meraki MX Traffic Shaping
Apply Meraki MX traffic-shaping policies to match business application priorities, with baseline measurements and checks for unintended restrictions.
Devices supported
across the UK
Client locations
supported
Traffic handled
at peak time
Average
response time
Average response is not a resolution time or a contractual guarantee. Support scope and response commitments are agreed for each engagement.
Meraki MX traffic shaping helps a branch use limited capacity according to business priorities. It cannot create bandwidth that a circuit does not have or repair every cause of poor application performance. MCI Network Services starts with measurements, identifies the actual bottleneck and applies supported shaping policies only where they address the problem. The objective is a predictable user experience during contention, with rules that engineers can understand and verify rather than an unexplained collection of limits.
Dashboard clarity
Structure organisations, networks and permissions around real operational ownership.
Consistent sites
Use repeatable standards without ignoring the differences between locations.
Practical operations
Keep cloud management connected to physical links, users and business services.
Measure the problem before choosing a rule
We establish which users, applications and times are affected. A slow file transfer, delayed voice call and unreliable cloud application may have different causes. We compare circuit utilisation, loss, latency and relevant client behaviour, then identify where congestion occurs. Poor Wi-Fi, a remote server bottleneck or an overloaded endpoint will not necessarily improve when an MX policy is changed.
The baseline should include busy periods and both traffic directions. Advertised circuit speed is not always the usable rate, particularly on asymmetric or variable connections. We record the capacity assumptions used in the design and the evidence behind them. A policy built around an unrealistic uplink value can make prioritisation less effective or restrict traffic unnecessarily.
Standards & partnerships
Confidence in the team behind your network.
Cisco Partner
Cisco Meraki
Cyber Essentials
Cyber Essentials PlusMCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information
Translate business priorities into traffic classes
The customer identifies services that need protection when capacity is constrained. Voice, interactive applications and bulk transfers may need different treatment, but the labels must correspond to traffic the platform can recognise reliably. We review supported classification, rule order and any existing group or client policies. Encrypted or shared-hosting traffic can make simple application assumptions less dependable, so classification is validated rather than accepted at face value.
Rules should be narrow enough to explain. A broad limit intended to restrain one backup job may also affect legitimate transfers from other systems. We document the match criteria, intended action and affected users. The business owner approves the trade-off, including which traffic may slow down when the site is busy and what outcome would justify adjusting the policy.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Review the complete traffic path
MX shaping is only one part of the path. A provider, wireless network or remote hub may impose its own limits or priorities. We check where markings are applied and whether downstream systems use them as intended. A priority label cannot guarantee treatment across an internet path that does not honour it. The report distinguishes local control from behaviour dependent on another network.
Routing and uplink selection also matter. A business application may move to a lower-capacity backup circuit or follow a different path after a failure. We assess how the policy behaves in that state and whether the branch needs a separate reduced-service expectation. Our Meraki branch network design work can address the wider connectivity choices when shaping alone cannot meet the requirement.
Different environments. The same care.
Built around the work
your network supports.
Finance, banking and the wider private sector. We start with the systems and people that depend on your connections.
Finance & banking
Market-data paths, routing and provider coordination on clients’ behalf.
Financial-market services ↗Offices & multi-site teams
Reliable access between people, workplaces and business applications.
Office network design ↗Data centres & cloud
Network boundaries, workload connections and operational ownership.
Data centre networks ↗Introduce changes in a controlled way
Before implementation, we record existing rules and the baseline measurements. A focused change is easier to evaluate than several simultaneous adjustments to routing, shaping and wireless settings. We agree the observation period, representative tests and rollback conditions, then apply the change to the intended scope. Template-based or centrally managed settings are reviewed for their effect on other sites.
The first checks confirm that the expected traffic matches the rule and unrelated traffic remains unaffected. We inspect available counters and application behaviour, including the effect of multiple concurrent users. A single speed test on an otherwise idle circuit is not a meaningful demonstration that prioritisation works during contention. Tests should recreate the business condition the policy was intended to improve.
Avoid turning a workaround into a permanent limit
Temporary bandwidth restrictions may be useful during an incident or circuit delay, but they need a review point. Once the underlying capacity problem is resolved, an old limit can become the reason users still experience poor performance. We record why each rule exists and what change would make it unnecessary. Unowned policies are investigated before being removed or copied into a new branch baseline.
The findings may show that a circuit upgrade, application scheduling change or different traffic path is more appropriate than additional shaping. We explain those alternatives and their dependencies rather than continue adding rules to compensate for a fundamentally undersized connection. The recommendation is tied to measured demand and the customer’s tolerance for degraded service.
Deliver evidence that operations can use
The handover includes the policy specification, before-and-after observations, known limitations and monitoring requirements. It identifies who can approve a priority change and how an engineer should investigate a complaint that appears after deployment. Where wireless behaviour is the main constraint, Meraki RF optimisation provides a separate route to assessment. MCI’s Cisco and Meraki network services keep these boundaries clear so that a performance problem is addressed at the layer actually responsible.
Technical references
- SD-WAN and traffic shaping — Cisco / Cisco Meraki
- General MX best practices — Cisco / Cisco Meraki
Talk to a specialist
What does your network need next?
Tell us what you are planning, changing or trying to improve. We will help define a practical next step and the engineering scope.
+44 203 196 6566Choose option 1
sales@proxar.co.ukUK-wide service.
Most of our engineers are based in Kent, with a focus on London, Sussex, Essex and Berkshire.
Existing customers should use their agreed support and escalation channels. This form is for service enquiries, not a monitored emergency ticket.
Tell us what you need.
A short outline is enough. Please do not include passwords or sensitive network details.
Thank you. Your enquiry has been submitted.
Please check your name, email and message, then try again.
Your form session expired. Please try again.
Please wait a minute before sending another enquiry.
We could not submit your enquiry. Please call or email us instead.