Connect. Secure. Manage.
Meraki VPN Concentrator Deployment
Deploy Meraki VPN concentrators in supported environments, coordinating addressing, routing and upstream firewall requirements with existing teams.
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 VPN concentrator deployment introduces a supported MX or virtual MX role for connecting remote Meraki networks to centrally hosted services. The appliance's placement and operating mode determine how it fits the surrounding routing and security architecture. MCI Network Services prepares and deploys concentrators with clear upstream dependencies, route ownership and acceptance tests, rather than treating the VPN endpoint as an isolated device.
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 concentrator's role
We identify the remote sites, central applications and networks the concentrator must connect. A data-centre deployment can differ from a public-cloud endpoint or a branch acting as a hub. The scope states which functions the selected platform will perform and which remain with upstream routers, firewalls or cloud-native services.
This distinction prevents incorrect expectations about features. A concentrator arrangement should not be assumed to offer the same forwarding, NAT or security behaviour as a routed branch deployment. We verify the actual supported mode, software and licence combination before deciding how traffic will enter and leave the device.
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
Prepare the placement and upstream network
The concentrator needs suitable connectivity to both the Meraki environment and the application networks it serves. We review addressing, VLAN placement, upstream security policy and any translation in the path. A device that reaches dashboard may still lack the connectivity required for the intended VPN service.
The design also identifies power, virtualisation or cloud dependencies. Physical resilience and operational access matter even when tunnel configuration is automated. We record how the concentrator is reached for management and who can assist locally or through the hosting platform if its normal network path fails.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Design routes in both directions
Remote branches need routes to central services, and those services need a valid return path to the branch networks. We examine the surrounding routing domain and select a supported integration method. Static or dynamic arrangements are chosen according to the topology, scale and platform capabilities rather than personal preference.
Route advertisements are limited to the networks required for the service. We identify default-route behaviour, overlapping prefixes and any competing paths through other gateways. The resulting policy should not accidentally make the concentrator a transit route for unrelated networks or merge segments that were intended to remain separate.
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 ↗Coordinate security enforcement
The path from a branch through the concentrator may cross other firewalls or inspection points. We define where access policy is enforced and how traffic is identified at that boundary. If the concentrator does not perform a particular inspection function in its selected mode, the design assigns that responsibility elsewhere explicitly.
Management access is treated separately from application traffic. Administrators, monitoring tools and automation need only the permissions relevant to their role. We review dashboard access and connected integrations alongside network controls, because a central concentrator can affect many branches when its configuration changes.
Plan capacity and resilience
Capacity planning considers the expected sites, traffic mix and the supported performance of the chosen platform. A nominal appliance rating is not a guarantee for every combination of tunnels and features. We assess expected load and the capacity available during a degraded state where the architecture includes a secondary path.
Physical MX and virtual MX resilience arrangements are not assumed to be interchangeable. We verify the supported design for the hosting environment and identify how routes change when an endpoint is unavailable. A second instance requires its own operational and licensing assessment; it is not automatically equivalent to a hardware warm-spare pair.
Introduce the concentrator through controlled tests
We prepare the dashboard and upstream configuration, then bring a representative branch into service before wider migration. The tests verify tunnel state, advertised routes, application reachability and the return path. We also check restricted access where segmentation is part of the design.
Failure and restoration tests are agreed with the customer and the hosting team. We record application behaviour as well as platform status, especially where stateful security devices or public-address changes can affect recovery. Untested scenarios remain visible in the handover rather than being counted as demonstrated resilience.
Hand over the complete service path
The final records include concentrator role, addresses, route policy, security boundaries, dependencies and escalation contacts. Monitoring should distinguish endpoint failure from a branch circuit issue or an unavailable application behind the concentrator. This gives the support team a useful starting point when many remote users report the same symptom.
MCI can deploy a concentrator within a new Meraki Auto VPN design or replace an existing endpoint as a controlled project. Share the branch scope, central network diagram and hosting model. We can define the required upstream changes and tests before introducing a device that will become a shared dependency for the wider estate.
Technical references
- VPN concentrator deployment guide — Cisco / Cisco Meraki
- MX routing behaviour — 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.