Cisco & Meraki specialists. Across the UK.
+44 203 196 6566 · option 1sales@proxar.co.uk

Connect. Secure. Manage.

Cisco Nexus Switching

Design and maintain Cisco Nexus switching for data centre environments, addressing server connectivity, resilience, software lifecycle and fault diagnosis.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki data-centre network infrastructure
Your network. Properly considered.Design · Implementation · Support
1,000+

Devices supported
across the UK

20+

Client locations
supported

Nearly 8 Tbps

Traffic handled
at peak time

3 min

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 switching connects servers, storage and the systems used by data-centre apps. We design, install and support these networks around the workload and the team that will run them. The work covers normal traffic, faults and recovery. Your team should know how to make changes and restore service when needed.

01

Workload-led design

Start with application, compute and storage dependencies rather than the switch model.

02

Clear failure domains

Understand which links, devices and sites can fail together.

03

Operational clarity

Make fabrics, external routing and management responsibilities supportable.

Start with workloads and operating requirements

We establish which systems the network must connect, how they communicate and what interruption they can tolerate. Server access, east-west app traffic, storage access and external network access have different needs. The assessment includes growth, rack layout, cabling and any planned migration from current equipment. A design based only on port counts can overlook the dependencies that determine service availability.

The operating model matters as much as topology. We identify whether the customer needs independently managed NX-OS switches, a supported VXLAN EVPN fabric or another Cisco data-centre architecture. ACI is considered as a distinct design and management approach, not an interchangeable switch setup. The choice must suit the apps and the engineering team’s ability to maintain the resulting setup.

Illustrative Cisco and Meraki fibre network rack with structured cabling
01Fibre, switching and the physical path behind the service.
Cisco PartnerCisco Partner
Cisco MerakiCisco Meraki
ISO 9001Quality management
ISO 27001Information security
Cyber EssentialsCyber Essentials
Cyber Essentials PlusCyber Essentials Plus

MCI Network Services is operated by Proxar Ltd. Certifications apply to the certified legal entity and the scope of its certificates. View accreditation information

Match hardware and software to the design

Nexus families and software releases differ in their supported features, forwarding resources and upgrade behaviour. We check the exact models, interface needs, optics, licences and scale rather than treating the product name as a guarantee of every capability. Existing hardware can sometimes remain useful, but its role must be justified against the intended feature combination and support lifecycle.

Capacity planning includes uplinks, oversubscription and the surviving network after a failure. Aggregate link capacity is not the same as guaranteed throughput for every individual flow. We review the traffic mix and identify where shared resources could become a constraint. The design records the assumptions so that later server additions can be assessed without guessing how much headroom remains.

Illustrative enterprise Cisco network rack in a modern office environment
02Enterprise switching and routing, built to be operated.

A useful starting point

Not sure where to start?

Bring the requirement. We will help you define the engineering work.

Talk to a specialist

Build resilience around complete paths

A pair of switches can still share power, cabling or upstream dependencies. We examine physical placement, management access and the app path through gateways and security devices. Where vPC is appropriate, its peer communication and connected-device behaviour are designed clearly. It is not treated as a conventional stack or a replacement for every form of routing resilience.

We also identify endpoints with only one physical connection. Those systems may lose service when their attached switch fails even if the wider fabric remains healthy. The business should understand which failures are covered and which require host, app or storage-level resilience. Clear boundaries prevent a network high-availability claim from being interpreted as a promise that every workload will remain uninterrupted.

Illustrative Cisco and Meraki network operations centre with monitoring displays
03Visibility, monitoring and operational control.

Coordinate server and platform integration

Server teams need agreed uplink, VLAN, bonding, MTU and failover settings. We compare the physical design with virtual switches and host settings so that both sides make compatible assumptions. A mismatch can cause intermittent failures that appear only when one link is lost or a workload moves. Joint acceptance tests are more useful than separate teams declaring their own components healthy.

Segmentation and management access are reviewed alongside network access. We set out the required routed boundaries, permitted shared services and the systems authorised to administer the switches. Monitoring and setup protection are included from the start. Credentials and sensitive topology records remain in controlled systems rather than being distributed through unprotected installation notes.

Illustrative Cisco and Meraki equipment in organised data-centre racks
04Data-centre connectivity with clear physical and logical boundaries.

Implement and test in controlled stages

Deployment begins with an approved design, setup review and a practical change plan. We stage the equipment where appropriate, check software and physical connections, then introduce production traffic in an agreed order. Pre-change records and rollback conditions are available before the customer depends on the new path. Changes affecting current workloads are coordinated with their owners.

Acceptance covers the intended Layer 2 and Layer 3 behaviour, representative apps and authorised failure scenarios. We record what was actually exercised and any scenario that remains untested. The handover includes diagrams, port records, software information and service checks, allowing another engineer to understand the delivered network without reconstructing it from device output alone.

Illustrative Cisco and Meraki equipment in a modern data-centre aisle
05Resilient infrastructure from rack to service path.

Support the network through its lifecycle

Nexus operations need release planning, capacity review, setup control and evidence-led fault investigation. We can provide a defined project, specialist support alongside an internal team or a scoped ongoing management service. Response hours, change authority and vendor escalation duties are agreed in the contract rather than implied by the word support.

Our data centre network services cover UK setups and can include Nexus design, rollout, upgrades and troubleshooting. Share the current topology, workload needs and business aim to begin. MCI will identify the engineering work and dependencies needed to deliver a supportable Cisco network, while keeping server, storage and app duties clear.

Illustrative Cisco and Meraki data-centre network infrastructure
06Network infrastructure designed around the workloads it carries.

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 6566

Choose option 1

sales@proxar.co.uk

UK-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.

We’ll use these details to respond to your enquiry. Please leave out passwords and sensitive network information. Read our privacy notice.