Specifically in AOS-8.13 and AOS-10.8, the Indoor SP Location feature was added using Beacons and Probe Responses, rather than FTM exchanges, to share GNSS location (ellipse) to neighboring APs.
Original Message:
Sent: Aug 18, 2026 04:28 AM
From: DR-fb7371
Subject: GPS Positioning for Internal APs
Thank you Josh, that's really helpful. I had created a GPS profile, but hadn't found the explanation of the "Broadcast GPS" option. I will give the struggling ones some time to see if that helps, but there may not be enough for that to work (which takes me back to my first point of why most APs don't get a reliable signal).
However, I still can't find anything that explains how the GPS enabled APs interact with the non-GPS ones using FTM or how to see the calculated location for non-GPS APs. "show ap details" only includes the location specified during provisioning and "show ap gps" understandably doesn't work on non-gps APs. I have ftm-responder-enable set on the VAP.
Original Message:
Sent: Aug 17, 2026 01:23 PM
From: JS-d3d5bc
Subject: GPS Positioning for Internal APs
For the second problem, look here:
Expand 8.13.0.0: https://arubanetworking.hpe.com/techdocs/ArubaOS/AOS_8x_WebHelp/Content/arubaos-solutions/AOS8-Whats-New.htm
Enable Broadcast GPS of the AP (indoor-sp-location is the CLI command): https://arubanetworking.hpe.com/techdocs/ArubaOS/AOS_8x_WebHelp/Content/arubaos-solutions/access-points/gps.htm
Original Message:
Sent: Aug 17, 2026 01:11 PM
From: DR-fb7371
Subject: GPS Positioning for Internal APs
Thanks Josh, you have hit one of the problems on the head - all the documentation is for central, but I am on AOS 8.13 with Conductors & cluster and I can't find anything for that
So you see I have two problems, one is that the AP-635 seem to struggle to get a GPS lock and the other is if I got GPS positions on my AP-635 I can't find out how to propagate that across the rest of my APs.
Original Message:
Sent: Aug 17, 2026 12:22 PM
From: JS-d3d5bc
Subject: GPS Positioning for Internal APs
This is currently available via enabling `indoor-sp-location` in the GPS stub which allows APs with an ellipse to share OTA via beacons. Which AOS version? Managed by Central or MCR?
Original Message:
Sent: Aug 17, 2026 12:08 PM
From: DR-fb7371
Subject: GPS Positioning for Internal APs
Hi Herman, yes they have had three weeks to get a lock on any satellites. This is a test building and my plan has been to have two GPS-enabled APs near windows on each floor, so they can get co-ordinates and then communicate with the other non-GPS AP-515 via FTM and across the whole building there will be 12 which have GPS.
I have been looking for information on how to get the APs to use FTM to talk to each other but have drawn a blank - this seems to be little or no documentation on this, but unless the AP-635 lock on to GPS it's not going to be much use anyway.
Original Message:
Sent: Aug 17, 2026 11:22 AM
From: HR-abaef5
Subject: GPS Positioning for Internal APs
Have you given it some time? It may take 24h or more for APs to accurately report GPS location, which is because they 'work together' to get a full GPS picture from different APs that only have limited view on GPS satellites. Also, I think per floor there are 3 APs selected as anchor APs, the others are derived from those anchors.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your HPE Aruba Networking partner, distributor, or Aruba TAC Support. Check https://www.arubanetworks.com/support-services/contact-support/ for how to contact HPE Aruba Networking TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or HPE Aruba Networking.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------