Troubleshooting maximum stack members exceeded

Cause

This failure can happen if you have an active stack that has already reached its maximum number of members. It can also happen when the maximum number of switches is reached with a combination of active members and strictly provisioned members.

Since one of the suggested initial deployment techniques is a deterministic method using strictly provisioned entries, this failure example demonstrates what occurs if the maximum number of members is reached by strictly provisioning 10 members. At least one of these configuration entries has an incorrect MAC addresses. Similar to the mismatched MAC address example, the stack attempts to “plug-and-go” to add the switch, however, since the maximum number of membership has already been reached, the switch cannot join the stack.

Action
  1. The following example shows the show stacking output before the switch attempts to join.

    Viewing stack members before the join

    switch(config)# show stack
    
    Stack ID         : 02009418-82d83c40                                           
              
    MAC Address      : 941882-d83c49    
    Stack Topology   : Chain                                   
    Stack Status     : Active                                  
    Split Policy     : One-Fragment-Up 
    Uptime           : 0d 15h 3m   
    Software Version : WC.16.04.0000x
    
    Mbr                                                                            
     ID  Mac Address   Model                               Pri Status         
     ---------------------------------------------------------------------
     *1  941882-d83c40 Aruba JL321A 2930M-48G Switch       150 Commander      
      2  9cdc71-f576c0 Aruba JL324A 2930M-24SR-PoE+ Switch 128 Member         
      3  941882-d91a40 Aruba JL319A 2930M-24G Switch       128 Standby        
      4  9cdc71-f2bbc0 Aruba JL324A 2930M-24SR-PoE+ Switch 128 Member         
      5  941882-d9a240 Aruba JL321A 2930M-48G Switch       128 Not Joined         
      6  941882-d9e900 Aruba JL319A 2930M-24G Switch       128 Not Joined         
      7  9cdc71-f8f480 Aruba JL323A 2930M-40G-8SR-PoE+ Sw..128 Not Joined         
      8  941882-da0f40 Aruba JL319A 2930M-24G Switch       128 Not Joined         
      9  9cdc71-f8d400 Aruba JL323A 2930M-40G-8SR-PoE+ Sw..128 Not Joined         
      10 9cdc71-f54940 Aruba JL324A 2930M-24SR-PoE+ Switch 128 Not Joined
  2. When a switch that does not match the MAC addresses attempts to join, that switch reboots when the maximum configuration is detected. The active stack logs the following:
    W 10/07/00 06:01:11 03253 stacking: ST3–CMDR: Maximum number of switches in the stack has been reached. Cannot add 1cc1de-4da900 type JL324A.
  3. The failure can be due to one of the strictly provisioned entries being incorrect. To correct this entry, reboot the switch. If there are already 10 switches in the stack, you cannot add additional switches at this time.