Overview

You can only see Meraki data for meetings that are hosted in your organization. If users join external meetings, then Meraki troubleshooting data for those external meetings won't be shown. Meraki data is kept up to a maximum of seven days in Troubleshooting.

Data is shown in five-minute intervals. The thresholds for good and poor data are:

  • Good (green)—SNR >= 20db or RSSI >= -80dBm or Average wireless latency <= 200ms
  • Poor (red)—SNR < 20db or RSSI < -80dBm or Average wireless latency > 200ms
Meraki troubleshooting data in Control Hub

Limitations

Meraki troubleshooting data is only available:

  • Up to a maximum of seven days. When viewing troubleshooting data for meetings beyond the previous seven days, the Meraki data line will be greyed out.
  • For the desktop version of Webex App and Cisco Room series devices. The mobile version of Webex App isn't supported.
  • For devices that are online. The Meraki data line won't show for devices that are offline.

Install and activate Meraki

You must have the full administrator role in order to set up Meraki integration for Troubleshooting.

1

Sign in to Control Hub, go to Organization Settings, and scroll to the Meraki section.

2

Toggle the Allow Meraki API access switch to on.

Allow Meraki API access setting in Control Hub
A pop-up window appears with a timer to show that Control Hub is requesting access to your Meraki dashboard account. If you don't finish setting up Meraki before the timer runs out, you must refresh the page to get the latest status update.
3

A tab page to the Meraki dashboard is shown. Sign in with your Meraki full administrator account to continue setting up the integration.

Meraki sign-in page for Troubleshooting integration in Control Hub
4

Select a Meraki organization to integrate with Troubleshooting in Control Hub.

Screenshot of allowing or denying Meraki access to a Control Hub organization
5

Select Allow.

The page returns to Control Hub with a success window if authorization has succeeded.
6

Once you finish setting up the integration, you can view the Control Hub organization details in the Meraki dashboard by going to Organization > Configure > Integrations > My integrations.

Meraki data troubleshooting charts

Key performance indicators (KPIs)

  • AP connection issue—Number of failed connections to a Meraki access point (AP) during a meeting.
  • Poor signal quality—Percentage of poor signal quality during a meeting. Signal quality is counted as poor if signal-to-noise ratio (SNR) is < 20db or received signal strength indicator (RSSI) is < 80dBm.
  • Average wireless latency—Average percentage of poor wireless latency during a meeting.
  • Data rate—Percentage of poor data rate during a meeting.
Meraki troubleshooting KPIs in Control Hub

Client connection

This chart shows details about the connection between the client, AP, and switch.

Meraki troubleshooting client connection in Control Hub

Access point details

This table provides information about the access point that a client connected to. Available details are:

  • Access Point—Name of the AP.
  • AP Model—Key and mac address of the AP.
  • Serial—Serial number of the AP.
  • LAN IP—LAN IP associated with the AP.
  • Wireless capabilities—Type of wireless connections that the AP supports.
Meraki troubleshooting access point details in Control Hub

Network quality

This graph shows the signal quality and wireless latency of the client on the Meraki network in five-minute intervals. You can hover over a spot in the line to see more details about the quality.

Meraki troubleshooting network quality in Control Hub

Signal quality

This graph shows the average SNR and RSSI for clients connected to the AP in five-minute intervals. If signal quality is poor, performance will likely be worse (i.e. more latency and slower data rates). The cause of poor signal strength can come from changes in the physical environment, RF configuration, or a far distance from the AP.

This graph only captures wireless network data.
Meraki troubleshooting signal quality in Control Hub

Wireless latency

This graph shows the wireless latency of the client in five-minute intervals. A connection with high latency can cause slowness during meetings. The cause of high latency can come from poor signal quality, interference, or high load on the AP.

Meraki troubleshooting wireless latency in Control Hub

AP Channel utilization

This graph shows the percentage of channels that were utilized by clients in ten-minute intervals. A high percentage of channel utilizations can cause higher than average latency. High channel utilization can also come from interference created by things like microwaves, bluetooth, and interference from neighboring APs.

This graph only captures wireless network data.
Meraki troubleshooting AP channel utilization in Control Hub

AP # of clients

This graph shows how many clients were connected to a specific access point (AP) in five-minute intervals. If an AP has a high number of clients connected to it, it can contribute to higher than average latency.

Meraki troubleshooting AP # of clients graph in Control Hub

AP usage

This graph shows how many clients connected to a specific AP in five-minute intervals. If an AP has a high number of clients connected to it, it can contribute to higher than average latency.

This graph only captures wireless network data.
Meraki troubleshooting AP usage graph in Control Hub

Client usage

This graph shows the received and sent data from a client in five-minute intervals.

Meraki troubleshooting client usage graph in Control Hub

Data Rate

This graph shows data rates used as a percentage of the maximum data rate that this client supports. A connection with low data rates will feel consistently sluggish. Poor data rates can occur due to poor signal quality, or client device or AP capability limitations.

This graph only captures wireless network data.
Meraki troubleshooting data rate graph in Control Hub