Image
Container Image
A read-only package containing an application and its required files used to create containers.
In everyday business: IT can deploy the same known application build repeatedly.
SWITCH REDUNDANCY
Switch Stacking and Redundancy Playbook
Design and commission a switch stack so it behaves as one managed system without hiding single points of failure.
Book 1 | Chapter 5
Chapter opening
Chapter 5 moves from the course overview into switch stacking and redundancy. The aim is not to memorise product menus or commands. The reader should understand what problem the technology solves, how it fits into the wider networking technical textbook, what normal operation looks like, and how to prove the result in the field.
The previous chapter introduced spanning tree and lacp configuration guide. This chapter continues the sequence by focusing on switch stacking and redundancy playbook, so the reader can connect the architecture to a more specific operational problem.
Learning objectives
- Explain the main purpose of Switch Stacking and Redundancy in plain language.
- Identify the components that must work together for the service to operate.
- Use evidence to separate a design problem from a configuration or physical fault.
- Describe the business impact of a failure and the evidence required for handover.
Why this matters in a real company
This subject matters because networking infrastructure supports normal business operations. Understanding the design makes purchasing, troubleshooting and recovery decisions easier to explain and verify.
Course: Networking Technical Textbook
PLAIN ENGLISH
Technical terms used in this chapter
You do not need to memorise the jargon first. Understand what each term does and why somebody running a company would care about it.
LACP
Link Aggregation Control Protocol
A protocol that combines compatible Ethernet links into one logical bundle.
In everyday business: It can add capacity and keep a connection alive if one member link fails.
NAT
Network Address Translation
A router or firewall function that changes IP addressing as traffic crosses a boundary.
In everyday business: Many private office devices can share one public Internet address.
PAT
Port Address Translation
A form of NAT that lets many internal connections share one public address by tracking transport ports.
In everyday business: Hundreds of users can browse the Internet through one public IPv4 address.
BUSINESS TRANSLATION
What this means outside the server room
This topic affects how reliably staff and systems can communicate. Good network design reduces downtime, makes faults easier to find and keeps departments or services separated where required.
Firewall
What it means: A firewall controls which network connections are allowed between users, systems and external networks.
In normal business language: It is a security checkpoint between parts of the company network. It should allow legitimate work while blocking unwanted access.
Why the decision matters: Firewall rules should describe real business flows such as 'staff may reach accounting on HTTPS', not unexplained broad permits.
NAT
What it means: NAT changes IP addresses as traffic crosses a network boundary.
In normal business language: It is similar to a company switchboard: many internal extensions can share one public number.
Why the decision matters: NAT helps with address use and publishing services, but it is not a substitute for firewall security.
Container
What it means: A container packages an application and its dependencies while sharing the host operating-system kernel.
In normal business language: Think of standardised shipping containers: the application is packaged the same way even when moved between compatible systems.
Why the decision matters: Containers improve deployment consistency, but persistent data, networking, security and backup still need deliberate design.
LACP
What it means: LACP combines several compatible Ethernet links into one logical bundle.
In normal business language: It is like using several lanes between two buildings instead of one, with traffic spread across the available lanes.
Why the decision matters: LACP can improve capacity and resilience, but the design must still avoid shared failure points.
5.1 What stacking gives the client
On supported platforms, stacking can provide one management/control plane, higher port density and resiliency. Cisco documents StackWise stacks as a unified system and supports full-ring topologies that preserve a second stack path if one stack link fails.
Before adding a member
- Check exact model stacking compatibility.
- Check software version compatibility.
- Check license level.
- Check install/bundle mode where relevant.
- Plan stack member numbers and priorities.
- Use the correct stack cable and respect its bend radius.
Cisco's current StackWise troubleshooting guidance warns against connecting a powered-on new member into a powered-on stack because stack merge behaviour can cause reloads. Follow the exact platform procedure.
Ring state matters
A half-ring can still operate, but it has lost the redundant stack path and may have lower available stack bandwidth. Verify the stack ring after any cabling change.
Typical verification
show switch
show switch stack-ring speed
show redundancy states
show version
Do not confuse stacking with uplink redundancy
A healthy stack still needs resilient uplinks, power and upstream design. Two stack members connected to the same single upstream switch and same power circuit still share those failure domains.
Replacement procedure
Document the failed member number, interface configuration and cabling before removal. Prepare the replacement software/license state and follow the vendor procedure so port numbering and stack role do not surprise the network.
Acceptance checklist
- All expected members visible.
- Full ring state where designed.
- Active and standby state healthy where supported.
- Member software/licensing consistent.
- Uplink/LACP paths tested across member failure.
- Stack and uplink cables labelled at both ends.
5.2 Power redundancy
Stack redundancy is incomplete when every member depends on one electrical circuit. Map each switch power supply to its PDU and upstream UPS/circuit. Where dual supplies are used, verify that the two feeds are genuinely independent if the design claims power-path resilience.
Uplink placement
Distribute uplinks across stack members where the platform/design supports it. This can keep upstream connectivity available if one member fails. Verify the logical port channel still has active members after the selected chassis is removed or powered down.
Replacement preparation
Keep a record of stack model compatibility, software image, member number, license and uplink/patch mapping. An emergency replacement is faster when the spare can be prepared before it reaches the rack.
5.3 Stack member numbering
Persistent member numbers make cabling and port references predictable. Before adding a replacement switch, confirm whether the platform preserves the removed member's number and configuration or whether manual renumbering is needed. Record this in the replacement runbook.
Software upgrade planning
A stack upgrade is a system change, not several unrelated switch upgrades. Confirm supported versions, boot mode, free flash, upgrade method, expected reload behaviour and rollback plan. Keep console access available because a failed upgrade can affect the whole logical switch.
Stack split risk
If the stack ring is incomplete and another stack link fails, members can become partitioned. The practical lesson is to treat a half-ring alarm as a resilience fault even while user traffic still works.
Port-channel design across members
Where the platform supports cross-stack EtherChannel, place member links on different stack switches so one member failure does not remove the entire uplink. Then test the actual member failure, not only a single cable pull.
Operational documentation
- Member number and serial number.
- Rack U position.
- Stack cable A and B destinations.
- Power feed/PDU.
- Uplink member ports.
- Software version and boot mode.
WORKED BUSINESS SCENARIO
Scenario: one switch carries staff, phones and cameras
A 48-port managed switch supports office PCs, VoIP phones, access points and CCTV cameras. The company wants separation and resilience without installing four separate physical networks.
What the chapter teaches us: VLANs, trunks, STP and link aggregation let one switching platform support several logical services, but only if the traffic path and redundancy are understood.
Think it through
- Which endpoints belong in which VLAN?
- Which links must carry multiple VLANs?
- What happens when a redundant Layer 2 path is added without loop control?
PRACTICAL WORK
Hands-on lab
Create a small isolated lab that reproduces the chapter's core architecture. Record the starting configuration, make one controlled change and prove the result with measurable evidence.
Troubleshooting exercise
Take one realistic failure, list the evidence you would collect before changing anything, then write the shortest fault-isolation path.
Chapter field checklist
- I can explain the subject without relying only on acronyms.
- I can draw or describe the main traffic, storage, power or service path.
- I know what normal operation should look like.
- I know which logs, counters or test results prove the result.
- I can explain the business impact if this component fails.
- I would document the final configuration and evidence at handover.
Chapter summary
Switch Stacking and Redundancy Playbook should now be understood as a business service with a technical implementation, not simply a collection of commands or product names. The important habit is to know the purpose, understand the dependencies, measure the result and document what was proven.
END OF CHAPTER
Review questions
- Explain the subject in plain language to a business owner.
- List the main dependencies that must be healthy before this service can work.
- Describe one realistic failure and the first three pieces of evidence you would collect.
- Explain what should be documented at handover.
- What is the difference between an access port and a trunk?
- Why is loop prevention required when redundant Layer 2 paths exist?
A good answer should explain the reason, not only repeat a product name or command.
Technical references
Use the current project specification and the exact product documentation for the installed equipment. These references support the technical principles used in this guide.