Overview

StackWise combines multiple Catalyst chassis into a single logical switch so the stack can act as one platform for configuration, management, and redundancy. The physical cabling pattern matters because it creates the closed ring that supports stack health and member visibility.

This guide keeps the existing field-oriented steps and commands intact while organizing them into a clearer article flow.

Supported switches and requirements

Confirm the exact Catalyst family, hardware revision, and StackWise technology before building the stack. The stack members must support the same data-stack implementation and run compatible software for the intended deployment.

STACKWISE DATA

Data-stack cable

STACK P1STACK P2

Forms the logical switch and carries stack traffic. A full ring uses both data-stack ports on every member.

STACKPOWER

Power-stack cable

POWER 1POWER 2

Shares power between supported members. It uses separate ports and must not be confused with StackWise data cabling.

Before you begin

Capture a backup, record the existing switch state, and confirm that every intended member is compatible before changing cables or rebooting the stack.

  • Back up the running configuration and current startup configuration.
  • Collect hardware, software, boot, and inventory details from each member.
  • Verify the planned rack order before assigning member numbers.
Use the platform and release-specific syntax for any command that differs from the examples shown here.

Physical stack cabling

The closed-ring pattern is the core of a resilient StackWise build. Each cable crosses from the left stack port on one member to the right stack port on the next member, and the final cable closes the ring back to the first switch.

Interactive cabling wizard

Follow the crossing pattern one cable at a time

Each switch shows Stack Port 1 on the left and Stack Port 2 on the right. Every inter-switch cable crosses from Port 1 to Port 2.

Step 1 of 4 Connect Switch 1 Stack Port 1 to Switch 2 Stack Port 2.
Four-switch StackWise closed-ring diagram Each switch has Stack Port 1 on the left and Stack Port 2 on the right. Cables connect Switch 1 Port 1 to Switch 2 Port 2, Switch 2 Port 1 to Switch 3 Port 2, Switch 3 Port 1 to Switch 4 Port 2, and Switch 4 Port 1 back to Switch 1 Port 2. REAR VIEW · STACKWISE DATA ● P1 = left stack port ● P2 = right stack port SWITCH 1 Priority 15 P1 P2 FANS / PSU SWITCH 2 Priority 14 P1 P2 FANS / PSU SWITCH 3 Priority 13 P1 P2 FANS / PSU SWITCH 4 Priority 12 P1 P2 FANS / PSU CABLE 1 · SW1 P1 → SW2 P2 CABLE 2 · SW2 P1 → SW3 P2 CABLE 3 · SW3 P1 → SW4 P2 CABLE 4 · SW4 P1 → SW1 P2

What to do

What to verify

    Verification commands

    Confirm the exact physical port orientation and supported StackWise technology for the specific Catalyst family being installed.

    Stack member numbering

    Assign the final member numbers before the stack is powered on. The member number affects interface numbering, so the planned rack order should be stable before the stack comes up.

    Renumber a member

    show switch
switch 1 renumber 2
write memory
reload

    The new number takes effect after reload. Interface numbering changes with the member number.

    Stack priority

    Set the intended active and standby roles before the stack initializes so the election process follows the deployment plan.

    Set stack priority

    switch 1 priority 15
switch 2 priority 14
switch 3 priority 13
switch 4 priority 12
write memory
show switch

    Software and configuration checks

    Use the beacon LED and the stack-status commands to verify that the CLI member number matches the physical chassis and that the stack is healthy before you proceed.

    Identify the physical member

    hw-module beacon slot 1 on
hw-module beacon slot 1 off

    Use the beacon LED to match the CLI member number to the physical chassis. Verify the syntax for the platform and release.

    Verify stack health

    show switch
show switch detail
show switch neighbors
show switch stack-ports summary
show switch stack-ring speed
show redundancy

    Step-by-step stacking procedure

    Each task below keeps the previous deployment flow intact and adds a clearer sequence for the stack build.

    Deployment checklist

    Complete the deployment one verified task at a time

    Each task includes the instructions, commands, and expected result needed to complete it.

    0 of 10 complete

    1. Capture pre-checks and back up the configuration

    Instructions

    1. Connect to the existing switch or each standalone switch.
    2. Save the running configuration.
    3. Capture hardware, software, interface, stack, and boot information.
    4. Store the output with the deployment records before changing anything.
    terminal length 0
show clock
show running-config
show startup-config
show version
show inventory
show switch
show boot
show install summary
show interfaces status
show logging

    Expected result: You have a current configuration backup and a complete baseline of the switch state.

    2. Verify compatible hardware, IOS XE, and install mode

    Instructions

    1. Record the exact model, stack module, and hardware revision of every intended member.
    2. Confirm all members support the same StackWise technology.
    3. Compare IOS XE versions and installation mode.
    4. Upgrade or remove any incompatible member before building the stack.
    show version
