Monitoring, Management & Location Tracking

Few clients missing in ALE though they are present in Airwave & controller

MVP
MVP
Q:

Few Clients  missing in ALE though they are present in Airwave and contorller

 

(024-ARMC-01) #show user-table mac 70:1C:E7:14:7B:C0

 

Users

-----

    IP             MAC            Name     Role        Age(d:h:m)  Auth    VPN link  AP name       Roaming   Essid/Bssid/Phy                      Profile               Forward mode  Type    Host Name

----------    ------------       ------    ----        ----------  ----    --------  -------       -------   ---------------                      -------               ------------  ----    ---------

10.24.36.151  70:1c:e7:14:7b:c0  boan2908  AFK-laerer  00:02:12    802.1x            024-IKT-AP01  Wireless  Akershus-FK/18:64:72:19:6e:32/a-VHT  Akershus-FK-aaa_prof  tunnel        Win 10

 

can see the access point the client is connected to is active on that controller.

 

(024-ARMC-01) #show ap active

 

Active AP Table

---------------

Name                     Group       IP Address    11g Clients  11g Ch/EIRP/MaxEIRP  11a Clients  11a Ch/EIRP/MaxEIRP    AP Type  Flags  Uptime          Outer IP

----                     -----       ----------    -----------  -------------------  -----------  -------------------    -------  -----  ------          --------

024-IKT-AP01             024-Vestby  10.24.36.34   0            AP:HT:11/12.0/18.5   3            AP:VHT:36E/23.0/23.0   225      Ada    23d:15h:5m:40s  N/A



A:

Check whether ALE is calculating the location of the missing client. We need to tail the location log to see whether location is getting calculated for that specific client or not. If location itself is not getting calculated then issue might be due to RSSI value, need to check on deployment side.

 

#tail –f /opt/ale/ale-location/logs/ale-location.log | grep 701ce7147bc0

2017-11-10 09:37:19.494 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:37:49.627 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:38:30.062 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:38:59.929 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:39:19.335 CET [pool-1-thread-2] DEBUG c.a.a.l.records.StationRecord - TARGET_TYPE_STATION 701ce7147bc0 scheduled with 2 RSSIs:[RssiRecord [rssi=-49, tsSecs=1510303027, bssid=24dec6fa0870, channel=0, classificationType=-1], RssiRecord [rssi=-49, tsSecs=1510303028, bssid=24dec6fa0870, channel=0, classificationType=-1]]

2017-11-10 09:39:19.821 CET [engine-worker-4] DEBUG c.a.a.l.records.StationRecord - New location for TARGET_TYPE_STATION 701ce7147bc0: x=31.966356, y=8.974388, floor=995A5F24F45C3A22AB9921BC38592CA7, algo=ALGORITHM_LOW_DENSITY

2017-11-10 09:39:29.914 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:40:00.096 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:40:30.227 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:41:00.366 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:41:30.579 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:42:00.701 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:42:30.860 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:43:11.087 CET [pool-1-thread-2] TRACE c.a.a.l.handlers.BasicMatrixHandler - Station 701ce7147bc0 reported by unknown BSSID 186472196e30

2017-11-10 09:43:30.256 CET [pool-1-thread-2] DEBUG c.a.a.l.records.StationRecord - TARGET_TYPE_STATION 701ce7147bc0 scheduled with 2 RSSIs:[RssiRecord [rssi=-51, tsSecs=1510303329, bssid=24dec6fa0870, channel=0, classificationType=-1], RssiRecord [rssi=-51, tsSecs=1510303258, bssid=24dec6fa0870, channel=0, classificationType=-1]]

2017-11-10 09:43:30.470 CET [engine-worker-4] DEBUG c.a.a.l.records.StationRecord - New location for TARGET_TYPE_STATION 701ce7147bc0: x=10.036356, y=9.970388, floor=995A5F24F45C3A22AB9921BC38592CA7

 

 

In above logs, we see client location is getting calculated by a unknown BSSID, We see such log entrees, if AP details missing in airwave or visualrf. Check whether this particular AP which is reporting this station is added to Airwave and also provisioned in VisualRF. ALE get AP location from VisualRF.

 

Version history
Revision #:
2 of 2
Last update:
‎06-08-2019 04:33 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: