The UXI Agent uses the Zebra Wireless Insights service. This service runs on the Zebra device and analyzes the packets to provide the roaming experience of the device.

In order for the agent to collect this data, the Zebra Wireless Insights license must be installed and activated on the device.

When roams occur and the data is reported to the agent, you will see new charts in the UXI dashboard.

The percentages and numbers in the graphs are based on the time-bucket you are viewing. In this example, it is showing 11:00-12:00. So within that one hour period, these graphs are saying there were 16 roams. All roams completed successfully without needing to retry, and no roam started and failed to where the device became disconnected.

Moving the mouse to the right slightly, we can see that results during the next hour.

In this example, it is showing 12:00-13:00. So within that one hour period, these graphs are saying there were 2 roams. All the roams did complete successfully. Half of the roams completed without needing to retry, and half needed to retry. and no roam started and failed to where the device became disconnected. To understand why a roam needed to retry, you can look at the triage menu.

Other charts like BSSID, channel are the most common within that time bucket. You can click and drag to zoom in to see more information. The lowest you can zoom in is 1-minute time-bucket.

You can see roaming issues in the status section of the sensor page.

When you click on the roaming issue, the triage menu will give you a detailed breakdown of the roam failure as reported by the Wireless Insights service from the packet analysis.

The first line of the triage that says "Roam Complete". This is the last successful message before the roaming issue began. Next you will see the "Roam Started" message, followed by a reason in () for why the roam started. The remaining messages follow a similar format until the roam completes or fails.

For any message you can click the + to expand to see the result from the Zebra service. The only important fields in the service output are the last BSSID (apMac), deivceMac, eventDate and timeStamp. The other important parts such as the event and reason we have translated for you in the message header therefore the other aspects of the service output can be ignored.