05-04-2017 01:50 AM
Is there any reason why an ALE (running in estimated mode with Airwave) has the graph on the monitoring page showing the number of UNASSOCIATED CLIENTS at zero but the ASSOCIATED CLIENT is showing an expected number??
I have two ALE servers with two local controllers connected to each, both ALE are importing maps from the same Airwave but one of the ALE servers refuses to show any activity on the UNASSOCIATED USERS graph, whilst the other one does.
ALE is version 18.104.22.168
05-04-2017 06:31 AM
Are you able to generate PDB file on the ALE server which is not displaying unassociated clients information in dashlet from maintainence tab?
If PDB generation is deferred or fails, ALE cannot calculate device location. Campus, Building, Floor, Location, and Geo_Fence APIs are not published, and the unassociated clients dashlet may not show any data.
Have you enabled RTLS option on this server ,if YES try disable and generated PDB.
05-04-2017 07:06 AM
I regenerated the PDB this morning and it completed successfully.
I am getting plenty of location events from that server but that graph never displays it yet on the other ALE it is. The only difference between the servers are the controllers that are talking to it. Could it be something on the controllers??
05-04-2017 11:53 AM
We could also use Location API/ Presence API and see in output whether we are seeing the association status as false for any client.
False status means client is unassociated.
Presence API queries use the following URL syntax:
Location API queries use the following URL syntax:
If we have unassociated clients but still not showing graphs try restart the location engine and check the status.
Does anonymization is enabled on this server, if Yes try disable it and check once.
We have bug in older version where when we enable anonymization unassoicated client count graph showing incorrect, it is fixed in latest code 22.214.171.124.
Bug 49413 Symptom: The unassociated client count increased continuously when anonymization was enabled, as ALE failed to clear old client records from the database.Scenario: This occurred in ALE 126.96.36.199 and earlier.