Cisco Meraki Cloud

This monitoring solution provides visibility into Cisco Meraki cloud-managed wireless infrastructure, including device availability, wireless performance, network client statistics, connection health, and license status using the Meraki Dashboard REST API.

Node SettingsMonitoringAdd Monitoring Sensor

Meraki Cloud monitoring gives a centralized view of all devices and networks within a Meraki organization. One sensor covers an entire organization — networks are discovered automatically, each appearing as a counter instance, and devices are discovered and listed in the Devices view.

Individual wireless devices are monitored by the Meraki Wireless sensor, which is added per device from the Devices view and takes its data from this sensor.

Requirements

This monitoring requires a Cisco Meraki credential profile containing a valid Meraki Dashboard API key with read access to the organization.

Options

After selecting credentials, choose the organization to monitor from the list, which is populated automatically using the API key. The organization field is read-only once the sensor has been created.

The default polling interval is 5 minutes.

Device Status Summary

The sensor does not track devices individually — it aggregates the status the Meraki cloud reports for every device in the organization:

• Online — device is reachable and communicating normally
• Offline — device is unreachable
• Alerting — device is reachable but has an active Meraki alert
• Dormant — device has not communicated recently but is not considered failed

The counts per status are published as the Summary counters. Each network gets a status object reflecting the devices it contains — Error when any of them is offline, Warning when any is alerting, otherwise OK. The sensor status itself is degraded to Warning when any device in the organization is offline or alerting.

The state of an individual device — and its CPU, memory, channel utilization, packet loss and latency — is monitored by the Meraki Wireless sensor added for that device.

Alerts:

Device membership, carrying the serial number, name, MAC, model and product type of the device:

• New Meraki Device Detected — a device was added to the network (Warning)
• Meraki Device Removed from the Network — a device is no longer in the network (Warning)

Network-level

• Network 2.4 GHz Congested — network-wide 2.4 GHz utilization above 75%; all APs in the network are congested
• Network 5 GHz Congested — network-wide 5 GHz utilization above 80%
• Network Upstream Packet Loss — upstream loss above 3% network-wide for 3 consecutive polls; systemic RF issue
• Network Downstream Packet Loss — downstream loss above 3% network-wide for 3 consecutive polls
• Heavy-Usage Clients — more than 50 clients classified as heavy users simultaneously; consider applying QoS limits

Connection failures

• Association Failures — clients repeatedly failing to associate to APs; check RF coverage, AP load, or SSID configuration
• Authentication Failures — clients failing authentication for 3 consecutive polls; check RADIUS, PSK, or 802.1X certificates
• DHCP Failures — clients not receiving IP addresses; check scope exhaustion or DHCP relay configuration
• DNS Failures — client DNS lookups failing; check DNS server reachability or Meraki DNS settings

License

• License Expired — the organization license has expired; devices may lose cloud management capabilities (Critical)
• License Warning — the license is expiring within 14 days, or per-device licenses are expiring soon (Warning)

Performance Metrics — Summary (organization-wide):

• Summary/Total Devices
• Summary/Online Devices
• Summary/Offline Devices
• Summary/Alerting Devices
• Summary/Dormant Devices

Performance Metrics — Network:

Collected per network.

• Network/Clients Total
• Network/Clients Heavy Usage
• Network/Avg Data Usage Per Client
• Network/% Channel Util 2.4 GHz
• Network/% Channel Util 5 GHz
• Network/% Upstream Packet Loss
• Network/% Downstream Packet Loss

Performance Metrics — Connection:

Collected per network, where the instance is the network name.

• Connection/Association Failures
• Connection/Authentication Failures
• Connection/DHCP Failures
• Connection/DNS Failures
• Connection/Successful Connections

Sensor Views

The sensor provides four on-demand views in the sensor detail panel.

Devices

All devices in the organization with status, network, model, firmware, IP address, CPU load, and memory usage. Wireless devices can be added for monitoring from here.

Networks

All networks with health status, client counts, average data usage, and offline device count.

Clients

Clients seen on a selected network in the last 24 hours, including MAC, IP, OS, SSID, VLAN, data usage, and last seen AP.

Other SSIDs

Wireless Air Marshal scan results for a selected network — neighbouring SSIDs and BSSIDs detected by the APs, with signal strength, channels, and first and last seen times.

Adding Devices for Monitoring

A device that is not monitored yet can be given a Meraki Wireless sensor straight from the Devices view. The monitoring column offers the node already using the LAN address of the device, or adds a new node for it — asking for the site, and for the monitoring probe where the site has more than one — and then configures the sensor on that node.

Only wireless devices with a known LAN address can be added this way, since the Meraki Wireless sensor exists for that product type alone and the node is identified by its address. Devices of other product types show no add action.

access pointair marshalcloudmerakimeraki-cloudwifiwireless