Troubleshooting a mismatched stack-ID

Cause
Action
  1. This stack example has two members and two more members that were strictly provisioned, following the initial install deterministic method.

    Displaying a stack with 3 unjoined switches

    switch# show stack
    
    Stack ID         : 00031cc1-de4d87c0
    MAC Address      : 1cc1de-4dc765
    Stack Topology   : Chain
    Stack Status     : Active
    Uptime           : 0d 0h 2m
    Software Version : WB.15.11.0000x
    
    Mbr
    ID  Mac Address   Model                                 Pri Status
    --- -----------   ------------------------------------- --- -----------
    1   1cc1de-4d87c0 HPE J9727A 2920-24G-PoE+-2SFP+ Switch  200 Standby
    2   1cc1de-4dc740 HPE J9729A 2920-24G-PoE+-2SFP+ Switch  128 Commander
    3   1cc1de-4dbd40 HPE J9726A 2920-24G-2SFP+ Switch       128 Not Joined
    4   1cc1de-4d79c0 HPE J9728A 2920-48G-4SFP+ Switch       175 Not Joined
    

    When powering on switch #:3, it does not join the stack.

  2. The stack ports for the new switch appear online, but the show stacking command shows that the switch has not been recognized.
    switch# show logging -r -s
    I 10/02/00 00:46:56 02558 chassis: ST1-STBY: Stack port 3 is now on-line.
    I 10/02/00 00:46:56 02558 chassis: ST2-CMDR: Stack port 2 is now on-line.
    Displaying the switch is not recognized
    switch(config)# show stacking stack-ports member 1,2
    
    Member 1
    
    Member Stacking Port  State Peer Member   Peer Port
    ------ -------------- ----- ------------- -------
    1      1              Down  0             0
    1      2              Up    2             1
    1      3              Down  0             0
    1      4              Down  0             0
    
    Member 2
    
    Member Stacking Port  State Peer Member   Peer Port
    ------ -------------- ----- ------------- -------
    2      1              Up    1             2
    2      2              Up    0             0
    2      3              Down  0             0
    2      4              Down  0             0
  3. 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.

    Output from the “not joined” switch
    switch# show stacking
    
    Stack ID         : 00011cc1-de4dbd40
    MAC Address      : 1cc1de-4dbd64
    Stack Topology   : Unknown
    Stack Status     : Active
    Uptime           : 0d 0h 1m
    Software Version : WB.15.11.0000x
    
    Mbr
    ID  Mac Address   Model                             Pri Status
    --- ------------- --------------------------------- --- -------------------
    1   1cc1de-4dbd40 HPE J9726A 2920-24G-2SFP+ Switch   128 Commander
  4. 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 Stack 2920 stacking factory reset.
    switch# 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.