Skip to main content
Cisco Meraki Documentation

Client Roaming Analytics

Click 日本語 for Japanese

Overview

Wireless roaming is a feature that allows you to maintain connectivity to the network as you move from one place to another. This technology allows your device to switch between different wireless networks, ensuring that you stay connected even if you're not in one place for an extended period of time.

Learn more with these free online training courses on the Meraki Learning Hub:

Sign in with your Cisco SSO or create a free account to start training.

Roaming behavior is often complex and difficult to troubleshoot. More often than not, users are forced to rely on timelines or connection logs, manually filtering and tracking entries for the client device(s) they’re interested in. This is what the current interaction might look like on the timeline:

Screenshot of a wireless Clients Timeline section with timespan set to last day.png

With the introduction of Roaming Analytics, Meraki Health transforms a static log of network events into a highly engaging, interactive, visualization of roaming behavior. Roaming analytics require a minimum firmware version of MR 29.4. Access point firmware updates can be scheduled on the General Configuration page under the "Firmware upgrades" section. For more information, see: Managing Firmware Upgrades

Screenshot of Roaming overview including categories roaming timeline and roaming event log.png

Features

Available as a new tab for all wireless clients, Roaming Analytics offers a variety of features designed to make troubleshooting roaming events easier than ever.

Event Categories

Screenshot showing Event Categories and hover over modal for ping pong clients.png

Using the time range selector, users can visualize roaming events during the last 6 hours, 12 hours, 24 hours, or last week. All roaming events during the selected period are automatically categorized into five event types. When hovering over event type tiles, the following descriptions are displayed:

  • Bad roams

    • any roam where the roam time is >= 3000ms (3 seconds); or

    • any roam where the RSSI on the arriving AP is >10dBm worse than the originating AP

  • Suboptimal roams

    • any roam where the roam time is between 250ms and 3s; or

    • any roam where the RSSI on the arriving AP is 6-10dBm worse than the originating AP

  • Good roams

    • Any roam where the roam time is <250ms and RSSI is better or no worse than 5 dBm than the originating AP

  • Ping pong clients

    • Any roam where the client is only roaming between two APs; and

    • A minimum of four roams occur between these two APs; and

    • Roams are, at most, 10 seconds apart

  • Sticky clients

    • Any client where its current SNR is <15 dB while there is an alternative at least 10 dB better; and

    • The transmit (Tx) power of the alternative is within 5 dBm of the current connection; and

    • The above is true for at least 10 minutes

  • Client disconnects

    • Client device left the network, and no roaming behavior was detected

Roaming Events Timeline

Screenshot showing Roaming status and Roaming timeline.png

All roaming behavior during the selected time period is presented as a chronological ribbon of roaming events. Each event is color-coordinated to its event category. By dragging the blue range selector, users can visualize the specific times or events that are most relevant to them. As the range selector moves, the below visual automatically adjusts to display roaming events during that time period. 

When hovering over specific roaming events, users are presented with a popover that details that particular event: date, time, APs, bands, RSSI, roaming protocol, and roam time.

Note that at any point in time, users are able to use their cursor to “zoom” into the timeline from a 1-hour interval to 2-minutes, by clicking on an event in the timeline.

Screenshot showing one hour Roaming timeline and hover over modal for a bad roam event with transition to two minute span when zoomed.png

Roaming Event Log

In addition to the visualized events, the user is presented with a log of all roaming activity for the client device. Note the blue focus state indicator. This indicator tracks the position of your cursor in the visualization to intelligently draw your attention to the corresponding event in the table. This also works in reverse; your cursor position in the table will intelligently focus the visualization.

The combination of an event log with visualization, along with intelligent focusing, presents roaming events in context. This enables users to quickly determine whether their roaming issues are isolated or will require additional troubleshooting.

Screenshot showing Roaming timeline highlighting an event in the roaming event log when hovered over.png

 

 

  • Was this article helpful?