Connect. Secure. Manage.
Meraki Configuration Standards
Define practical Meraki configuration standards for naming, tagging, addressing and settings so site growth does not create an inconsistent dashboard.
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 configuration standards give engineers a dependable starting point without pretending every site is identical. They define how the business names networks, allocates addresses, protects administration and records exceptions. MCI Network Services develops standards that can be applied in the dashboard and understood by the people supporting the estate. The output is not a generic collection of recommended settings; it is a practical baseline tied to your equipment, applications, responsibilities and change process.
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.
Identify the decisions that need consistency
We examine the existing estate and the incidents or deployment difficulties that prompted the review. Repeated VLAN numbers with different meanings, inconsistent port descriptions and uncertain alert ownership are common reasons to establish a baseline. We separate matters that genuinely need uniform treatment from local details that should remain flexible. A branch circuit address, for example, is not an inconsistency simply because it differs from another site’s address.
The baseline is organised around operational questions. How is a network identified? Which team owns its gateway? What does an unused port look like? Where are exceptions recorded? Answering those questions makes the standard useful during a deployment or outage. It also avoids a document that describes ideal conditions but gives an engineer no way to handle the equipment already installed.
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 naming and addressing together
Names should distinguish sites, buildings, cabinets and device roles without relying on memory. We choose conventions that are short enough to use but meaningful enough to search. Tags need a defined purpose, particularly when they influence filtering or automation. Reusing a tag to mean both a location and a security role can make a future bulk change difficult to assess safely.
Addressing standards cover subnets, management networks and the ownership of gateway or DHCP services. We identify conflicts with remote networks and existing VPN connections before introducing a new pattern. Readdressing is not treated as a harmless housekeeping task: it can affect firewall policy, monitoring and applications. Any required migration belongs in a separate approved change rather than being silently included in a standards exercise.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Establish device-role baselines
A staff access port, access-point uplink and switch-to-switch trunk serve different purposes. We define the appropriate configuration pattern for each supported role, including how exceptions are approved. Protection settings should follow the intended neighbour and service; copying every control to every port can disable legitimate infrastructure. The standard records why a setting exists as well as its selected value.
Wireless and edge settings need the same discipline. SSID names, authentication methods, traffic handling and branch routing should correspond to real user groups and application paths. The document distinguishes what is required from what is merely available in the dashboard. New features are assessed for the actual platform and release instead of being enabled estate-wide because they appear in a menu.
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 ↗Choose how standards are enforced
The implementation may use independently managed networks, configuration templates or a controlled automation workflow. Each has different consequences for local overrides and change propagation. Our Meraki configuration templates service addresses inherited configuration in detail. The standards project identifies which parts of the baseline should be centrally controlled and which require a local decision with an auditable record.
Checks should be repeatable. We define how engineers compare a site with the baseline and how they distinguish an approved exception from accidental drift. A dashboard export, API-based comparison or manual review may be appropriate depending on scope. We do not describe a one-time checklist as continuous enforcement, and we record limitations where a setting cannot be reliably observed by the chosen method.
Make exceptions manageable
A standard becomes unhelpful when the only choices are blind compliance or an undocumented workaround. We create an exception process that records the business reason, affected systems, risk owner and review date. Examples might include a specialist device that cannot use the preferred authentication method or a temporary carrier arrangement during relocation. The exception should be narrow enough to remove when the underlying dependency changes.
Not every deviation warrants immediate remediation. We prioritise exposed administration, incorrect segmentation or unreliable recovery ahead of cosmetic differences. Changes to an operating site need their own validation and rollback arrangements. The standards register therefore separates approved design, current state and planned remediation rather than presenting all sites as compliant before work has been completed.
Handover and adoption
The final package includes the baseline, role-specific settings, naming and addressing rules, exception register and review procedure. We walk through representative tasks with the engineers who will use it. A standard that cannot guide a new-site build or fault replacement needs refinement before it is adopted. The dashboard change audit can provide a later check on how the baseline is being maintained.
MCI’s Cisco and Meraki network services support both internal IT teams and managed estates. We can establish a first standard, rationalise several inherited approaches or prepare a baseline for a larger rollout. Ownership and update responsibilities are agreed at handover so the document evolves with the network instead of becoming an obsolete attachment to a completed project.
Technical references
- Organisation change log — Cisco / Cisco Meraki
- Managing dashboard administrators and permissions — 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.