Catalyst StackWise: Two-C9200 Source Stacking Example
The stored article is titled “9300,” but its scenario explicitly uses two C9200 switches. This translation retains that actual scope. Do not infer that C9200 and C9300 can be mixed in one stack, or that every model in either family has the same stack compatibility.
1. Check compatibility
Confirm the supported hardware combination, identical compatible software release and matching license level. Cisco also requires matching operational mode when adding members. Use the installation guide for the exact SKU, stack modules and cables.
2. Set numbers and priorities, if required
Stack priority ranges from 1 to 15; a higher value favors active election. A switch number determines interface numbering and is independent of priority. New standalone examples begin as switch 1. Renumbering takes effect after reload; plan disruption and verify current numbering before issuing commands.
First standalone switch, source example:
Switch#switch 1 renumber 1
Switch#switch 1 priority 15
WARNING: Changing the switch priority may result in a configuration change for that switch. Do you want to continue?[y/n]? [yes]: yes
1
2
3Second standalone switch, before its renumbering reload:
Switch#switch 1 renumber 2
Switch#switch 1 priority 10
WARNING: Changing the switch priority may result in a configuration change for that switch. Do you want to continue?[y/n]? [yes]:
1
2
3The source typo reunumber is corrected to renumber. The switch 1 priority 10 line refers to the current standalone ID before reload. Once that unit is actually switch 2, address its priority using its real ID, for example switch 2 priority 10. Check the confirmation prompt and planned reload workflow; changing priority does not immediately preempt a running active switch.
3. Connect the supported stack topology
The source next says to attach the stack cables. Cisco warns against connecting a powered-on standalone switch into a powered-on stack because of stack merging. Prepare/connect new members while powered off and follow the matching hardware guide and election sequence.
Archived join/election output (the source repeats SWITCH_ADDED three times):
*Jun 29 08:46:03.457: %STACKMGR-1-STACK_LINK_CHANGE:Switch 2 R0/0: stack_mgr: Stack port 1 on switch 2 is up
*Jun 29 08:46:03.457: %STACKMGR-1-STACK_LINK_CHANGE:Switch 2 R0/0: stack_mgr: Stack port 2 on switch 2 is up
*Jun 29 08:46:03.457: %STACKMGR-6-SWITCH_ADDED:Switch 2 R0/0: stack_mgr: Switch 2 has been added to the stack.
*Jun 29 08:46:03.457: %STACKMGR-6-SWITCH_ADDED:Switch 2 R0/0: stack_mgr: Switch 2 has been added to the stack.
*Jun 29 08:46:03.457: %STACKMGR-6-SWITCH_ADDED:Switch 2 R0/0: stack_mgr: Switch 2 has been added to the stack.
*Jun 29 08:46:03.457: %STACKMGR-6-ACTIVE_ELECTED:Switch 2 R0/0: stack_mgr: Switch 1 has been elected ACTIVE.
1
2
3
4
5
64. Inspect the resulting state
Switch#sh switch
Switch/Stack Mac Address : 003c.109c.ab80 - Local Mac Address
Mac persistency wait time: Indefinite
H/W Current
Switch# Role Mac Address Priority Version State
------------------------------------------------------------
*1 Active 003c.109c.ab80 15 V07 Ready
2 Member 003c.109e.2d80 10 V07 Ready
1
2
3
4
5
6
7
8This output records switch 1 as Active, priority 15, and switch 2 as Member, priority 10; both show V07 and Ready. Those printed roles are preserved, not changed to an expected Standby role. Verify the actual platform and redundancy state independently.
5. Inspect interface numbering
Switch#sh ip int brief
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES NVRAM administratively down down
GigabitEthernet0/0 unassigned YES unset down down
GigabitEthernet1/0/1 unassigned YES unset down down
GigabitEthernet1/0/2 unassigned YES unset down down
GigabitEthernet1/0/3 unassigned YES unset down down
GigabitEthernet1/0/4 unassigned YES unset down down
GigabitEthernet1/0/5 unassigned YES unset down down
GigabitEthernet1/0/6 unassigned YES unset down down
GigabitEthernet1/0/7 unassigned YES unset down down
GigabitEthernet1/0/8 unassigned YES unset down down
GigabitEthernet1/0/9 unassigned YES unset down down
GigabitEthernet1/0/10 unassigned YES unset down down
GigabitEthernet1/0/11 unassigned YES unset down down
GigabitEthernet1/0/12 unassigned YES unset down down
GigabitEthernet1/0/13 unassigned YES unset down down
GigabitEthernet1/0/14 unassigned YES unset down down
GigabitEthernet1/0/15 unassigned YES unset down down
GigabitEthernet1/0/16 unassigned YES unset down down
GigabitEthernet1/0/17 unassigned YES unset down down
GigabitEthernet1/0/18 unassigned YES unset down down
GigabitEthernet1/0/19 unassigned YES unset down down
GigabitEthernet1/0/20 unassigned YES unset down down
GigabitEthernet1/0/21 unassigned YES unset down down
GigabitEthernet1/0/22 unassigned YES unset down down
GigabitEthernet1/0/23 unassigned YES unset down down
GigabitEthernet1/0/24 unassigned YES unset down down
GigabitEthernet1/1/1 unassigned YES unset down down
GigabitEthernet1/1/2 unassigned YES unset down down
GigabitEthernet1/1/3 unassigned YES unset down down
GigabitEthernet1/1/4 unassigned YES unset down down
Te1/1/1 unassigned YES unset down down
Te1/1/2 unassigned YES unset down down
Te1/1/3 unassigned YES unset down down
Te1/1/4 unassigned YES unset down down
GigabitEthernet2/0/1 unassigned YES unset down down
GigabitEthernet2/0/2 unassigned YES unset down down
GigabitEthernet2/0/3 unassigned YES unset down down
GigabitEthernet2/0/4 unassigned YES unset down down
GigabitEthernet2/0/5 unassigned YES unset down down
GigabitEthernet2/0/6 unassigned YES unset down down
GigabitEthernet2/0/7 unassigned YES unset down down
GigabitEthernet2/0/8 unassigned YES unset down down
GigabitEthernet2/0/9 unassigned YES unset down down
GigabitEthernet2/0/10 unassigned YES unset down down
GigabitEthernet2/0/11 unassigned YES unset down down
GigabitEthernet2/0/12 unassigned YES unset down down
GigabitEthernet2/0/13 unassigned YES unset down down
GigabitEthernet2/0/14 unassigned YES unset down down
GigabitEthernet2/0/15 unassigned YES unset down down
GigabitEthernet2/0/16 unassigned YES unset down down
GigabitEthernet2/0/17 unassigned YES unset down down
GigabitEthernet2/0/18 unassigned YES unset down down
GigabitEthernet2/0/19 unassigned YES unset down down
GigabitEthernet2/0/20 unassigned YES unset down down
GigabitEthernet2/0/21 unassigned YES unset down down
GigabitEthernet2/0/22 unassigned YES unset down down
GigabitEthernet2/0/23 unassigned YES unset down down
GigabitEthernet2/0/24 unassigned YES unset down down
GigabitEthernet2/1/1 unassigned YES unset down down
GigabitEthernet2/1/2 unassigned YES unset down down
GigabitEthernet2/1/3 unassigned YES unset down down
GigabitEthernet2/1/4 unassigned YES unset down down
Te2/1/1 unassigned YES unset down down
Te2/1/2 unassigned YES unset down down
Te2/1/3 unassigned YES unset down down
Te2/1/4 unassigned YES unset down down
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68The full source output is retained, including its GigabitEthernet and Te uplink names. Treat these as that captured example, not a universal port inventory. The initial VLAN is administratively down and other interfaces are down/unassigned; this is not evidence of successful traffic forwarding.
6. Additional inspection commands and neighbors
sh switch neighbors
Show switch
Show switch detail
Show redundancy
Show redundancy state
DaSha-OFF-Inside-ASW-C9200-L#show switch neighbors
Switch # Port 1 Port 2
-------- ------ ------
1 2 2
2 1 1 In the two-member neighbor output, both stack ports on switch 1 lead to switch 2, and vice versa. Verify ring/port status and redundancy on the actual system rather than relying only on member discovery. Copied editor line-number gutters are omitted.
Official English references: C9200 StackWise architecture; verify and troubleshoot C9200/C9300 StackWise.