Connect. Secure. Manage.
Cisco Nexus Software Upgrades
Prepare NX-OS upgrades with platform compatibility, feature dependencies and maintenance sequencing checked against the production environment.
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.
Cisco Nexus software upgrades need a supported route to the new release and a plan for disruption. We check the hardware, features in use and linked devices before changing NX-OS. Tests and recovery steps are agreed in advance. Support for an in-service upgrade alone does not prove that your change will avoid an outage.
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 reason and the target state
An upgrade may address security exposure, a defect, hardware support or a required feature. We record that aim and compare the proposed release with the customer’s support needs. The newest available image is not automatically the appropriate target for every estate. Current vendor guidance, known issues and support milestones are reviewed for the actual platform and feature set.
The inventory includes switch models, supervisors or modules where relevant, current images, licences and important services. vPC, routing, overlays, storage-related functions and external integrations can affect the supported path. We identify dependencies across peers and management systems before scheduling the work. An image that boots successfully is not enough if it changes a feature the production network relies on.
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 the upgrade path and expected impact
Cisco’s platform-specific upgrade guidance and compatibility information are used to establish whether intermediate releases or extra preparation are required. Supported impact checks are run or reviewed where available. The plan records whether the intended method is disruptive, reduced-impact or eligible for a supported in-service procedure, including the prerequisites on which that assessment depends.
Even an eligible procedure needs application-level consideration. Routing changes, peer behaviour and exceptional conditions can affect traffic. We agree the maintenance window and customer expectations accordingly. If the supported path requires interruption, that is stated clearly rather than obscured behind optimistic terminology. The business should know what is being protected by topology and what still depends on app recovery.
A useful starting point
Not sure where to start?
Bring the requirement. We will help you define the engineering work.
Prepare backups, access and recovery material
Before the window, we capture settings, live state and relevant management records. Required images are received through authorised channels and checked for integrity where supported. Storage availability, boot settings and hardware health are reviewed so that an avoidable prerequisite failure does not consume the change window.
Recovery planning includes alternative management access and the practical limits of downgrade. A backup of the settings does not guarantee that a previous release can be restored without extra steps. We check the documented recovery path and identify any feature or change to the settings that complicates it. The person authorised to stop the upgrade and invoke recovery is named before work begins.
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 ↗Sequence changes around the topology
Paired switches and fabric nodes are upgraded in an order consistent with the supported design. We check the health and capacity of the remaining path before taking a component out of service. A network already operating with lost redundancy should not be treated as an ordinary maintenance candidate without assessing the extra risk.
The sequence includes hold points for checking peer state, routing, interfaces and representative traffic. We do not continue through a rollout simply because the first device restarted successfully. Unexpected conditions are investigated against the agreed stop criteria. Any temporary routing or operational adjustments are documented with a restoration step so that the final network does not retain maintenance-only exceptions.
Validate functions after the upgrade
Post-change checks compare the actual state with the pre-change baseline and the intended target. We review interface health, neighbours, vPC consistency where applicable, forwarding, management access and relevant telemetry. Server and app owners perform the agreed service tests. This catches problems that a software-version check alone would miss.
The observation period should reflect the risk and the functions affected. Rekeying, scheduled jobs or traffic patterns may expose issues later than the first few minutes. We record what was tested and any remaining monitoring need. A maintenance report distinguishes completion of the upgrade procedure from confirmation that every possible app scenario has been exercised.
Leave a clear lifecycle record
The handover records the installed release, method used, deviations, test results and outstanding actions. Configuration protection and monitoring integrations are checked after the change. Future maintenance decisions can then start from a reliable record instead of a mixture of outdated asset lists and individual engineer notes.
MCI can prepare an upgrade plan for your team, carry out an agreed change window or support a broader Nexus lifecycle programme. Our Cisco data-centre services are scoped to the actual estate and duties. Provide the models, current releases and reason for maintenance to begin. We will identify the supported options and the evidence required before making a production change.
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.