Controller-less WLANs

What are CPU management options on an Instant Access Point?

by on ‎04-09-2015 03:59 AM

Environment : This article applies to Aruba Instant Access Points running InstantOS 3.4 and later.

 

Aruba Instant is a cluster architecture, where in all slave IAPs need continuous supply of master beacons from the IAP acting as Virtual Controller(VC). Delay in these beacons, cause the slave IAP to assume the current master is down and transition itself for an election of new master. This could cause if virtual controller allocates excessive CPU for Datapath and Management of associated clients, thereby delaying or queuing the master beacons. This is mainly observed in high client density environments.

To avoid these circumstances, InstantOS 3.4 introduces a feature to reserve Virtual Controller CPU for management and Control Plane functions.
 
Below screen shot from Instant GUI shows the Dynamic CPU Management options for specific environments:
 
rtaImage.png
 
Screenshot below guides to enable the feature via command line:
 
rtaImage.jpg
 
 
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.