Events And Actions During A Failover - Extreme Networks Summit WM20 User Manual

Availability and Controller Functionality

Events and Actions During a Failover

If one of the Summit WM Controllers in a pair fails, the connection between the two Summit WM
Controllers is lost. This triggers a failover mode condition, and a critical message is displayed in the
information log of the remaining Summit WM Controller.
After the Wireless AP on the failed Summit WM Controller loses its connection, it will try to connect to
all enabled interfaces on both controllers without rebooting. If the Wireless AP is unsuccessful, it will
begin the discovery process. If the Wireless AP is not successful in connecting to the Summit WM
Controller after five minutes of attempting, the Wireless AP will reboot.
If the AP is assigned to different WM-ADs on the two controllers, it will reboot. Because of the pairing
of the two Summit WM Controllers, the Wireless AP will then register with the other Summit WM
Controller.
All user sessions using the AP that fails over will terminate unless the Maintain client sessions in
event of poll failure option is enabled on the AP Properties tab or AP Default Settings screen.
NOTE
A Wireless AP connects first to a Summit WM Controller registered as ac_manager and, if not found, then seeks an
ru_manager. If the primary Summit WM Controller fails, the secondary one registers as ru_manager. This enables the
secondary Summit WM Controller to be found by Wireless APs after they reboot.
When the Wireless APs connect to the second Summit WM Controller, they will be assigned to the WM-
AD that is defined in the system's default AP configuration. The wireless device users will log in again
and be authenticated on the second Summit WM Controller.
156
Summit WM20 User Guide, Software Release 4.2