show inventory
show switch
show install summary
show boot
dir flash:

    Expected result: Every member is supported in the same stack and runs the intended IOS XE version and installation mode.

    3. Assign unique member numbers

    Instructions

    1. Decide the final physical rack order.
    2. While each switch is standalone, assign its intended member number.
    3. Save the configuration and reload when required.
    4. Confirm the switch returns with the intended member number.
    show switch
switch 1 renumber 2
write memory
reload

    Expected result: Every intended member has a unique number with no duplicate member IDs.

    4. Configure the intended active and standby priorities

    Instructions

    1. Choose the preferred active member.
    2. Assign it the highest priority.
    3. Assign the preferred standby the next-highest priority.
    4. Use progressively lower priorities for the remaining members.
    5. Save and verify the priority column.
    switch 1 priority 15
switch 2 priority 14
switch 3 priority 13
switch 4 priority 12
write memory
show switch

    Expected result: The priority values match the planned active and standby election order.

    5. Confirm the physical rack order with beacon LEDs

    Instructions

    1. Turn on the beacon for one member at a time.
    2. Match the CLI member number to the physical chassis.
    3. Apply a rack label if needed.
    4. Turn the beacon off before moving to the next member.
    hw-module beacon slot 1 on
hw-module beacon slot 1 off

    Expected result: The physical top-to-bottom rack order matches the planned member numbering.

    6. Save boot settings and power down for cabling

    Instructions

    1. Save the running configuration on each switch.
    2. Confirm each switch will boot the intended image or package set.
    3. Shut down the switches according to the maintenance plan.
    4. Wait for power to be fully removed before installing or changing StackWise cables.
    write memory
show boot
show install summary
show version

    Expected result: Every member has saved configuration and correct boot settings before power is removed.

    7. Cable the complete StackWise ring

    Instructions

    1. Connect SW1 P1 to SW2 P2.
    2. Connect SW2 P1 to SW3 P2.
    3. Connect SW3 P1 to SW4 P2.
    4. Close the ring by connecting SW4 P1 to SW1 P2.
    5. Seat and secure every connector, and keep StackPower cables separate.
    show switch neighbors
show switch stack-ports summary
show switch stack-ports detail
show switch stack-ring speed

    Expected result: After power-on, every switch has two stack neighbors and both StackWise ports are operational.

    8. Power on and wait for every member to join

    Instructions

    1. Power on the intended active member first for a controlled new-stack build.
    2. Allow it to initialize, then power on the remaining members.
    3. Watch the console for version, SDM, and stack-port messages.
    4. Do not proceed until every intended member reaches Ready.
    show switch
show switch detail
show logging | include STACK|SWITCH|SDM|VERSION
show version

    Expected result: Every intended member appears with the correct number and reports Ready.

    9. Verify ring health, bandwidth, and redundancy

    Instructions

    1. Confirm all members are present and Ready.
    2. Verify every member has two neighbors.
    3. Verify both stack ports on every member are operational.
    4. Confirm the ring speed and active/standby state.
    5. Resolve any half-ring, port-down, or unexpected election condition.
    show switch
show switch detail
show switch neighbors
show switch stack-ports summary
show switch stack-ports detail
show switch stack-ring speed
show redundancy

    Expected result: The stack is a closed ring, both stack ports are operational, and active/standby roles match the deployment plan.

    10. Save the final configuration and capture post-checks

    Instructions

    1. Review final member status, stack ports, redundancy, boot settings, and interface status.
    2. Save the completed stack configuration.
    3. Capture post-check output.
    4. Compare the post-checks to the pre-check baseline and document any intentional differences.
    show clock
show switch
show switch detail
show switch stack-ports summary
show redundancy
show boot
show interfaces status
show running-config
write memory

    Expected result: The completed stack is healthy, saved, and fully documented.

    Verification commands

    Use the commands in this section as a compact reference while validating the stack after cabling and after any configuration change.

    Show stack membership

    show switch
show switch detail

    Show stack ports and neighbors

    show switch neighbors
show switch stack-ports summary
show switch stack-ports detail

    Show ring speed and redundancy

    show switch stack-ring speed
show redundancy

    Troubleshooting

    When the stack does not come up as expected, work from the physical connections to the stack status outputs and eliminate one variable at a time.

    • Confirm that the intended members have joined and show Ready.
    • Verify that each member has two neighbors and that both stack ports are operational.
    • Review half-ring, switch-election, and port-down conditions before changing more configuration.

    Common mistakes

    • Connecting StackWise data ports to StackPower ports.
    • Using the wrong crossing pattern or leaving the ring open.
    • Assigning duplicate member numbers or leaving the stack priorities inconsistent.
    • Proceeding before the physical rack order and member numbering are confirmed.

    Final validation checklist

    Confirm these items before closing the change window and handing the stack back to production.
    • The ring is closed and every member is present.
    • Every member reports Ready and the expected member number.
    • The configured priorities and stack ports match the deployment plan.
    • The final configuration has been saved and the post-check output has been reviewed.