AP Testing and Verification
9 minute read
If there are telemetry or other FTM data issues, navigate to the AP and execute specific show commands to pinpoint the problem.
Verifying AP configuration
To verify that the configuration has been successfully pushed to the AP, run the command show running-config | include FTM. Ensure that both ftm-scan-enable and ftm-responder-enable are present, indicating that FTM is enabled and capable of facilitating FTM exchanges between APs.
Example:
AP-AOS10# show running-config | include ftm
ftm-scan-enable
ftm-responder-enable
Additionally, you can check if the GPS setting is enabled.
AP-AOS10# show running-config
gps
state enable
Analyzing FTM details
To examine FTM data, use the command show ap range scanning-results. This command provides a display of all successful FTM measurements between peer APs within the last 20 minutes. The output includes the following information, which proves useful for debugging the channel:
-
Average RTT: Presented in nanoseconds, to be later converted into meters.
-
Average RSSI: If the RSSI increments, it indicates that the AP is farther away, resulting in higher RTT.
-
Average STD: The standard deviation can indicate the quality of the results.
-
Channel: The AP predominantly selects an 80 MHz channel, which is optimal for accurate FTM. Choosing 80 MHz provides more resolution and better accuracy, making it the recommended option for improved results.
Example:
AP-AOS10# show ap range scanning-results
Ranging results
---------------
Peer-bssid Average RTT Average rssi (dbm) Average std (100ps) Channel Number of valid RTTs Number of FTMs Antenna RTTs/Init-mask/Resp-mask Time Stamp
---------- ----------- ------------------ ------------------- ------- -------------------- -------------- ------- ------------------------ ----------
74:9e:75:41:17:30 69 60 10 36E 15 16 0 69,0,0 69,0,0 69,0,0 69,0,0 68,0,0 66,0,0 69,0,0 69,0,0 70,0,0 70,0,0 70,0,0 70,0,0 69,0,0 70,0,0 68,0,0 2024-03-21 11:47:01
74:9e:75:41:4f:70 114 64 4 36E 16 16 0 114,0,0 113,0,0 113,0,0 114,0,0 114,0,0 114,0,0 114,0,0 113,0,0 113,0,0 114,0,0 114,0,0 114,0,0 114,0,0 114,0,0 113,0,0 114,0,0 2024-03-21 11:47:15
74:9e:75:41:7c:70 137 61 53 36E 15 16 0 127,0,0 141,0,0 141,0,0 138,0,0 139,0,0 140,0,0 139,0,0 126,0,0 141,0,0 140,0,0 126,0,0 140,0,0 141,0,0 140,0,0 138,0,0 2024-03-21 11:47:30
00:4e:35:e9:19:50 146 69 14 36E 13 16 0 147,0,0 145,0,0 144,0,0 144,0,0 145,0,0 144,0,0 144,0,0 146,0,0 147,0,0 147,0,0 147,0,0 147,0,0 147,0,0 2024-03-21 11:48:13
00:4e:35:e9:12:d0 143 64 7 36E 15 16 0 142,0,0 143,0,0 142,0,0 142,0,0 144,0,0 143,0,0 144,0,0 142,0,0 142,0,0 144,0,0 143,0,0 143,0,0 144,0,0 142,0,0 142,0,0 2024-03-21 11:48:27
74:9e:75:41:0e:60 147 71 3 36E 14 16 0 147,0,0 147,0,0 147,0,0 147,0,0 147,0,0 147,0,0 147,0,0 146,0,0 147,0,0 147,0,0 147,0,0 146,0,0 147,0,0 148,0,0 2024-03-21 11:48:39
74:9e:75:41:4f:70 115 66 3 36E 16 16 0 114,0,0 114,0,0 115,0,0 114,0,0 115,0,0 115,0,0 115,0,0 114,0,0 115,0,0 115,0,0 114,0,0 115,0,0 115,0,0 114,0,0 113,0,0 115,0,0 2024-03-21 11:48:56
74:9e:75:41:7c:70 138 62 3 36E 16 16 0 138,0,0 138,0,0 138,0,0 138,0,0 138,0,0 138,0,0 138,0,0 137,0,0 138,0,0 137,0,0 137,0,0 137,0,0 137,0,0 138,0,0 138,0,0 138,0,0 2024-03-21 11:49:11
Total:8
About 20 mins to age out
Reading FTM summary
Run the command show ap range scanning-summary. This command can be used for debugging purposes, it allows you to determine if an AP is rejecting FTM data, providing insights into potential issues within the setup. For instance, if the Fail Scan counter continues to rise or matches the Scan counter, it indicates that the AP is unable to reach or communicate with the neighboring AP indicated by the Peer-bssid.
Example:
AP-AOS10# show ap range scanning-summary
Ranging History
---------------
Peer-bssid Total Scan Fail Scan
---------- ---------- ---------
74:9e:75:41:3d:d0 4877 4800
74:9e:75:41:17:30 9119 637
00:4e:35:e9:12:d0 8930 82
74:9e:75:41:27:20 6467 3289
74:9e:75:41:40:70 5524 4231
74:9e:75:41:4f:70 8838 919
00:4e:35:e9:19:50 8957 798
74:9e:75:41:7c:70 9068 687
74:9e:75:41:0e:60 8522 123
d0:d3:e0:ef:61:50 4914 4844
Total:10
AP-AOS10#
Analyzing FTM history
Use the command show ap range scanning-history, which provides the following fields:
-
Peer-bssid: BSSID of neighboring APs.
-
Last scan result, with possible values:
- 0: Success
- 1: AP driver is engaged in other tasks (busy), which occurs as the AP changes channels and requires time for detection.
- 2: Unreachable target BSSID, indicating a lack of connection with the peer AP.
It is normal to observe occasional failures and achieving a 100% success rate may not always be possible.
Example:
AP-AOS10# show ap range scanning-history
Ranging History
---------------
Peer-bssid Last Scan Result Time Stamp
---------- ---------------- ----------
00:4e:35:e9:12:d0 0 2023-12-17 18:28:18
74:9e:75:41:27:20 0 2023-12-17 18:28:51
74:9e:75:41:3d:d0 0 2023-12-17 18:29:29
d0:d3:e0:ef:61:50 0 2023-12-17 18:30:02
74:9e:75:41:27:20 0 2023-12-17 18:30:33
74:9e:75:41:3d:d0 0 2023-12-17 18:31:06
d0:d3:e0:ef:61:50 0 2023-12-17 18:31:41
74:9e:75:41:0e:60 2 2023-12-17 18:32:08
74:9e:75:41:0e:60 2 2023-12-17 18:32:22
74:9e:75:41:0e:60 0 2023-12-17 18:32:35
d0:d3:e0:ef:61:50 0 2023-12-17 18:49:10
Total:11
For result, 0: success; 1: fail because of driver busy; 2: unreachable target BSSID
Verifying cloud telemetry
Activate the debug log by executing the command debug-log-to-cloud. Subsequently, wait for 5 minutes, as the AP sends the telemetry to the cloud every 5 minutes. Then use the command show log stats-to-cloud ftmscan to confirm that the AP is indeed sending the FTM telemetry. This command enables you to verify details such as the BSSIDs, radios and channels of peer APs, and whether the AP is actively engaging in FTM exchanges, providing additional diagnostic information.
Example:
AP-AOS10# debug-log-to-cloud
AP-AOS10# show log stats-to-cloud ftmscan
2023-12-17 19:07:07 T PeerFTMReport Stats: peer_mac[74:9e:75:41:3d:d0], radio_mac[74:9e:75:41:40:70], channel[124], band[1], bandwidth[1], ftm_avg_rssi[49]
2023-12-17 19:07:07 ... ftm_avg_rtt[73], ftm_min_rtt[70], ftm_max_rtt[74], ftm_std_dev[13], ftm_num_samples[16], ftm_valid_samples[16], chain_mask[0]
2023-12-17 19:07:07 ... time_stamp[1702867028]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[70], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[74], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[74], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[74], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T PeerFTMReport Stats: peer_mac[00:4e:35:e9:12:d0], radio_mac[74:9e:75:41:40:70], channel[44], band[1], bandwidth[1], ftm_avg_rssi[79]
2023-12-17 19:07:07 ... ftm_avg_rtt[327], ftm_min_rtt[323], ftm_max_rtt[330], ftm_std_dev[21], ftm_num_samples[16], ftm_valid_samples[16], chain_mask[0]
2023-12-17 19:07:07 ... time_stamp[1702867066]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[323], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[330], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[326], init_mask[0], resp_mask[0]
2023-12-17 19:07:07 T FTMMeasurement Stats: ftm_rtt[328], init_mask[0], resp_mask[0]
Verifying GPS telemetry
Confirm the availability of GPS telemetry for the 600 series APs by using the command show ap gps summary. This command displays GPS information on the AP, allowing you to assess whether the AP is obtaining GPS latitude and longitude values. In cases where the AP is situated indoors and may face challenges in acquiring GPS location, checking this information becomes particularly useful for the APs.
Example:
AP-AOS10# sh ap gps summary
GPS Information
---------------
Type Position (Latitude,Longitude) Altitude
---- ------------------------------ --------
$GNGGA 37.385870, -121.987549 34.2 M
$GNRMC 37.385870, -121.987549 N/A
$GNGLL 37.385870, -121.987549 N/A
GPS Configuration
------------------
Current Dynamic Model
---------------------
stationary
AP-AOS10#
If you do not observe any FTM or GPS data, ensure that the AP can detect neighboring APs by executing the command show ap monitor ap-list. This command provides a list of AP neighbors and indicates whether the AP is FTM capable or not in the FTM support column at the right most side.
Additionally, validate whether the AP is scanning different channels by using the command show ap arm scan-times.
Example:
AP-AOS10# show ap monitor ap-list
Monitored AP Table
------------------
bssid essid band/chan/ch-width/ht-type ap-type transition-type confirmed dos dt/mt ut/it encr nstas avg-snr curr-snr avg-rssi curr-rssi wmacs ibss cl-delay pathloss bss-color partial bss color bss color disabled FTM support snr/rssi-age snr/rssi-report-age
----- ----- -------------------------- ------- --------------- --------- --- ----- ----- ---- ----- ------- -------- -------- --------- ----- ---- -------- -------- --------- ----------------- ------------------ ----------- ------------ -------------------
74:9e:75:41:0e:60 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid no disable 1280967/1280967 10/9 wpa2-psk-aes 0 25 25 70 70 0 no 0 0 21 false false yes 9 2
74:9e:75:41:40:70 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid yes disable 1280964/1280964 7/6 wpa2-psk-aes 0 12 12 82 83 0 no 256 96 25 false false yes 6 2
00:4e:35:e9:19:50 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid yes disable 1280964/1280964 7/6 wpa2-psk-aes 0 34 34 60 61 0 no 256 76 37 false false yes 6 2
74:9e:75:41:27:20 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid yes disable 1280964/1280964 7/6 wpa2-psk-aes 0 31 31 63 64 0 no 256 75 3 false false yes 6 2
00:4e:35:e9:12:d0 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid yes disable 1280964/1280964 2/1 wpa2-psk-aes 0 32 33 62 62 0 no 256 78 45 false false yes 1 2
74:9e:75:41:3d:d0 Open-Locate-Network 5GHz/36E/80MHz/HE valid valid yes disable 1280952/1280952 7/6 wpa2-psk-aes 0 7 7 87 88 0 no 244 99 26 false false yes 6 2
Additionally, validate whether the AP is scanning different channels by using the command show ap arm scan-times.
AP-AOS10# sh ap arm scan-times
Channel Scan Time
-----------------
channel band assign-time(ms) scans-attempted scans-rejected scans-deferred dos-scans flags timer-tick
------- ---- --------------- --------------- -------------- -------------- --------- ----- ----------
34 5GHz 19580 178 0 0 0 DYp 2261483
36 5GHz 1102671440 3604 0 0 0 DVACLYFETSp 2265270
38 5GHz 182270 1657 0 0 0 DYp 2261857
40 5GHz 377630 3433 0 0 0 DVACUYBPTSJp 2264996
42 5GHz 0 543 1086 0 0 DYp 0
44 5GHz 404030 3673 0 0 0 DVACLYFBTSMp 2265003
46 5GHz 202620 1842 0 0 0 DAYp 2265025
112 5GHz 348370 3167 0 0 0 DACUYXSJp 2265117
116 5GHz 402270 3657 0 0 0 DACLYXSMp 2265126
120 5GHz 402050 3655 0 0 0 DACUYXSJp 2265129
124 5GHz 375320 3412 0 0 0 DACLYXSMp 2265178
128 5GHz 356400 3240 0 0 0 DACUYXSJp 2265182
132 5GHz 365860 3326 0 0 0 DACLYXSMp 2265192
136 5GHz 345840 3144 0 0 0 DACUYXSJp 2265197
140 5GHz 317350 2885 0 0 0 DACLYXSMp 2265210
144 5GHz 345840 3144 0 0 0 DACUYXSp 2265238
149 5GHz 396110 3601 0 0 0 DACLYSp 2265222
153 5GHz 399520 3632 0 0 0 DACUYSJp 2265232
Channel Flags:
D: All-Reg-Domain Channel, C: Reg-Domain Channel, A: Activity Present, Z: Rare Channel
V: Valid, T: Valid 20MHZ Channel, F: Valid 40MHz Channel, P: Valid 40MHZ Channel Pair
E: Valid 80/80+80MHz Channel (First 20M), B: Belongs to valid 80/80+80MHz channel, G: Valid 160MHz Channel (First 20M), Q: Belongs to valid 160MHz channel
O: DOS Channel, K: DOS 40MHz Upper, H: DOS 40MHz Lower
R: Radar detected in last 30 min, X: DFS required, q: Zero Wait DFS, t: Zero Wait DFS Test Mode
N: Split Channel Scan J: Unconventional Scan 40MHz Above, M: Unconventional Scan 40MHz Below, L: Scan Secondary Above
U: Scan Secondary Below, Y: Scan 80MHz, W: Scan 160MHz, b: Out-of-band scan Channel (valid only for dual 5GHz mode)
p: Pooling Preference, S: Transmit Allowed, u: UTB filtered channel, x: Preferred Scan Channel (6GHz Only)
WIF Channel Scanning State.
Current opmode: Default
-----------------------------------------------------
Scan mode channel current-scan-band current-scan-channel last-dos-channel timer-milli-tick next-scan-milli-tick (jitter) scans (Tot:Rej:Eff(%):Last intvl(%))
--------- ------- ----------------- -------------------- ---------------- ---------------- ----------------------------- ------------------------------------
Moderate 36E 5GHz 161E 0 2265270000 2265273560 (166) 192086:2290:98:100
Moderate 6 2.4GHz 8+ 0 2265270000 2265270560 (165) 449753:1:99:100
Default 69S 5GHz 0 0 2265270000 0 (0) 1:0:100:0
UTB filter Info:
------------------
Type Version A1 Version A2 Version A3 Version A4 Channel Spacing
---- ---------- ---------- ---------- ---------- ---------------
BAW 3 3 3 3 50 MHz
UTB filter results:
---------------------
Band selected Last blocked channel
------------- --------------------
6GHz 0
Feedback
Was this page helpful?
Glad to hear it!
Sorry to hear that.