User's Manual

Availability, mobility, and controller functionality
hwc_controlleravailmobility.fm
Availability overview
A31003-W1050-U100-2-7619
, March 2008
258 HiPath Wireless Controller, Access Points and Convergence Software V5 R1 , C20/C2400 User Guide
After the Wireless AP on the failed HiPath Wireless 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 HiPath Wireless
Controller after five minutes of attempting, the Wireless AP will reboot.
If the AP is assigned to different VNSs on the two controllers, it will reboot.
Because of the pairing of the two HiPath Wireless Controllers, the Wireless AP
will then register with the other HiPath Wireless 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 page.
Note: A Wireless AP connects first to a HiPath Wireless Controller registered as
ac_manager and, if not found, then seeks an ru_manager. If the primary HiPath
Wireless Controller fails, the secondary one registers as ru_manager. This
enables the secondary HiPath Wireless Controller to be found by Wireless APs
after they reboot.
When the Wireless APs connect to the second HiPath Wireless Controller, they
will be assigned to the VNS that is defined in the system’s default AP
configuration. The wireless device users will log in again and be authenticated on
the second HiPath Wireless Controller.