Table of Contents
Advertisement
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
page 34 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.
Troubleshooting unit replacement issues
The unit replacement process is intended to replace one unit with a clean unit of exactly the same model without entering any
command. Unit replacement is not designed to discover new units. Refer to Replacing stack units in
guidelines
on page 34 for more information.
Check the following items when you experience unit replacement issues.
•
The replacement unit is a clean unit (does not contain a startup-config.txt file).
•
The replacement unit running configuration does not contain the stack enable command.
•
The replacement unit running configuration does not contain the stack disable command.
•
The configurations for the stack ports on the active controller match the physical connections to the unit.
•
Only one unit is being replaced at a time. If the active controller detects multiple new units, it issues warning messages.
•
The clean unit must match only one reserved stack unit configuration. The active controller issues warning messages if
the new unit matches multiple units.
•
The console of the new unit displays a warning message if the unit receives unit-replacement packets when it does not
qualify for unit replacement.
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01
ICX Stack Troubleshooting
Troubleshooting unit replacement issues
Stacking deployment guidelines
Stacking deployment
on
241
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
