Connect. Secure. Manage.
Meraki SD-WAN
Design Meraki SD-WAN around branch connectivity, application performance and Auto VPN, with supported routing and failover behaviour tested before handover.
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 SD-WAN brings supported site links, VPNs and traffic rules into Dashboard management. We plan the routes, security and provider roles around the apps and locations you use. Tests check the complete service, including faults. An appliance being online is useful evidence, but does not show that every required WAN path works.
The whole path
Understand how sites, providers, cloud networks and security controls fit together.
Resilience that can be tested
Separate a second circuit from genuine end-to-end service resilience.
Provider coordination
Keep addressing, routing and escalation ownership clear across organisations.
Establish the branch and application requirements
We find the offices, data centres and cloud networks that need network access, along with their important traffic flows. A small branch using cloud apps has different needs from a site hosting shared services or a financial-market connection. The design reflects those differences instead of assuming every location should send all traffic through the same central hub.
The circuit inventory includes bandwidth, addressing, provider equipment and failure dependencies. Two internet services can still share infrastructure, and a backup link may have insufficient capacity for normal operation. We set out the service expected during degraded conditions before selecting policies that depend on those links.
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
Verify the supported MX deployment model
Meraki MX capabilities depend on the chosen appliance, firmware, licence and operating mode. We check the required routing, VPN, security and performance features for the actual estate. A feature available on one model or in one mode should not be assumed to behave identically across every site.
The assessment also considers equipment ownership, dashboard administration and licensing responsibility. The customer needs to retain appropriate control over its organisation and understand which party handles renewals, changes and incident escalation. Cloud management simplifies administration only when those duties remain clear.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Design VPN topology and route availability
Auto VPN can connect supported Meraki peers. But the topology still requires decisions about hubs, spokes, advertised networks and permitted communication. We find the destinations each site needs and the dependencies of central services. A large shared VPN should not automatically make every branch network reachable from every other location.
We also review connections to non-Meraki setups and current routing domains. Their setup and failure behaviour may differ from Auto VPN and need separate validation. Our Meraki Auto VPN design work addresses the topology and routing detail where it forms the core of the proposed service.
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 ↗Align traffic policy with security and capacity
Preferred uplinks, performance policies and local internet treatment should follow app needs. We assess which flows benefit from a particular path and what should happen when that path is unavailable or degraded. The policy must be understandable enough for support engineers to explain why a connection took a particular route.
Security inspection and public addressing are part of the same decision. Moving traffic between exits may change the address seen by an external service or affect a stateful session. We test these consequences rather than promising that every app will experience transparent failover because the appliance supports multiple uplinks.
Introduce the service through a representative pilot
We prepare dashboard setup, site variables and provider prerequisites before moving production traffic. A pilot includes relevant local services, user groups and app paths, with a practical rollback plan. The rollout sequence should allow engineers to distinguish an internet handoff problem from a VPN or policy issue.
Application testing is performed from representative devices, not only from the appliance. DNS, authentication and internal routing can fail even when the MX reports healthy network access. The acceptance record includes permitted and restricted paths so the rollout checks security boundaries and ordinary reachability.
Test resilience and operating visibility
We agree which link or appliance failures can be exercised safely and observe both loss and restoration. The tests consider surviving-path capacity, app reconnection and any change in inspection or source address. A design may retain network access while delivering a reduced service, and that limitation should be clear to the business.
Monitoring needs to distinguish a lost backup link, a failed VPN path and a complete site outage. Alerts are routed to an accountable team with provider contacts and recovery instructions. A dashboard status alone does not prove that the customer's important workflow is functioning or that someone will respond when it is not.
Keep the estate consistent without hiding exceptions
Templates and shared standards can reduce repetitive administration, but site-specific needs need controlled treatment. We document approved exceptions and review their effect before central changes or firmware updates. An emergency local adjustment should not become a permanent undocumented dependency.
MCI delivers Cisco and Meraki network services across the UK, with particular experience supporting organisations with multiple locations. We can design a new Meraki SD-WAN estate, migrate a current WAN or provide a defined operational service. Share the sites, circuits and app priorities so the proposal can identify exactly what will be delivered, tested and supported.
Technical references
- Meraki SD-WAN best-practice design — Cisco / Cisco Meraki
- Meraki Auto VPN general 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.