Active Controller And Standby Controller Resets - Arris Ruckus ICX 7850 Series Configuration Manual

• Longer up time - The unit with the longest up time if the up time is at least 30 seconds longer than for any other unit.
When up times are compared, there is no effect if the difference is less than 30 seconds.
• Lowest boot stack ID - The unit that has the lowest boot stack ID. Unit ID 1 is the lowest. The unit ID may be 1 through
12.
• MAC address - The member with the lowest MAC address.
When hitless failover is disabled, the following factors, in the order shown, are used to determine active and standby controllers.
• Boot as active controller - Indicates that a unit was previously active controller before the current boot sequence and will
again assume the role of active controller when two standalone units are combined into a stack. When a third
standalone unit joins the stack, the current active controller becomes subject to the other factors in this list. You can
upgrade your current active controller to "boot as active controller" status by executing the write memory command.
The system interprets the write memory action as a directive to maintain the current active controller role regardless of
resets or a new unit joining the stack.
• Priority - The unit with the highest priority value.
• Greater number of members - The unit that has control over the greater number of stack members.
• Longer up time - An up time that is more than 30 seconds longer than the next one in size is considered. Where up times
are compared, there is no effect if the difference is less than 30 seconds.
• Lowest boot stack ID - The unit that has the lowest boot stack ID. Unit ID 1 is the lowest. The unit ID may be 1 through
12.
• MAC address - The member with the lowest MAC address.

Active controller and standby controller resets

If hitless stacking failover is enabled, when an active controller is reset or removed from the stack, the standby controller takes
over immediately.
NOTE
Hitless stacking failover is enabled by default.
The stack behaves differently when a failover occurs depending on whether hitless-failover enable is configured. If it is not
configured and the active controller is reset or removed from the stack, the standby reloads the entire stack. The standby reloads
to become the active controller. If hitless-failover enable is configured, the standby takes over immediately without reloading any
unit.
If both the active and the standby controllers are removed, the rest of the stack continues to function because the other stack
members are operating on whatever is programmed in the hardware. However, the stack members are not able to learn any new
addresses. In this case, the following message is displayed every few minutes.
Stack member is non-operational because of no Active or standby controller
You can recover to standalone mode by "stack unconfigure me"
Use the stack unconfigure me command to restore the units as standalone devices with a pre-stacking configuration.
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01
Stack Management
Stack device roles and elections
199