Monitoring, Management & Location Tracking

No Location Events Generated on ALE
Problem:

Selecting a floor on the ALE Map dashboard will throw out an error "No location data found on floor"

 

No location data found on floor

 

 

 

 

 



Diagnostics:

We will have to check the data feed reader to see if ALE is receiving data feeds from controller ( or IAP) or not.

 

[root@ale ~]# /opt/ale/bin/feed-reader -f location
Attempting to 'connect' to endpoint: tcp://localhost:7779
Connected to endpoint: tcp://localhost:7779
Subscribed to topic: "location"

 

If no location events are generated, follow the troubleshooting steps mentioned in the section titled Solution



Solution

Problem: The ALE feed-reader output does not display any location events.

 

Below is a systematic check to isolate the issue. The feed-reader should show output on the screen.

 

An example of a the logs from healthy ALE server.

[root@ale ~]# /opt/ale/bin/feed-reader -f location
Attempting to 'connect' to endpoint: tcp://localhost:7779
Connected to endpoint: tcp://localhost:7779
Subscribed to topic: "location"

[163] Recv event with topic "location"
seq: 386919601
timestamp: 1459144630
op: OP_UPDATE
topic_seq: 17365188
source_id: 74867AD029E7
location {
    sta_location_x: 376.225
    sta_location_y: 119.738
    error_level: 56
    associated: false
    campus_id: 70A685841CAE395EA407F45E197348F7
    building_id: 6D4B8CFE4251375F893A3C9A2190D019
    floor_id: EFB4C4538F2732A9AB0590C0D67B2154
    hashed_sta_eth_mac: C907DEFA23F45FD6D06B975D0058301E0AD13A49
    loc_algorithm: ALGORITHM_CALIBRATION
    longitude: 103.859
    latitude: 1.29511
    altitude: -5
    unit: FEET
}

