Managing Stack Partitioning; Merging Stacks - Arris Ruckus ICX 7850 Series Configuration Manual

Stack Management

Managing stack partitioning

When the reload command is entered on the active controller without the unit-id parameter as shown in the following example,
the entire stack reloads.
device# reload
NOTE
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.
You can specify a list of stack members to reload as shown in the following example.
device# reload unit-id 1,2,4-8
The example reloads units 1 and 2 and units 4 through 8.
For additional information on the reload command, refer to the Ruckus FastIron Command Reference.

Managing 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 stack with a linear topology fails, the 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 stacks

Ruckus ICX 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 interactive-setup to merge stacks because interactive-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.
216
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01