Troubleshooting Stack Interactive-setup

Stack interactive-setup can be used to form linear and ring stack topologies. For information about the procedure, refer to Scenario1 - Using stack interactive-setup to create a stack.

If stack interactive-setup does not detect all the units that should be detected, perform the following checks:

• Make sure that all the cables are properly connected.
• Make sure that all the relevant ports are in the UP state.
• Make sure that all the units are running the same image.
• Issue the stack enable command only on the unit that will serve as the active controller.
• Make sure that stack disable is not configured on any prospective members (for example, by entering the show running-config command on the unit).
• Check to see if spanning tree protocols (STP, RSTP, PVST, or MSTP) are configured either globally or on the default VLAN. Connecting new links or new units without configuring spanning tree protocols creates Layer 2 loops. Loops cause high traffic count on the affected ports and may cause high CPU utilization if the looped packets are trapped to the CPU. Stack interactive-setup and many functions may not work properly in a looped environment.
  Note: RUCKUS recommends that you configure STP globally or on the default VLAN before making new stacking connections. If the system is already experiencing loops before you configure STP, STP may not converge when the looping packets have higher priority than STP's BPDU packets. Refer to Stacking deployment guidelines for information on handling loops.

If stack interactive-setup times out (this may happen due to inactivity), you will not be able to make any changes in your configuration or stack topology until you restart the session by entering the stack interactive-setup command.