Environment : Product and Software: This article applies to Aruba Instant Access Points (IAP's) running on Aruba InstantOS 220.127.116.11-18.104.22.168 and later.
Aruba Instant does not require an external mobility controller to regulate and manage the Wi-Fi network. Instead, one IAP in every network assumes the role of a Virtual Controller (VC).
Below-mentioned is the brief description on the Election Process:
- IAP boots up, stay in ‘INITIAL’ state for a while, if it receives any master beacon, it becomes slave.
- If no master beacon received, transition to ‘Pot-Master’ state (Pot: Point of Time) and stay for a while. If it receives any master beacon during this period, trigger the conflict resolve algorithm to compute a new master.
- If no master beacon received, transition to ‘Master’ state and start to broadcast master beacon. If it receives any master beacon during this period, trigger the conflict resolve algorithm to compute a new master.
- At any time, if a slave do not hear master beacon for a while, it uses the same manner to do the transition.
IAP uses following order as Conflict Resolve Algorithm, to resolve conflicts:
- look into IP scope. IAP with default-ip cannot win
- look into 3G capability
- look into AP class, Arran (IAP-13x) gets higher priority
- look into uptime, older AP gets higher priority
- look into AP MAC, bigger address gets higher priority
- Master is running with default-ip, a new IAP comes up and gets DHCP address and thereby becomes the new Master. At the same time, any IAP with default-ip will reboot automatically for IP recovery.
- Master (without 3G dongle) is UP for less than 5 mins, then a new IAP (with 3G dongle) comes up. The new IAP becomes the new Master.