Managing Traditional Stack Partitioning; Merging Traditional Stacks - Ruckus Wireless ICX 7450 Configuration Manual

• unit-id - Designates stack member or members to reload. The
combination, such as 2,4-6,8. Values must be separated by a comma, with no space.
If you need to reload the active controller, use the stack switch-over command. When switchover occurs, the original active controller can
be reloaded using the reload unit-id command.

Managing traditional stack partitioning

Ring topology stacks do not partition when a stack member fails. Operation is interrupted briefly while the stack recalculates a new path.
Ring topologies are more stable than linear topologies because they provide redundant pathways in case of accidental failure.
When a unit in a traditional stack with a linear topology fails, the traditional stack divides (partitions) into two or more separate stacks that all
have the same configuration. This may cause an IP address conflict in the network. To keep the stacks separate, change the IP address of
each new stack.
When a stack breaks into partitions, the partition with the active controller remains operational. If a partition contains the standby controller,
this partition becomes operational because the standby controller assumes the active role and reloads the partition units. However, if hitless
failover is enabled, the partition units are not reloaded. A partition without an active controller or standby controller does not function. To
reconfigure these units to act in standalone mode, you must first enter a stack unconfigure me command on each unit.
To reverse the partitioning, reconnect all of the units into the original stack topology using the stacking ports. This is the same as merging
stacks. If the original active controller again has the highest priority, it regains its role. If two partition active controllers have the same priority,
the active controller with the most stack members is elected. This process helps minimize traffic interruption.

Merging traditional stacks

Traditional stacks may be merged, but the total number of stack units must not exceed the maximum stack supported by the device. For
example, you could combine two stacks of ICX 7750 devices with four units each into a single stack of eight units.
NOTE
You cannot use secure-setup to merge stacks because secure-setup does not work across stack boundaries.
You can merge stacks by connecting them together using the stacking ports. Before doing this, make sure that no stacking ports (for
example, ports on an end unit in a linear stack topology) have been reconfigured as data ports.
When stacks are merged, an election is held among the active controllers. The winning controller retains its configuration and the IDs of all
of its original stack members. The remaining stack units lose their configuration and are reset. If the IDs of the losing stack units conflict with
the IDs of the winning units, they may change, and the IDs will no longer be sequential.
NOTE
You can use secure-setup to renumber the members in the newly merged stack. Refer to
for more information.
The following examples show how stack merging works:
• If a stack partitions into multiple stacks because of a connection failure, you can fix the connection and the stack partitions will
merge back into the original stack with no change to stack IDs because all stack IDs are distinct.
• In a linear stack topology, the end units of the stack have only one stacking port configured. Before you can merge two linear
stacks, you must reconfigure the end units so that both ports are stacking ports.
Ruckus FastIron Stacking Configuration Guide, 08.0.40b
Part Number: 53-1003910-11
unit-list variable can be a single ID, a list of IDs, a range of IDs, or a
Traditional Stack Management

Merging traditional stacks

Renumbering stack units on page 131
133