Connect. Secure. Manage.
Catalyst SD-WAN Configuration Profiles
Develop reusable Catalyst SD-WAN configurations with clear site variables, exception handling and change controls for repeatable deployments.
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.
Catalyst SD-WAN configuration profiles organise shared settings and site-specific values for supported WAN edges. We help build and maintain groups and profiles that engineers can review safely. The work checks release support, ownership of variables and the reach of each change. A shared profile needs clear limits because one edit may affect many sites.
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 configuration model in use
An estate may contain current templates, newer configuration-group workflows or a transition between supported approaches. We find the software versions, device families and management capabilities before recommending a model. Similar terminology in different releases should not be treated as proof that setup can be moved unchanged between them.
The assessment also examines how the current setup was created. Manual changes, inherited templates and site exceptions can produce differences that are not obvious in a central summary. We compare the intended model with device state so the project begins from the live estate rather than an idealised description of it.
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
Separate reusable policy from site variables
Common settings belong in a structure that can be maintained once and applied deliberately. Site-specific addresses, interfaces, circuit details and local service needs need a controlled source of truth. We set out the variables, permitted values and the person responsible for confirming them before rollout.
The model should make errors difficult to overlook. A blank or copied value can cause a site to lose management access or advertise the wrong network. We use reviewable naming and validation rules appropriate to the supported platform, and avoid a design where engineers must remember which undocumented fields are safe to reuse.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Build profiles around meaningful functions
Profiles should reflect the actual transport, service and system duties of the edge. We examine how routing, interfaces, security and management settings interact, rather than treating each setup section as independent. A change to a service-side interface can affect route advertisement and policy even when the transport profile remains untouched.
The organisation also needs an approach to exceptions. A genuinely different branch need may justify a separate profile or controlled variation, but creating a unique copy for every site can remove the benefits of standardisation. We document why exceptions exist and how they will be reviewed when the platform or business need changes.
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 ↗Review changes as estate-wide actions
A central change to the settings can affect many devices. We establish who can edit, approve and deploy it, and how the intended target set is checked. Administrative permissions should reflect that impact; ordinary monitoring access should not automatically include authority to alter a shared production profile.
Before rollout, the proposed difference is reviewed against the affected site roles and dependencies. We identify whether a change alters management network access, routing or app paths and whether local support is needed. A small edit in the interface does not necessarily mean a small operational change across the estate.
Pilot with representative devices
A test group should include the hardware and site patterns relevant to the proposed change. We check the generated setup, successful app and actual device state, then test the services the profile is intended to support. A management task reporting success is not enough if a local app or route behaves differently afterwards.
We also test how failures are reported. Invalid variables, unsupported features and interrupted network access should produce a clear operational response. The team needs to know whether the device retained its previous state, received part of the intended setup or requires manual recovery through another access method.
Control drift and operational exceptions
Devices can diverge from the intended central model through emergency changes or unsupported local edits. We review the platform's supported consistency checks and agree how discrepancies are investigated. Not every difference is malicious or accidental, but every significant exception should have an explanation and owner.
The process should avoid blindly overwriting a local change that is currently keeping a service working. We establish the reason, assess the correct long-term setup and return the site to an approved state through change control. This preserves accountability without turning consistency enforcement into an avoidable outage mechanism.
Maintain the configuration library over time
Profiles need lifecycle management as software, hardware and site needs change. We recommend clear version records, retirement of obsolete variants and a documented recovery approach. Backups should preserve both the setup material and enough context to understand which sites and variables belonged to it.
MCI can build a setup library for a new rollout or rationalise a current estate with excessive variation. Our Catalyst SD-WAN site onboarding service applies those standards to individual branches. Share the current model, device families and recurring operational problems so we can prepare a supported setup approach that remains understandable when the network grows.
Technical references
- Catalyst SD-WAN configuration groups — Cisco / Cisco Meraki
- Catalyst SD-WAN configuration consistency — 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.