When the UXI agent runs a test and the test failed, if the location is available, the agent will get the location of the issue and report the location in the issue triage.
Zebra Devices / OS Lifeguard Update Version
To enable location, you need Zebra devices with specific OS/Lifeguard versions that support 802.11mc. At this time, you must have a Zebra device running A10 with lifeguard 120.
You must also have Aruba 500 series APs with a software version that supports 802.11mc location. In our testing, we use AOS 184.108.40.206_84941.
Aruba Central Floormaps in VisualRF
Ensure VisualRF has the floormaps and correct AP placement on the floormaps.
Aruba Central FTM Enabled on the SSID
On the SSID the Zebra Devices are connected to, you need to enable "Fine Timing Measurement (802.11mc) Responder Mode"
Testing the network to ensure FTM is working
It is recommended to use a 3rd party app from google to make sure FTM is working on your network. https://play.google.com/store/apps/details?id=com.google.android.apps.location.rtt.wifirttscan&hl=en_US&gl=US
Once you have all the prerequisites in place, follow these steps to enable the UXI Agent for Zebra to collect location when issues occur.
Integrate your UXI Dashboard with Aruba Central
Follow these steps to complete the Aruba Central Integration in your UXI dashboard. UXI will also collect the floormaps and BSSIDs from Aruba Central.
Verify Floormaps Are Created by the Agent on the Device
Start the UXI Agent. Based on the BSSID the device is connected to, the agent will fetch the appropriate floormap for your location. If everything was setup properly, you would see a floormap.xml file on the Zebra device under Documents -> Aruba.
Stage the Device to Enable Location using the Floormap.xml file
You can follow the Zebra guide to create a stagenow profile that enables and activates FTM on the device, or scan the following barcode in stagenow which has everything you need already.
Now when the UXI Agent for Zebra runs a test and the test fails, the agent will attempt to get the location from the device and attach the location to the issue in the issue triage.
Threshold issues are computed on the cloud, not on the device. Therefore threshold issues will not have a location.
Not all triage issues will have the location. Location is only displayed if the device returns the location to the agent when asked.
All other features are vendor agnostic, only this feature requires Aruba 500 series APs managed by Aruba Central.