Back to All Scenarios
PASSEDvendor / meraki_ap_fleet_offline
Meraki AP Fleet Offline — 20 APs Lose Cloud Connectivity
An upstream switch reboot causes 20 Meraki MR46 access points to lose their uplink simultaneously. APs lose Meraki Dashboard cloud connectivity and fall into local management mode. SSIDs remain broadcasting but no new clients can authenticate via RADIUS.
Pattern
MERAKI_EVENT
Severity
CRITICAL
Confidence
85%
Remediation
Remote Hands
Test Results
| Metric | Expected | Actual | Result |
|---|---|---|---|
| Pattern Recognition | MERAKI_EVENT | MERAKI_EVENT | |
| Severity Assessment | CRITICAL | CRITICAL | |
| Incident Correlation | Yes | 46 linked | |
| Cascade Escalation | Yes | Yes | |
| Remediation | — | Remote Hands — Corax contacts on-site support via call, email, or API |
Scenario Conditions
20 Meraki MR46 APs on IDF switch stack. Switch stack rebooted unexpectedly. APs configured for cloud-managed RADIUS proxy. 300+ wireless clients affected. Meraki Dashboard shows fleet offline.
Injected Error Messages (3)
Meraki Dashboard alert: 20 MR46 access points offline — Building-A AP fleet lost cloud connectivity, devices unreachable, last seen 3 minutes ago, SSID 'Corp-WiFi' degraded
IDF switch stack reboot detected — Cisco 9300 stack recovering, PoE ports re-initializing, 20 downstream Meraki APs lost power during stack reload, port Gi1/0/1-24 cycling
RADIUS authentication requests dropping — Meraki cloud RADIUS proxy offline for Building-A APs, 802.1X auth failures spiking, NPS seeing no requests from Meraki APs
Neural Engine Root Cause Analysis
The Building-A Meraki AP fleet has lost cloud connectivity, resulting in 20 MR46 access points going offline simultaneously 3 minutes ago. This appears to be a network infrastructure failure affecting the upstream connection from Building-A to Meraki's cloud dashboard, rather than individual AP hardware failures. The presence of 15 correlated incidents in the same time window strongly suggests a shared network infrastructure root cause, likely an ISP outage, core network equipment failure, or firewall/routing issue preventing the APs from maintaining their cloud management connection.
Remediation Plan
1. Verify Building-A internet connectivity and ISP status 2. Check core network equipment (switches, routers, firewalls) serving Building-A for failures or configuration changes 3. Test connectivity from Building-A to Meraki cloud endpoints (dashboard.meraki.com, *.meraki.com) 4. Review firewall rules and routing tables for changes that might block Meraki traffic 5. If network infrastructure is confirmed functional, contact ISP to investigate upstream connectivity issues 6. Consider temporary failover to backup internet connection if available 7. Monitor for AP recovery once network connectivity is restored
Tested: 2026-03-30Monitors: 3 | Incidents: 3Test ID: cmncjga3o017pobqeif0di498