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

Connect. Secure. Manage.

Catalyst Switch Stacking

Configure Cisco switch stacks with compatible software, resilient cabling and recovery procedures that account for member failure and replacement.

Cisco Partner since 2009 Projects & ongoing support

Illustrative Cisco and Meraki network rack in a modern office
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.

Catalyst switch stacking can make a group of switches easier to manage. It also creates shared points of control that need care. We help you choose and set up a supported stack, then check how it behaves when a link or unit fails. Planned maintenance and recovery are part of that work.

01

Cisco-focused engineering

Design around the platform, traffic and failure behaviour you actually operate.

02

Change with evidence

Use pre-checks, acceptance criteria and a documented route back.

03

Operational handover

Keep the configuration, diagrams and responsibilities understandable after delivery.

When a stack makes sense

A stack allows compatible physical switches to operate as one logical system, subject to the capabilities and restrictions of the particular Catalyst family. This can reduce the number of individually managed devices and make it easier to provide uplinks or port capacity across a group of switches. It may also introduce dependencies between members that would not exist with independently managed equipment.

The starting point is the business need. We ask whether the aim is extra access ports, simpler management, resilient connections, easier replacement or a combination of these. The answer influences the appropriate topology. A stack that is convenient for a single wiring cabinet may not be appropriate across physically separated areas with different power and maintenance arrangements.

Illustrative enterprise Cisco network rack in a modern office environment
01Enterprise switching and routing, built to be operated.
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

Verify hardware and software compatibility

Not every Catalyst model can be stacked with every other model. Before specifying hardware, we confirm the supported platform family, stack technology, member limits, software needs and any restrictions affecting uplinks or licensing. We also check the available stacking modules and cables, their physical routing and whether the rack layout allows members to be replaced safely.

Mixed hardware generations deserve particular scrutiny. A setup that appears compatible at the feature level may have operational limitations during an upgrade or failover. We document the supported combination and identify any assumptions that need testing. Where a customer’s current switches cannot form a supported stack, the right answer may be independent switches with an appropriate upstream design rather than an improvised setup.

Illustrative Cisco and Meraki fibre network rack with structured cabling
02Fibre, switching and the physical path behind the service.

A useful starting point

Not sure where to start?

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

Talk to a specialist

Design the stack topology

The physical stacking topology influences both capacity and fault tolerance. We review the intended ring or other supported arrangement, cable lengths, member placement and the effect of a failed link. Where the platform supports it, a complete ring can provide an alternative path after a stack-link fault. But the remaining bandwidth and the specific recovery behaviour still require verification.

Power is a separate consideration. Two switches in one stack are not resilient if they depend on the same failed power feed. We assess power supplies, rack distribution, environmental conditions and, where applicable, supported power-sharing features. Resilience claims should describe the complete service path, including access links, uplinks, gateways and upstream security devices.

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

Understand control-plane and maintenance risks

A logical stack has shared operational characteristics. A software upgrade or control-plane incident can affect more than one physical member, depending on the platform and change procedure. We explain that risk to customers who assume multiple boxes automatically mean independent failure domains.

We also establish the process for adding or replacing a member. Member numbering, switch priority, software alignment and interface identification can affect setup persistence and port mappings. A replacement should follow a documented process, including backup of the settings and validation, rather than relying on a technician to improvise during an outage.

Illustrative Cisco and Meraki industrial network equipment in a plant environment
04Network engineering for operational and industrial environments.

Configure uplinks and access services

Stacking changes how ports are presented. But it does not remove the need for sound Layer 2 and Layer 3 design. We check VLANs, trunks, link aggregation, spanning-tree behaviour and the placement of routed gateways. If uplinks are spread across members, the intended failure path must be supported and tested.

For access stacks, we review Power over Ethernet budgets, authentication policies, voice VLANs and the effects of member loss on connected devices. A failed member will still disconnect endpoints attached to its physical ports. Stacking may improve uplink or management resilience without providing endpoint-level continuity. That distinction matters when discussing service availability with a business owner.

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

Test the behaviour before handover

Acceptance testing should reflect the design aims. Depending on the agreed scope, we check member discovery, stack health, software alignment, uplink status, expected failover and restoration behaviour. Tests involving a member restart or stack-link disconnection need an agreed maintenance window and a safe rollback plan.

We also check management access, monitoring alerts, interface descriptions and backups of the settings. The operations team should be able to identify which physical member hosts a reported port, understand how a replacement will affect the stack and find the correct escalation procedure. Clear records are especially important in larger estates with similar-looking cabinets.

Illustrative Cisco and Meraki network rack in a modern office
06The office network: switching, uplinks and structured cabling.

Ongoing management and support

A stack should be included in the network lifecycle plan. We track software support, hardware availability, capacity growth and changes to the settings that could affect multiple members. Monitoring needs to distinguish a single interface problem from a stack-wide event, and incident procedures should avoid making an unstable situation worse through unnecessary restarts.

MCI provides Cisco and Meraki network services throughout the UK, particularly London, Kent, Sussex, Essex and Berkshire. If you are planning a Catalyst refresh or reviewing a current stack, share the models, topology and the failures you need to withstand. We can assess the design, define acceptance tests and agree the support duties before any change is made.

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

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.