Connect. Secure. Manage.
Meraki Campus Fabric Design
Plan a supported Meraki-managed campus fabric with a documented underlay, overlay and fault-domain design that matches the organisation's needs.
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 campus fabric design turns your site’s needs into a plan engineers can build. We define physical paths, fabric roles, logical services and links to the wider network. The design states how faults should be handled and which functions sit outside the fabric. Tests can then check those choices against the intended service.
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.
Choose an architecture that fits the campus
We start with buildings, access areas, app locations and the operational boundaries that matter to the customer. The design should accommodate real cable routes, retained equipment and maintenance practices. We compare suitable role placement and topology options against those constraints rather than forcing every campus into the same diagram regardless of its size or needs.
Platform choice follows the required roles and current support matrix. Some devices may terminate overlay services, while others provide ordinary access or transport. We identify those distinctions in the design and explain where combinations of roles are supported. The customer should be able to understand which components carry a shared responsibility and what services would be affected if one of them failed.
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
Define the underlay as an independent foundation
The underlay provides reachability between the relevant fabric nodes. We specify physical links, addressing, routing and the capacity required under normal and degraded conditions. MTU and encapsulation needs are checked across the full transport path. A link that carries ordinary small packets successfully may still conceal a problem for encapsulated traffic if the path has inconsistent limits.
We also document resource reservations and the boundary between automated provisioning and retained setup. This prevents two management processes from attempting to use the same interfaces or address space. The design includes the evidence needed to confirm that the transport works before overlay services are introduced, making later troubleshooting more systematic and reducing the risk of misdiagnosing a basic reachability fault as an endpoint-policy problem.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Map services into the logical network
Logical segmentation should reflect access needs, not simply reproduce every historical VLAN without review. We identify endpoint groups, app dependencies and shared services, then map them to supported routing and policy constructs. The design explains how addresses are assigned, where gateways sit and how endpoints reach services outside their own segment.
A distinction is maintained between separating routing contexts and enforcing security decisions. Where traffic needs inspection or more detailed access control, the relevant enforcement point is included. Our fabric segmentation service develops the permitted-flow model and testing approach. The design avoids claims that a fabric automatically provides complete zero trust or resolves every compliance need by being deployed.
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 ↗Design the external handoffs explicitly
The fabric must connect to WAN, internet, data-centre and other retained networks through agreed boundaries. We specify the handoff method, route advertisements, permitted prefixes and the owner of each side. Default routes and shared-service reachability receive particular attention because an apparently minor error can affect many endpoint segments at once.
Resilience at the boundary is considered alongside internal fabric resilience. Two internal paths do not protect against a single external firewall or a common upstream circuit. We trace both directions of important app traffic and consider stateful services. The design states what happens when a handoff or border component fails and which app sessions may need to recover independently of routing convergence.
Make maintenance and recovery part of the specification
A production design needs a workable upgrade and change model. We find the access required, the order of operations and the checks that establish a safe starting state. Where redundancy supports maintenance, the procedure must still follow the platform’s supported behaviour and the customer’s app constraints. We avoid describing an upgrade as non-disruptive without evidence for the exact arrangement.
Recovery considerations include records of the settings, management network access and the effect of a partially completed rollout. The design should explain how engineers determine the current state and what information they need before taking corrective action. This is particularly important when dashboard workflows automate several underlying changes that are not obvious from a single interface-level view.
Define acceptance before implementation begins
The acceptance plan connects needs to observable results. It includes representative endpoint access, approved isolation checks, external app paths and chosen failure scenarios. Each test identifies its scope, expected result and responsible participants. This avoids a handover where one team considers the project complete because devices are online while another still cannot use a required service.
MCI can deliver the design as an independent package or take it into fabric migration. The final documentation includes topology, addressing, role allocation, policy intent, handoffs and operational assumptions. It gives the customer a basis for rollout and future changes while clearly separating confirmed capabilities from conditions that still require a pilot, vendor confirmation or approval from another service owner.
Technical references
- Cloud fabric architecture — Cisco / Cisco Meraki
- Cloud-managed EVPN fabric technical guide — 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.