Connect. Secure. Manage.
Meraki MS Switch Deployment
Deploy Meraki MS switches with validated uplinks, access-port settings and dashboard configuration, followed by connectivity and failover checks.
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 MS switch deployment should leave a site with working connections, usable records and a recovery plan—not simply a green device icon. MCI Network Services stages and commissions supported MS switches for office, branch and campus requirements. We work from an agreed port and uplink design, check the management path before cutover and validate the services attached to the switch. The scope can cover a new installation, an additional cabinet or replacement of an existing access layer.
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.
Prepare the site and the configuration together
Before installation, we confirm the switch model, port requirements, power budget, optics and rack arrangements. Access points, phones and other powered devices need sufficient capacity under the intended power-supply conditions. We also check cable identification and the physical route of uplinks. A configuration cannot compensate for an incompatible optic, a damaged patch lead or an installation position that prevents safe access to power and stack connections.
The configuration plan records each port’s intended role. Desk connections, infrastructure trunks and specialist devices should not inherit the same settings by accident. We identify VLANs, authentication dependencies and any local exceptions, along with the team that owns routed gateways and DHCP. Where the existing documentation is incomplete, discovery is part of the preparation rather than a problem deferred until the old switch has been disconnected.
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
Stage in the correct dashboard network
Equipment ownership, inventory claiming and network assignment are verified before the device is connected. Staging should use the intended configuration model and a safe management path. We review firmware eligibility and allow time for the required preparation, avoiding an unplanned upgrade during a short production cutover. The Meraki inventory and device claiming service can resolve assignment or ownership issues before installation begins.
If the network is bound to a template, we inspect the inherited settings and supported local overrides. A preconfigured port map is only useful if the template will not replace it unexpectedly. We record the template relationship and compare the staged device with the approved design. Any difference is resolved or explicitly accepted before the switch becomes part of the production path.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Commission uplinks before moving endpoints
We establish the intended management and uplink connectivity first. Checks include negotiated speed, VLAN carriage, link aggregation where used and the expected spanning-tree role. Redundant links need a supported design; plugging two cables into different switches is not proof of safe resilience. We confirm which failure cases the topology is intended to tolerate and how forwarding should change when one path disappears.
Where stacking is included, the physical and logical membership follows the model-specific procedure. We verify supported member combinations, software alignment and the relevant stack state. Our Meraki switch stack design work addresses this separately when the customer needs a topology review. Deployment should implement an agreed design rather than introduce a stack simply because the equipment has compatible-looking ports.
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 ↗Move users and devices in a controlled sequence
For a replacement, we map old ports to new ports and identify the services most sensitive to interruption. A camera, access point or phone may take time to recover after power is removed. A server or specialist appliance may depend on specific tagging or aggregated links. These dependencies influence the migration order and the checks performed before the next group of connections is moved.
We retain a practical recovery route during the change. That may involve preserving the original switch configuration and cabling records, maintaining alternative management access and defining when to stop. Rollback is not merely putting the old switch back in the rack: engineers need to know which connections changed and whether any upstream settings were modified as part of the cutover.
Test services and restrictions
Acceptance covers representative endpoints, address allocation, gateway reachability and the business applications in scope. We inspect errors, power events and unexpected port states rather than relying only on link lights. Where an access policy or isolated VLAN is part of the design, testing includes denied traffic as well as permitted traffic. A device reaching the internet does not prove its access to internal networks is correctly restricted.
Agreed failover tests demonstrate the effect of an uplink or member failure when it is safe to exercise them. We distinguish endpoint loss on a failed physical switch from continuity for devices connected elsewhere. Tests that cannot be performed are recorded as untested; high availability is not presented as proven solely because the topology contains more than one box.
Leave an operational handover
The completed installation includes device identities, port mappings, uplink details, software state and the results of acceptance checks. Alert ownership and the process for replacing a failed device are agreed with the support team. MCI can deliver this work across UK sites, including London, Kent and nearby counties, as part of wider Cisco and Meraki network services. Ongoing monitoring, engineering response and hardware replacement obligations are defined separately in the support scope.
Technical references
- Switch port configuration — Cisco / Cisco Meraki
- Meraki switch stacks — 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.