CB stack merges and breaks

CB stack merges

When two CB stacks merge, they behave according to the rules governing stack merges described in the RUCKUS FastIron Stacking Configuration Guide. The active controller that loses the new controller election reboots. The PE groups from the losing stack join the winning CB stack, and PE units are initialized.

CB stack breaks

if hitless-failover is enabled and the active controller leaves the CB stack, the standby controller takes over immediately.

When a CB stack breaks, two CB stacks may form if the units that break away include a standby controller. In this case, the standby takes control to form a stack or a standalone. Each stack owns any PE unit directly connected to the stack. Each stack removes any live PE unit that is not linked to the stack. The old active controller for the CB owns any PE unit that has LAG ports connected to both stacks.

Refer to the RUCKUS FastIron Stacking Configuration Guide for detailed information on traditional stack breaks and merges.