ALE integration with IAP

by on ‎08-06-2014 02:11 PM

IAP can be used with ALE server in order to determine the position of clients and analyze user behavior.

 

VC sends associated and unassociated client information to ALE server. Other information IAP sends include Virtual Controller details, AP table, and radio table If the ALE sever is configured with a host name, then before sending any information, the VC perform mutual certificated-based authentication with ALE server in the same manner as with Activate and Athena Where possible, VC sends changes in information instead of a whole update

The information sent is encoded in the google ProtoBuf format, a flexible, efficient, and automated mechanism for serializing structured data.
 
Environment: IAP cluster and Meridian App SSL tunnel the ALE server.
 
Network Topology : rtaImage (2).jpg
CLI Configuration:
 
#ale-server <server>  
#ale-report-interval <internal>

Note:

ALE server address could be ip/fqdn or ip:port/fqdn:port format
 
ALE-report-interval: iap post info per ale-report-interval, range is 6~60s, default is 30s.

UI configuration:
 
rtaImage (3).jpg
 
Findings clients location:
 
http://10.65.182.126:8080/api/v1/location?sta_eth_mac=F4:F1:5A:70:CC:BE
 
rtaImage (4).jpg


# show ale config


ALE Config
----------
Type                 Value
----                 -----
ale-server           10.65.182.125:8088
ale-report-interval  30

 

# show ale status


ALE Status
----------
Type                   Value
----                   -----
ale login status       True
ale login status code  success
ale fail times         0
ale request state      Idle

 

#show log system | include ale


Nov 16 06:43:22  cli[1552]: <341299> <DBUG> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: op Delete encode client message, total station count 0.Nov 16 06:43:22  cli[1552]: <341295> <INFO> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: encode delete message succeed, total msg len 64.Nov 16 06:43:22  cli[1552]: <341299> <DBUG> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: op Add encode client message, total station count 0.Nov 16 06:43:22  cli[1552]: <341295> <INFO> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: encode add message succeed, total msg len 128.Nov 16 06:43:22  cli[1552]: <341299> <DBUG> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: op Update encode client message, total station count 0.Nov 16 06:43:22  cli[1552]: <341300> <DBUG> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: access point op Update, ap's mac d8:c7:c8:cd:ea:65, ap's name d8:c7:c8:cd:ea:65, ap's ip 10.64.20.188.Nov 16 06:43:22  cli[1552]: <341295> <INFO> |AP d8:c7:c8:cd:ea:65@10.64.20.188 cli|  ale: encode update message succeed, total msg len 6899.

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.