[164] Recv event with topic "location"
seq: 386919602
timestamp: 1459144612
op: OP_UPDATE
topic_seq: 17365189
source_id: 74867AD029E7
location {
    sta_location_x: 242.938
    sta_location_y: 301.975
    error_level: 58
    associated: false
    campus_id: 70A685841CAE395EA407F45E197348F7
    building_id: 6D4B8CFE4251375F893A3C9A2190D019
    floor_id: EFB4C4538F2732A9AB0590C0D67B2154
    hashed_sta_eth_mac: 7276E1E7324467C54B86236DE8CAE5B5AAAC7C0C
    loc_algorithm: ALGORITHM_CALIBRATION
    longitude: 103.859
    latitude: 1.29455
    altitude: -5
    unit: FEET


Below are the checks we must run.

Check 1: Does ALE generate any events at all?

[root@ale ~]# /opt/ale/bin/feed-reader
Attempting to 'connect' to endpoint: tcp://localhost:7779
Connected to endpoint: tcp://localhost:7779
Subscribed to topic: ""

Check 2: Is ALE receiving client RSSI feed from the controller/IAP?

If the source for client RSSI is AMON:

[root@ale ~]# /opt/ale/bin/feed-reader -e tcp://localhost:7778
Attempting to 'connect' to endpoint: tcp://localhost:7778
Connected to endpoint: tcp://localhost:7778
Subscribed to topic: ""

If the source for client RSSI is RTLS:

[root@ale ~]# /opt/ale/bin/feed-reader -e tcp://localhost:7777
Attempting to 'connect' to endpoint: tcp://localhost:7777
Connected to endpoint: tcp://localhost:7777
Subscribed to topic: ""

 

Check 3: Is the controller's physical IP correctly configured on ALE?

Only the physical/switch IP of the controller is recommended to be configured on ALE.

Check 4: Is the ALE IP address correctly configured on the controller/VC?

On the controller: Under Configuration -> Management -> Scroll down to the Analytics and Location Engines section -> Verify whether an ALE entry is configured.

 

 

 

On the IAP VC: Under VC homepage -> Expand on More -> Services -> RTLS tab -> Verify whether the Analytics & Location Engine knob is checked and the ALE IP address is configured.

 

ALE entry on IAP.png

 

Check 5: Is NTP correctly set up on ALE and the controller/IAP?

On ALE: Under Configuration' -> Options -> NTP Server -> Verify whether an IP address is configured for the NTP server. If not, specify one and click onApply.

Check 6: Is ALE receiving data from the controller/IAP?

For AMON feed from the controller:

[root@ale ~]# tcpdump port 8211
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
00:01:41.424288 IP 10.70.20.252.8211 > 10.70.120.248.8211: UDP, length 1370
00:01:41.424848 IP 10.70.20.252.8211 > 10.70.120.248.8211: UDP, length 1370
00:01:41.425149 IP 10.70.20.252.8211 > 10.70.120.248.8211: UDP, length 1370

For RTLS feed from the controller, filter on the port that was configured on the controller and ALE. In the example below, port 8855 was used. The source IP addresses in the output correspond to traffic from different APs.

[root@ale ~]# tcpdump port 8855
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
19:49:18.387301 IP 10.70.20.203.fuscript > 10.70.120.248.8855: UDP, length 392
19:49:18.515666 IP 10.70.20.198.fuscript > 10.70.120.248.8855: UDP, length 392
19:49:18.581172 IP 10.70.20.194.fuscript > 10.70.120.248.8855: UDP, length 392
19:49:18.806412 IP 10.70.20.205.fuscript > 10.70.120.248.8855: UDP, length 436

For traffic from an Instant AP cluster, filter on the destination port that was configured on the Instant VC. TCP 8088 is used in the example command below.

[root@ale ~]# tcpdump port 8088
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes


Check 7: Are the APs on the controller/IAP cluster able to hear client devices in their vicinity?

On the controller:

(pfe-controller) # show ap monitor client-list ap-name POC-ALE-03-81:92

Monitored Client Table
----------------------
mac                bssid              essid             channel  sta-type     auth  phy-type       dt/mt            ut/it      snr  rssi  cl-delay
---                -----              -----             -------  --------     ----  --------       -----            -----      ---  ----  --------
60:f8:1d:b7:64:48  ac:a3:1e:55:89:72  hpn-byod          48       interfering  no    80211a-VHT-40  559/559          1/0        14   81    -
84:3a:4b:34:1d:5e  94:b4:0f:5c:a2:b0  App-Test-JI       36       interfering  yes   80211a-HT-40   756/756          3/2        10   85    -
5c:e0:c5:89:2b:f0  ac:a3:1e:55:6f:51  ethersphere-wpa2  48       interfering  no    80211a-VHT-40  1385/1385        3/43       13   82    -
c8:e0:eb:39:26:bf  18:64:72:e5:8e:90  pfe-psk           36       valid        yes   80211a-VHT-80  1258/1258        11/10      18   77    -
60:02:b4:85:31:99  18:64:72:40:b9:d1  Angel-Media       36       interfering  yes   80211a-HT-40   82897/82897      9/8        16   79    -
e8:b1:fc:87:89:76  40:e3:d6:d7:6c:b0  Hd-lab-k12        36       interfering  yes   80211a-VHT-80  3054933/3054933  2/1        11   84    -
5c:c5:d4:c1:17:9f  40:e3:d6:d7:6c:b0  Hd-lab-k12        36       interfering  yes   80211a-VHT-80  3044573/3044573  3/2        9    86    -

<output snipped>


On the IAP:

AP2# sh ap monitor sta-list

Monitored Client Table
----------------------
mac                bssid              essid             channel  sta-type     auth  phy-type       dt/mt          ut/it      snr  rssi  cl-delay
---                -----              -----             -------  --------     ----  --------       -----          -----      ---  ----  --------
ac:d1:b8:8a:6f:1f  40:e3:d6:d7:6c:b0  Hd-lab-k12        36       interfering  yes   80211a         296962/136372  7/17       17   78    -
a4:5e:60:4a:4d:a3  94:b4:0f:5c:f7:50  IAP POC Lab       165      interfering  yes   80211a-VHT-20  15260/7148     4/2        24   71    -
24:77:03:d5:ba:54  94:b4:0f:5c:f7:50  IAP POC Lab       165      interfering  yes   80211a-HT-20   387504/176661  8/3        18   77    -
a4:67:06:46:55:e7  94:b4:0f:5c:f7:50  IAP POC Lab       165      interfering  yes   80211a-HT-20   4048/1902      437/203    15   80    -
40:e2:30:1c:82:4b  40:e3:d6:d7:6c:b0  Hd-lab-k12        36       interfering  yes   80211a         385484/176819  18/46898   19   76    -
8c:29:37:e8:2d:70  94:b4:0f:5c:f7:50  IAP POC Lab       165      interfering  no    80211a         1318/628       579/272    27   68    -

<output snipped>

 

If you have verified all the above steps and still do not see any location events on ALE, please open a Support ticket.

 

 

 

 

Version history
Revision #:
2 of 2
Last update:
‎03-18-2017 01:01 PM
Updated by:
 
Labels (1)
Contributors
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.