Troubleshoot a mismatched stack-ID
This is an example of a stack that has two members with three more members that have been strictly provisioned, following the deterministic method of initial installation.
Viewing a stack with 3 unjoined switches
switch# show stack
Stack ID : 01009418-82d9e900
MAC Address : 941882-da0f62
Stack Topology : Chain
Stack Status : Active
Split Policy : One-Fragment-Up
Uptime : 0d 0h 3m
Software Version : WC.16.04.0000x
Mbr
ID Mac Address Model Pri Status
--- ----------------- ------------------------------------- --- ---------------
1 941882-d83c40 Aruba JL321A 2930M-48G Switch 128 Not Joined
2 941882-d91a40 Aruba JL319A 2930M-24G Switch 128 Not Joined
3 941882-d9a240 Aruba JL321A 2930M-48G Switch 128 Not Joined
*4 941882-da0f40 Aruba JL319A 2930M-24G Switch 128 Commander
5 941882-d9e900 Aruba JL319A 2930M-24G Switch 128 Standby
When powering on switch 3, it does not join the stack.
The stack ports for the new switch appear online, however, the
show stacking
command shows that the switch has not been recognized.
Viewing the switch is not recognized
switch(config)# show stack
Stack ID : 01009418-82d9a240
MAC Address : 941882-d9a249
Stack Topology : Chain
Stack Status : Active
Split Policy : One-Fragment-Up
Uptime : 0d 0h 1m
Software Version : WC.16.04.0000x
Mbr
ID Mac Address Model Pri Status
--- ----------------- ------------------------------------- --- ---------------
*3 941882-d9a240 Aruba JL321A 2930M-48G Switch 128 Commander
The
show stacking command does not show that the member is “Not Joined.”
A log file indicates that a “topo /hello” was seen from a switch that was not part of the current stack ID. The console of the switch that should have been member 3 shows the following example output.
Viewing output from the “not joined” switch
switch(config)# show stacking stack-ports member 4,5 Member 4 Member Stacking Port State Peer Member Peer Port ------ ------------- -------- ----------- --------- 4 1 Down 0 0 4 2 Up 5 1 Member 5 Member Stacking Port State Peer Member Peer Port ------ ------------- -------- ----------- --------- 5 1 Up 4 2 5 2 Down 0 0
The output is different if you have an inactive fragment, since this switch can have the configuration from an old stack. In this case, it might be inactive and show ‘missing’ switches from the old configuration. The stack-id value does not match the stack ID of the Aruba Stack 2930M stacking factory reset.
switch(config)# stacking factory-reset
Configuration will be deleted and device rebooted,continue [y/n]?
Y
To join this switch to the other stack, execute the
stacking factory-reset
command to erase all of the stale stacking configuration information. This command automatically reboots the switch and on its subsequent boot, the switch is able to join the new stack.