Controller Based WLANs

Introduction : As we all know, Access Points and Controllers exchange heartbeat messages as keepalive mechanism and the interval between each heartbeat is 1 (one) second by default. In case of Remote Access Point, which is terminating on to the controller over Internet, this frequent exchange of hearbeats causes increase in bandwidth usage.


This issue has been addressed in ArubaOS 6.3.0.0, by having the heartbeat interval as a configurable parameter for Campus Access Points (CAP's), Remote Access Points (RAP's) and Mesh Portals.

Feature Notes :

Environment : This article applies to Aruba Mobility Controllers and Aruba Access Points running ArubaOS version 6.3.0.0 or higher.

Configuration Steps : Access Point, on connecting to associated controller and downloading system profile, informs internal datapath module to start sending heartbeats to controller. Before sending heartbeats, ap datapath looks for heartbeat interval value configured in ap system profile.


From CLI, 

In the ap system profile, configure it using the below command:

"heartbeat-interval"

Below is configuration screenshot from controller:






From WebUI:


Navigate to AP Group and then to respective AP System Profile -> then Click on Advance tab