\nPrimary Network Tier<\/strong><\/td>\n| Campus Access Layer (wiring closet)<\/td>\n | Distribution and Core \/ Campus Collapsed Core<\/td>\n<\/tr>\n | \nInterconnect Media<\/strong><\/td>\n| Proprietary StackWise backplane cables<\/td>\n | Standard optical transceivers \/ DACs (10G\/25G\/40G\/100G)<\/td>\n<\/tr>\n | \nMaximum Physical Distance<\/strong><\/td>\n| Up to 3 meters (same or adjacent rack)<\/td>\n | Up to several kilometers (across buildings\/datacenters)<\/td>\n<\/tr>\n | \nMaximum Stack Members<\/strong><\/td>\n| Up to 8 switches (platform-dependent)<\/td>\n | Strictly 2 switches (paired node active\/standby)<\/td>\n<\/tr>\n | \nSupported Platforms<\/strong><\/td>\n| Catalyst 3650, 3850, 9200, 9300, 9300X<\/td>\n | Catalyst 3850-48XS, 9400, 9500, 9600<\/td>\n<\/tr>\n | \nDedicated Hardware Module<\/strong><\/td>\n| Requires dedicated stacking kit \/ backplane slots<\/td>\n | Uses native fixed or modular network uplink ports<\/td>\n<\/tr>\n | \nStack Interconnect Bandwidth<\/strong><\/td>\n| 80 Gbps (9200L) to 1 Tbps (9300X)<\/td>\n | Scalable based on number of SVL links aggregated<\/td>\n<\/tr>\n | \nSplit-Brain Detection<\/strong><\/td>\n| Hardware backplane signaling loop<\/td>\n | Dual-Active Detection (DAD) via fast-hello or ePAgP<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n<\/span>Hardware Compatibility Matrix and Stacking Cable Specifications<\/span><\/h2>\nImplementing StackWise requires selecting the correct platform tier, stacking module, and cable lengths. Stacking components cannot be mixed across incompatible hardware families (for example, a Catalyst 9200 cannot stack with a Catalyst 9300).<\/p>\n \n\n\n| Switch Series<\/th>\n | Stacking Technology<\/th>\n | Backplane Bandwidth<\/th>\n | Required Stacking Kit<\/th>\n | Compatible Cable Part Numbers<\/th>\n<\/tr>\n<\/thead>\n | \n\nCatalyst 9200L<\/strong><\/td>\n| StackWise-80<\/td>\n | 80 Gbps<\/td>\n | C9200L-STACK-KIT<\/code><\/td>\nSTACK-T4-50CM<\/code>, STACK-T4-1M<\/code>, STACK-T4-3M<\/code><\/td>\n<\/tr>\n\nCatalyst 9200 (Modular)<\/strong><\/td>\n| StackWise-160<\/td>\n | 160 Gbps<\/td>\n | C9200-STACK-KIT<\/code><\/td>\nSTACK-T4-50CM<\/code>, STACK-T4-1M<\/code>, STACK-T4-3M<\/code><\/td>\n<\/tr>\n\nCatalyst 9300 \/ 9300L<\/strong><\/td>\n| StackWise-480 \/ 320<\/td>\n | 480 Gbps \/ 320 Gbps<\/td>\n | Built-in (9300) \/ C9300L-STACK-KIT<\/code><\/td>\nSTACK-T1-50CM<\/code>, STACK-T1-1M<\/code>, STACK-T1-3M<\/code><\/td>\n<\/tr>\n\nCatalyst 9300X<\/strong><\/td>\n| StackWise-1T<\/td>\n | 1 Tbps<\/td>\n | Built-in<\/td>\n | STACK-T3-50CM<\/code>, STACK-T3-1M<\/code>, STACK-T3-3M<\/code><\/td>\n<\/tr>\n\nCatalyst 3850<\/strong><\/td>\n| StackWise-480<\/td>\n | 480 Gbps<\/td>\n | Built-in<\/td>\n | STACK-T1-50CM<\/code>, STACK-T1-1M<\/code>, STACK-T1-3M<\/code><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\nCable Selection Rule:<\/em> Standard installations within a single 42U equipment rack use 0.5-meter cables (50CM<\/code>) to daisy-chain adjacent switches and a 1-meter or 3-meter cable (1M<\/code>\/3M<\/code>) to close the loop from the bottom switch back to the top switch.<\/p>\n
\n<\/span>Step-by-Step Implementation Guide: Provisioning and Configuring StackWise<\/span><\/h2>\nDeploying a clean, deterministic StackWise configuration requires establishing physical counter-rotating ring topologies, defining priority values to ensure predictable master selection, and pre-provisioning hardware.<\/p>\n +-----------------------+\n | Switch 1 (Active) |\n | Priority: 15 |\n | Port 1 Port 2 |\n +-----|-----------^-----+\n | |\n | Stack | Return\n | Cable | Loop\n v |\n +-----|-----------|-----+\n | Port 1 Port 2 |\n | Switch 2 (Standby) |\n | Priority: 14 |\n | Port 1 Port 2 |\n +-----|-----------^-----+\n | |\n | Stack |\n | Cable |\n v |\n +-----|-----------|-----+\n | Port 1 Port 2 |\n | Switch 3 (Member) |\n | Priority: 1 |\n +-----------------------+\n<\/code><\/pre>\n<\/span>Step 1: Connect Physical Stacking Cables in a Redundant Ring<\/span><\/h3>\nConnect the switches in a closed ring loop using backplane ports:
\n1. Connect Port 1 of Switch 1 to Port 2 of Switch 2.
\n2. Connect Port 1 of Switch 2 to Port 2 of Switch 3.
\n3. Close the ring by connecting Port 1 of Switch 3 back to Port 2 of Switch 1.
\nThis counter-rotating ring topology ensures that if any single cable fails, the stack automatically fails over to a half-ring topology without dropping packet forwarding.<\/em><\/p>\n<\/span>Step 2: Set Switch Priorities for Deterministic Election<\/span><\/h3>\nPower on Switch 1 only. Once booted to the CLI, elevate its priority to ensure it always wins the active switch election (priority range is 1 to 15, with 15 being the highest):<\/p>\n Switch# configure terminal\nSwitch(config)# switch 1 priority 15\nSwitch(config)# exit\nSwitch# write memory\n<\/code><\/pre>\nPower on the second switch, join it to the stack, and assign it priority 14 to designate it as the deterministic Standby unit:<\/p>\n Switch# configure terminal\nSwitch(config)# switch 2 priority 14\nSwitch(config)# exit\nSwitch# write memory\n<\/code><\/pre>\nAny subsequent members can retain the default priority value of 1<\/code>.<\/p>\n<\/span>Step 3: Pre-provision Stack Members<\/span><\/h3>\nPre-provisioning registers the switch hardware model in the active configuration before physical hardware is powered on, preventing configuration wipes if a switch reboots:<\/p>\n Switch(config)# switch 2 provision c9300-48p\nSwitch(config)# switch 3 provision c9300-48p\nSwitch(config)# end\nSwitch# write memory\n<\/code><\/pre>\n<\/span>Step 4: Boot Sequence and Stack Formation<\/span><\/h3>\n\n- Power down all units.<\/li>\n
- Power on the intended Active switch (Switch 1) first and wait 2 to 3 minutes for it to initialize the control plane.<\/li>\n
- Power on the intended Standby switch (Switch 2).<\/li>\n
- Power on the remaining stack members simultaneously.<\/li>\n<\/ol>\n
<\/span>Step 5: Verify Stacking Health and Fabric Integrity<\/span><\/h3>\nRun the operational verification commands to ensure all members are recognized and running in a full-ring state:<\/p>\n Switch# show switch\nSwitch# show switch stack-ports summary\nSwitch# show switch stack-ring detail\n<\/code><\/pre>\nConfirm that the stack role reflects Active<\/code> for switch 1, Standby<\/code> for switch 2, and Member<\/code> for subsequent switches, with stack-ring speed running at full operational bandwidth.<\/p>\n
\n<\/span>High Availability Troubleshooting: Election, Failover, and Ring Integrity<\/span><\/h2>\nWhen a StackWise cluster experiences hardware faults or link degradation, systematic diagnostics identify whether the root issue is control plane election drift, SSO synchronization failure, or physical ring partitions.<\/p>\n <\/span>1. Stack Master Election Logic<\/span><\/h3>\nIf the designated Active switch reboots or drops from the stack, the remaining switches elect a new Active switch using this exact hierarchy:
\n1. Current Active Switch:<\/strong> An operational Active switch always retains its role over new joiners.
\n2. Highest Priority Value:<\/strong> The member configured with the highest switch priority (1\u201315<\/code>).
\n3. Non-Default Configuration:<\/strong> A switch with an existing interface-level configuration is preferred over an unconfigured switch.
\n4. Higher Feature Set \/ License Tier:<\/strong> Switches running higher software feature licenses take precedence.
\n5. Longest System Uptime:<\/strong> The switch with the longest continuous running time.
\n6. Lowest MAC Address:<\/strong> The switch possessing the lowest base MAC address.<\/p>\n<\/span>2. Validating Stateful Switchover (SSO) and Nonstop Forwarding (NSF)<\/span><\/h3>\nTo ensure the Standby unit is prepared for an instantaneous takeover without dropping active routing tables, verify redundancy state via the CLI:<\/p>\n Switch# show redundancy\n<\/code><\/pre>\nEnsure the output displays Operating Mode: SSO<\/code> and that the Standby switch status reports STANDBY HOT<\/code>. If the state is stuck in STANDBY COLD<\/code> or CONFIG DUMP<\/code>, check for Cisco IOS XE software version mismatches between members using:<\/p>\nSwitch# show version running-license\n<\/code><\/pre>\nAll members in a physical stack must run the identical software version and license tier. If an image mismatch occurs, use the software auto-upgrade<\/code> feature or manually install matching .bin<\/code> packages.<\/p>\n<\/span>3. Diagnosing Ring Partitions and Cable Breaks<\/span><\/h3>\nPhysical cable damage or incomplete loop topologies downgrade backplane performance. Inspect the ring status:<\/p>\n Switch# show switch stack-ring detail\n\nStack Ring Length: 3\nStack Ring Activity: Full\nStack Ring Speed: 480G\nStack Ring Re-entrancy: Enabled\n<\/code><\/pre>\n\n- Condition – Ring Activity: Full:<\/strong> All backplane cables are seated properly, and the ring functions with 100% throughput across both counter-rotating paths.<\/li>\n
- Condition – Ring Activity: Partial (Half-Ring):<\/strong> One cable or stack port is down. The stack remains functional, but data plane bandwidth is halved, and resiliency is compromised. Run
show switch stack-ports summary<\/code> to isolate the specific port in a Down<\/code> state and reseat or replace that cable.<\/li>\n<\/ul>\n<\/span>4. Resolving Stack Split-Brain Scenarios<\/span><\/h3>\nIf multiple stack cables are severed simultaneously, a stack can partition into two independent clusters (a “split-brain” state), with both claiming the same active IP address. Physical StackWise minimizes this because stack cables loop adjacent units; however, if a partition occurs:
\n1. Isolate the partitioned members by shutting down the corresponding uplink trunk ports to avoid network-wide MAC flap and IP conflict errors.
\n2. Restore the physical stacking connections.
\n3. Power-cycle the rogue stack member to force it to reintegrate into the original master\u2019s control plane.<\/p>\n
\n<\/span>Technical Specifications and Official Documentation References<\/span><\/h2>\nCisco maintains verified hardware metrics, architecture white papers, and configuration manuals for Catalyst switching lines. Below are the key engineering specifications governing Cisco IOS XE StackWise technology.<\/p>\n <\/span>Technical Architecture Specifications<\/span><\/h3>\n\n- Control Plane Model:<\/strong> Centralized Active-Standby 1:N architecture running Cisco IOS XE High Availability framework.<\/li>\n
- Hardware Forwarding (Data Plane):<\/strong> Distributed hardware forwarding across all ASIC-level Packet Forwarding Engines (PFEs) on individual stack members.<\/li>\n
- Stack Ring Bandwidth:<\/strong><\/li>\n
- StackWise-80: 80 Gbps bidirectional throughput (Catalyst 9200L).<\/li>\n
- StackWise-160: 160 Gbps bidirectional throughput (Catalyst 9200).<\/li>\n
- StackWise-480: 480 Gbps bidirectional throughput (Catalyst 9300 \/ 3850).<\/li>\n
- StackWise-1T: 1 Tbps bidirectional throughput (Catalyst 9300X).<\/li>\n
- Maximum Stacking Scale:<\/strong> Up to 8 switch members per stack; up to 448 ports managed as a single logical entity (excluding uplink breakout constraints).<\/li>\n
- Protocol Support:<\/strong> IEEE 802.3ad (LACP), Cross-Stack EtherChannel, Nonstop Forwarding with Stateful Switchover (NSF\/SSO), StackPower (Catalyst 9300 modular power pooling).<\/li>\n<\/ul>\n
<\/span>Key Cisco Documentation References<\/span><\/h3>\n\n- Cisco Catalyst 9300 Series Switches Architecture White Paper (Document ID: C11-739097):<\/strong> Covers the UADP ASIC implementation, ring buffer allocation, and packet recirculation logic within StackWise-480 and StackWise-1T topologies.<\/li>\n
- Cisco IOS XE Stacking Configuration Guide (Catalyst 9000 Series):<\/strong> Contains complete command references, pre-provisioning rules, switch-number reassignment procedures, and software upgrade operations.<\/li>\n
| | | | | | | | | | | | | | | | | | | | | |