Connect. Secure. Manage.
Catalyst SD-WAN Upgrade Services
Plan Catalyst SD-WAN software upgrades across control components and edge devices, with compatibility checks and a staged recovery approach.
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 upgrade services plan software changes across central services and WAN edges. We check compatibility, test suitable examples and agree recovery steps before rollout. The plan fits your network layout and maintenance windows. Choosing a new release alone is not enough to protect the sites and apps that rely on the WAN.
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 estate and the reason for change
We inventory management, control and orchestration components, edge models, software releases and setup workflows. The proposed change may address support lifecycle, a security issue, a defect or a required feature. We record that aim so the upgrade can be assessed against a concrete need rather than a general preference for a higher version number.
The review includes connected systems and integrations. Identity services, cloud connections, monitoring and automation may rely on behaviours that change with a release. Existing site exceptions are identified because they are often where a standard upgrade sequence encounters unexpected dependencies.
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
Select a supported target and sequence
The target release is checked against Cisco's current compatibility and upgrade guidance for the actual component combination. We identify permitted intermediate steps, prerequisites and any feature or platform restrictions. A release suitable for one device family is not automatically the appropriate target for every edge in the estate.
The rollout sequence accounts for central services and remote sites together. We explain where mixed-version operation is supported and for how long it is intended to exist during the project. Temporary compatibility is not treated as a permanent operating model without a separate supported justification.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Prepare recovery material and access
Before the change, we capture the relevant setup, platform state and supported backups. We check that the recovery material is accessible to the authorised engineers and that its restoration method is understood. A backup file alone does not prove that an interrupted upgrade can be recovered within the available maintenance window.
Remote access deserves particular attention. An edge upgrade can remove the same path used by the engineer performing it. We agree alternative access, local assistance and replacement arrangements where needed, distinguishing a software rollback from a device that no longer starts or reaches the network.
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 ↗Pilot on representative sites
The pilot should include relevant hardware families, transport types and app needs. Choosing only the smallest or least critical branch may leave important risks untested. We compare the pre-change baseline with routing, control relationships, policy and user workflows after the upgrade.
Known issues and release-specific behaviour are reviewed against the pilot results. A successful installation does not prove that all required functions behave correctly. Where a defect or limitation affects the customer, we agree whether to adjust the target, apply a supported workaround or postpone part of the rollout rather than silently accepting degraded service.
Coordinate the production change windows
The plan sets out the sites or components affected in each window, expected service interruption and the people needed for app validation. Provider and local-site contacts are included where their assistance may be required. Communications distinguish a planned interruption from an incident and explain how progress will be reported.
We set stop and rollback criteria before rollout. These include failures in control network access, routing, critical apps or recovery access. An upgrade should not continue across the estate merely because the initial steps completed if the pilot or first production wave reveals an unresolved problem.
Validate normal, degraded and restored operation
Post-change checks compare the intended setup with actual device and platform state. We check relevant routes, segments, app paths and monitoring. Where agreed and safe, we exercise failover and restoration to identify changes that appear only when the preferred transport is unavailable.
We also examine setup consistency and any migration of profiles or management settings. A platform upgrade can leave deprecated objects or unresolved tasks that require follow-up. The acceptance record distinguishes a fully checked site from one with an outstanding exception rather than counting every completed software job as equivalent.
Close the upgrade with lifecycle records
The final inventory records installed releases, dates, results and remaining actions. Obsolete images or temporary settings are reviewed through the customer's retention and recovery needs. The operations team receives any changed procedures, known limitations and monitoring expectations introduced by the new software.
MCI can manage a defined upgrade programme or support your engineers during critical stages of a current Catalyst SD-WAN deployment. Share the component inventory, current releases and the reason for upgrading. We can establish a supported path and realistic change plan without promising that every upgrade is non-disruptive or that a successful installation automatically resolves every operational issue.
Technical references
- Cisco Catalyst SD-WAN release and support documentation — 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.