Connect. Secure. Manage.
Nexus Dashboard Upgrade Services
Prepare Nexus Dashboard upgrades with platform and fabric compatibility checks, backup protection and post-change service validation.
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.
Nexus Dashboard upgrade services keep the management platform aligned with supported releases and fabrics. We check the upgrade route, linked systems and backups first. After the change, we test the workflows your team uses. Switches may still pass traffic while management tasks fail, so both parts of the service need attention.
Workload-led design
Start with application, compute and storage dependencies rather than the switch model.
Clear failure domains
Understand which links, devices and sites can fail together.
Operational clarity
Make fabrics, external routing and management responsibilities supportable.
Establish the maintenance objective
The reason for an upgrade may be security, defect correction, support lifecycle or a required capability. We record that aim and compare suitable target releases against the customer’s estate. The latest image is not chosen automatically without reviewing supported paths, known issues and the connected fabric versions. A capability available in one release may require extra platform or device changes.
The inventory includes rollout form factor, cluster resources, managed fabrics, integrations and custom workflows. We check which teams depend on the platform for daily operations and what functions may be unavailable during maintenance. These details shape the window and acceptance plan. A successful platform restart is not the only criterion for completing the change.
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
Verify compatibility across the management stack
The upgrade path is checked against Cisco’s documentation for the exact source and target releases. Intermediate steps, infrastructure prerequisites and service compatibility are identified before the window. We distinguish a platform upgrade from a fabric software upgrade; one does not on its own authorise or complete the other.
Connected systems also need review. Identity providers, certificates, automation, monitoring and ticketing integrations can depend on interfaces or behaviours that change across releases. We find the owners who will check those functions. Unsupported or untested integrations are recorded as risks rather than assumed to survive because they worked with the previous version.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Check health and prepare recoverable records
We review platform health, available resources and relevant alerts before starting. Existing faults can complicate an upgrade and should be assessed rather than ignored. Required software is received through authorised channels and checked where supported. The rollout plan includes pre-change evidence so that post-upgrade differences can be interpreted accurately.
Backups and exports follow supported procedures for the rollout. We confirm what they contain, where they are stored and how recovery would work. A backup file or hypervisor snapshot is not accepted as a universal rollback strategy. Credentials and sensitive service data remain protected, and the customer knows which recovery actions require extra infrastructure or vendor involvement.
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 ↗Plan the sequence and operational cover
The change plan defines the supported upgrade sequence, hold points and conditions for stopping. It identifies who can authorise continuation, who handles adjacent systems and how engineers will manage the fabrics if the platform is temporarily unavailable. Alternative access is tested where it is part of the recovery plan.
The team also agrees how ongoing incidents and unrelated changes will be handled during maintenance. Concurrent setup activity can make state comparisons and recovery harder. We recommend a controlled window appropriate to the risk, while recognising the customer’s operational needs. Any emergency exception is recorded so that the final validation accounts for changes made outside the planned sequence.
Validate the functions the business relies on
After the upgrade, we check platform health, fabric network access, access roles and the relevant service data. Representative workflows are exercised: retrieving device state, investigating an event, generating a change preview or applying an approved limited task where included. These tests establish more than the fact that administrators can log in.
External integrations are checked with their owners, and any changed behaviour is documented. The observation period should reflect the functions involved, including scheduled jobs that may not run immediately. Untested conditions remain visible in the report. We do not claim complete service assurance from a short initial check that has not exercised the customer’s important workflows.
Update lifecycle and recovery documentation
The handover records the installed release, upgrade method, deviations and acceptance results. Backup and recovery procedures are updated for the new state, and the platform’s compatibility with the connected estate is documented. Outstanding actions have owners and review dates. This creates a reliable baseline for the next maintenance decision rather than leaving the team to infer it from change-ticket comments.
MCI can review an upgrade plan, support a customer-led window or deliver the maintenance as a scoped engagement. The work complements Nexus Dashboard deployment and software lifecycle planning. Provide the current release, rollout model and fabric inventory to begin. We will identify the supported options and the evidence from the live network required before the change is accepted.
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.