Table of Contents
Advertisement
and a new set of routes is relearned. The new set of routes will be the same as the old routes, unless the network has
changed.
•
OSPFv2 and OSPFv3 non-stop routing support - For more information, refer to the Ruckus FastIron Layer 3 Routing
Configuration Guide.
When control protocols are synchronized and protocol synchronization timers have expired, the standby controller is placed in
hot-standby mode, ready to take over as the active controller. If a switchover occurs, the standby controller takes over without
interrupting data traffic.
After baseline synchronization, any new events that occur on the active controller are dynamically synchronized on the standby
controller. Such events include:
•
CLI, HTTP, and SNMP configurations
•
Link events
•
Interrupts
•
Layer 2 and Layer 3 forwarding table updates
•
Dynamic user authentication updates such as 802.1X or multi-device port authentication
After a switchover, the new active controller receives updates from the stack members and sends verification information to the
stack members to ensure that they are synchronized.
NOTE
The events described previously occur internally and do not create or affect the external network topology.
Standby controller role in hitless stacking
In software releases that do not support hitless stacking, the standby controller functions as a dummy device, meaning it
provides limited access to CLI commands such as show, stack, and a few debug commands. The active controller can access the
full range of the CLI. The standby controller synchronizes its configuration with the active controller at each reset.
With the introduction of hitless stacking, the standby controller shadows the active controller. The role or behavior of the
standby controller with hitless stacking is as follows:
•
The local console on the standby controller still accepts only show, stack, and a few debug commands.
•
The runtime configuration on the standby controller is synchronized with the active controller whenever there is a
configuration change.
•
Protocols are configured in the runtime configuration, but no protocol packets are sent out on the standby controller.
•
The state of every unit is known, including the state of the active controller. The show commands display current
information such as STP or port states.
•
When a failover occurs, the standby controller uses its current runtime configuration. The configuration could be
different from the active controller if the last configuration transmission was lost.
•
After a failover, the new active controller (the old standby controller) programs all other units in hardware, based on its
runtime configuration.
Standby controller election
Candidates for standby controller must meet the following criteria:
•
The unit is operational, and the image and module configuration match those of the active controller.
Ruckus FastIron Stacking Configuration Guide, 08.0.90
Part Number: 53-1005572-01
Hitless Stacking
Standby controller role in hitless stacking
177
Hide quick links:
Advertisement
Table of Contents
Troubleshooting
